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 <quint...@redhat.com> > Cc: Amit Shah <amit.s...@redhat.com> > Cc: Eric Blake <ebl...@redhat.com> > Cc: Markus Armbruster <arm...@redhat.com> > Signed-off-by: zhanghailiang <zhang.zhanghaili...@huawei.com> > Signed-off-by: Li Zhijian <lizhij...@cn.fujitsu.com> > Signed-off-by: Gonglei <arei.gong...@huawei.com> > --- > 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 <ebl...@redhat.com> -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
