From: Eric Blake <eblake@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, quintela@redhat.com, dgilbert@redhat.com,
eddie.dong@intel.com, lizhijian@cn.fujitsu.com,
zhangchen.fnst@cn.fujitsu.com, xuquan8@huawei.com
Subject: Re: [Qemu-devel] [PATCH 3/3] COLO: Don't process failover request while loading VM's state
Date: Tue, 17 Jan 2017 12:24:19 -0600 [thread overview]
Message-ID: <c79e149c-7d0e-76ae-20f5-b99a595650b5@redhat.com> (raw)
In-Reply-To: <1484657864-21708-4-git-send-email-zhang.zhanghailiang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
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 <eblake@redhat.com>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-01-17 18:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 12:57 [Qemu-devel] [PATCH 0/3] COLO: fix some bugs zhanghailiang
2017-01-17 12:57 ` [Qemu-devel] [PATCH 1/3] COLO: fix setting checkpoint-delay not working properly zhanghailiang
2017-02-08 10:38 ` Dr. David Alan Gilbert
2017-02-08 11:18 ` Hailiang Zhang
2017-01-17 12:57 ` [Qemu-devel] [PATCH 2/3] COLO: Shutdown related socket fd while do failover zhanghailiang
2017-01-18 11:01 ` Dr. David Alan Gilbert
2017-02-08 11:14 ` Hailiang Zhang
2017-02-08 19:53 ` Dr. David Alan Gilbert
2017-02-13 4:13 ` Hailiang Zhang
2017-01-17 12:57 ` [Qemu-devel] [PATCH 3/3] COLO: Don't process failover request while loading VM's state zhanghailiang
2017-01-17 18:24 ` Eric Blake [this message]
2017-01-18 8:19 ` Hailiang Zhang
2017-02-10 15:44 ` [Qemu-devel] [PATCH 0/3] COLO: fix some bugs Dr. David Alan Gilbert
2017-02-13 8:46 ` Hailiang Zhang
2017-02-13 10:17 ` Dr. David Alan Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c79e149c-7d0e-76ae-20f5-b99a595650b5@redhat.com \
--to=eblake@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xuquan8@huawei.com \
--cc=zhang.zhanghailiang@huawei.com \
--cc=zhangchen.fnst@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).