qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Zhang Chen <zhangckid@gmail.com>, qemu devel <qemu-devel@nongnu.org>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RESEND V3 10/16] qmp event: Add COLO_EXIT event to notify users while exited COLO
Date: Thu, 4 Jan 2018 11:10:12 -0600	[thread overview]
Message-ID: <225d94e2-feb5-6081-faa9-4d0a028e0dfc@redhat.com> (raw)
In-Reply-To: <1515045675-6993-11-git-send-email-zhangckid@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2558 bytes --]

On 01/04/2018 12:01 AM, Zhang Chen wrote:
> From: zhanghailiang <zhang.zhanghailiang@huawei.com>
> 
> 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',

Isn't that spelled x-colo-lost-heartbeat in QMP?

> 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.
> 
> Cc: Markus Armbruster <armbru@redhat.com>
> Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> Signed-off-by: Zhang Chen <zhangckid@gmail.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---

Focusing on just the UI:


> +++ b/qapi-schema.json
> @@ -2921,6 +2921,27 @@
>  { 'command': 'query-acpi-ospm-status', 'returns': ['ACPIOSTInfo'] }
>  
>  ##
> +# @COLO_EXIT:
> +#
> +# Emitted when VM finishes COLO mode due to some errors happening or
> +# at the request of users.
> +#
> +# @mode: which COLO mode the VM was in when it exited.
> +#
> +# @reason: describes the reason for the COLO exit.
> +#
> +# Since: 2.11

You've missed 2.11; this should be 2.12.

> +#
> +# Example:
> +#
> +# <- { "timestamp": {"seconds": 2032141960, "microseconds": 417172},
> +#      "event": "COLO_EXIT", "data": {"mode": "primary", "reason": "request" } }
> +#
> +##
> +{ 'event': 'COLO_EXIT',
> +  'data': {'mode': 'COLOMode', 'reason': 'COLOExitReason' } }

Since COLOMode is in migration.json, shouldn't this 'event' declaration
live there as well?

> +
> +##
>  # @ACPI_DEVICE_OST:
>  #
>  # Emitted when guest executes ACPI _OST method.
> diff --git a/qapi/migration.json b/qapi/migration.json
> index 03f57c9..f7b2cc6 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -854,6 +854,19 @@
>  ##
>  { 'enum': 'FailoverStatus',
>    'data': [ 'none', 'require', 'active', 'completed', 'relaunch' ] }
> +##
> +# @COLOExitReason:
> +#
> +# The reason for a COLO exit
> +#
> +# @request: COLO exit is due to an external request
> +#
> +# @error: COLO exit is due to an internal error
> +#
> +# Since: 2.11

2.12

> +##
> +{ 'enum': 'COLOExitReason',
> +  'data': [ 'request', 'error' ] }
>  
>  ##
>  # @x-colo-lost-heartbeat:
> 

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2018-01-04 17:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  6:00 [Qemu-devel] [PATCH RESEND V3 00/16] COLO: integrate colo frame with block replication and COLO proxy Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 01/16] filter-rewriter: fix memory leak for connection in connection_track_table Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 02/16] colo-compare: implement the process of checkpoint Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 03/16] colo-compare: use notifier to notify packets comparing result Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 04/16] COLO: integrate colo compare with colo frame Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 05/16] COLO: Add block replication into colo process Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 06/16] COLO: Remove colo_state migration struct Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 07/16] COLO: Load dirty pages into SVM's RAM cache firstly Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 08/16] ram/COLO: Record the dirty pages that SVM received Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 09/16] COLO: Flush memory data from ram cache Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 10/16] qmp event: Add COLO_EXIT event to notify users while exited COLO Zhang Chen
2018-01-04 17:10   ` Eric Blake [this message]
2018-01-07 13:46     ` Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 11/16] savevm: split the process of different stages for loadvm/savevm Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 12/16] COLO: flush host dirty ram from cache Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 13/16] filter: Add handle_event method for NetFilterClass Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 14/16] filter-rewriter: handle checkpoint and failover event Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 15/16] COLO: notify net filters about checkpoint/failover event Zhang Chen
2018-01-04  6:01 ` [Qemu-devel] [PATCH RESEND V3 16/16] COLO: quick failover process by kick COLO thread Zhang Chen
2018-01-04  6:32 ` [Qemu-devel] [PATCH RESEND V3 00/16] COLO: integrate colo frame with block replication and COLO proxy no-reply

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=225d94e2-feb5-6081-faa9-4d0a028e0dfc@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.com \
    --cc=zhangckid@gmail.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).