Re: [Qemu-devel] [PATCH COLO-Frame v10 02/38] migration: Introduce capability 'x-colo' to migration

[Eric Blake]

On 11/03/2015 04:56 AM, zhanghailiang wrote:
> We add helper function colo_supported() to indicate whether
> colo is supported or not, with which we use to control whether or not
> showing 'x-colo' string to users, they can use qmp command
> 'query-migrate-capabilities' or hmp command 'info migrate_capabilities'
> to learn if colo is supported.
> 
> Cc: Juan Quintela <address@hidden>
> Cc: Amit Shah <address@hidden>
> Cc: Eric Blake <address@hidden>
> Cc: Markus Armbruster <address@hidden>
> Signed-off-by: zhanghailiang <address@hidden>
> Signed-off-by: Li Zhijian <address@hidden>
> Signed-off-by: Gonglei <address@hidden>
> ---
> v10:
> - Rename capability 'colo' to experimental 'x-colo' (Eric's suggestion).
> - Rename migrate_enable_colo() to migrate_colo_enabled() (Eric's suggestion).

> +++ b/qapi-schema.json
> @@ -540,11 +540,15 @@
>  # @auto-converge: If enabled, QEMU will automatically throttle down the guest
>  #          to speed up convergence of RAM migration. (since 1.6)
>  #
> +# @x-colo: If enabled, migration will never end, and the state of the VM on 
> the
> +#        primary side will be migrated continuously to the VM on secondary
> +#        side. (since 2.5)

I think this has missed 2.5, so you'll need to tweak it to say 2.6.

With that fixed,
Reviewed-by: Eric Blake <address@hidden>

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature