From: Eric Blake <eblake@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, armbru@redhat.com
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qapi-schema: clarify 'colo' state for MigrationStatus
Date: Wed, 2 Nov 2016 09:04:33 -0500 [thread overview]
Message-ID: <f1f826e3-49b6-1755-24fe-ea96d8d484b1@redhat.com> (raw)
In-Reply-To: <1478072652-9884-1-git-send-email-zhang.zhanghailiang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
On 11/02/2016 02:44 AM, zhanghailiang wrote:
> VM can not get into colo state unless users enable 'x-colo'
> capability for migration, Here it is necessary to clarify
> this.
>
> Suggested-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> ---
> v2:
> - Clarify colo state for RunState too as Eric suggested.
> ---
> qapi-schema.json | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
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:[~2016-11-02 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 7:44 [Qemu-devel] [PATCH v2] qapi-schema: clarify 'colo' state for MigrationStatus zhanghailiang
2016-11-02 14:04 ` Eric Blake [this message]
2016-11-14 2:36 ` Hailiang Zhang
2016-11-14 13:54 ` Stefan Hajnoczi
2016-11-15 6:12 ` Hailiang Zhang
2016-11-15 8:44 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2016-11-15 8:58 ` Zhang Chen
2016-11-15 9:03 ` Hailiang Zhang
2016-11-15 9:10 ` Zhang Chen
2016-11-17 7:08 ` Hailiang Zhang
2016-11-17 7:52 ` Laurent Vivier
2016-11-17 10:07 ` Stefan Hajnoczi
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=f1f826e3-49b6-1755-24fe-ea96d8d484b1@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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).