On 01/17/2017 06:57 AM, zhanghailiang wrote: > We should not do failover work while the main thread is loading > VM's state. Otherwise the consistent of VM's memory and > device state will be broken. > > We will restart the loading process after jump over the stage, > The new failover status 'RELAUNCH' will help to record if we > need to restart the process. > > Cc: Eric Blake <ebl...@redhat.com> > Signed-off-by: zhanghailiang <zhang.zhanghaili...@huawei.com> > Signed-off-by: Li Zhijian <lizhij...@cn.fujitsu.com> > Reviewed-by: Dr. David Alan Gilbert <dgilb...@redhat.com> > --- > migration/colo.c | 26 ++++++++++++++++++++++++++ > qapi-schema.json | 4 +++- > 2 files changed, 29 insertions(+), 1 deletion(-) >
> +++ b/qapi-schema.json
> @@ -856,10 +856,12 @@
> #
> # @completed: finish the process of failover
> #
> +# @relaunch: restart the failover process, from 'none' -> 'completed'
You'll need to add a '(since 2.9)' tag
> +#
> # Since: 2.8
> ##
> { 'enum': 'FailoverStatus',
> - 'data': [ 'none', 'require', 'active', 'completed'] }
> + 'data': [ 'none', 'require', 'active', 'completed', 'relaunch' ] }
>
> ##
> # @x-colo-lost-heartbeat:
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
