qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH V10 10/20] qmp event: Add COLO_EXIT event to not


From: Eric Blake
Subject: Re: [Qemu-devel] [PATCH V10 10/20] qmp event: Add COLO_EXIT event to notify users while exited COLO
Date: Mon, 23 Jul 2018 13:41:33 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

On 07/22/2018 02:33 PM, Zhang Chen wrote:
From: zhanghailiang <address@hidden>

If some errors happen during VM's COLO FT stage, it's important to
notify the users of this event. Together with 'x-colo-lost-heartbeat',
Users can intervene in COLO's failover work immediately.
If users don't want to get involved in COLO's failover verdict,
it is still necessary to notify users that we exited COLO mode.

Signed-off-by: zhanghailiang <address@hidden>
Signed-off-by: Li Zhijian <address@hidden>
Signed-off-by: Zhang Chen <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Markus Armbruster <address@hidden>
---
  migration/colo.c    | 31 +++++++++++++++++++++++++++++++
  qapi/migration.json | 38 ++++++++++++++++++++++++++++++++++++++
  2 files changed, 69 insertions(+)

At this point in the release cycle, this series feels like enough of a new feature (rather than a bug fix) that it is probably not appropriate for 3.0, which means...


+++ b/qapi/migration.json
@@ -900,6 +900,44 @@
  { 'enum': 'FailoverStatus',
    'data': [ 'none', 'require', 'active', 'completed', 'relaunch' ] }
+##
+# @COLO_EXIT:
+#
+# Emitted when VM finishes COLO mode due to some errors happening or
+# at the request of users.
+#
+# @mode: report COLO mode when COLO exited.
+#
+# @reason: describes the reason for the COLO exit.
+#
+# Since: 3.0

...this and other references should be updated to 3.1.

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]