From: Eric Blake <eblake@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] qapi: Allow introspecting fix for savevm's cooperation with blockdev
Date: Tue, 17 Sep 2019 11:33:53 -0500 [thread overview]
Message-ID: <8eae6ac1-bbc1-63ba-14b2-779ed3f42a29@redhat.com> (raw)
In-Reply-To: <249a9ca557108397b313625593bc83f161f32a16.1568735079.git.pkrempa@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1882 bytes --]
On 9/17/19 10:49 AM, Peter Krempa wrote:
> savevm was buggy as it considered all monitor owned block device nodes
> for snapshot. With introduction of -blockdev the common usage made all
> nodes including protocol nodes monitor owned and thus considered for
> snapshot. This was fixed but clients need to be able to detect whether
> this fix is present.
>
> Since savevm does not have an QMP alternative add the feature for the
> 'human-monitor-command' backdoor which is used to call this command in
> modern use.
>
> Signed-off-by: Peter Krempa <pkrempa@redhat.com>
> ---
> qapi/misc.json | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/qapi/misc.json b/qapi/misc.json
> index 6bd11f50e6..e2b33c3f8a 100644
> --- a/qapi/misc.json
> +++ b/qapi/misc.json
> @@ -1020,6 +1020,11 @@
> #
> # @cpu-index: The CPU to use for commands that require an implicit CPU
> #
> +# Features:
> +# @savevm-blockdev-monitor-nodes: If present, the savevm monitor command
> +# correctly handles monitor owned block nodes
> +# when taking a snapshot.
Is it worth adding a '(since 4.2)' on when features are added?
> +#
> # Returns: the output of the command as a string
> #
> # Since: 0.14.0
> @@ -1047,7 +1052,8 @@
> ##
> { 'command': 'human-monitor-command',
> 'data': {'command-line': 'str', '*cpu-index': 'int'},
> - 'returns': 'str' }
> + 'returns': 'str',
> + 'features' : [ { 'name': 'savevm-blockdev-monitor-nodes' } ] }
We could, of course, actually implement a QMP 'savevm' and use _that_ as
the introspection. But that's a bigger can of worms, so this is
reasonable enough for the 4.2 timeframe.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-17 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 15:49 [Qemu-devel] [PATCH 0/2] qapi: Add detection for the 'savevm' fix for blockdev Peter Krempa
2019-09-17 15:49 ` [Qemu-devel] [PATCH 1/2] qapi: Add feature flags to commands in qapi introspection Peter Krempa
2019-09-17 16:03 ` Eric Blake
2019-09-17 15:49 ` [Qemu-devel] [PATCH 2/2] qapi: Allow introspecting fix for savevm's cooperation with blockdev Peter Krempa
2019-09-17 16:33 ` Eric Blake [this message]
2019-09-18 8:22 ` Kevin Wolf
2019-09-18 8:32 ` Peter Krempa
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=8eae6ac1-bbc1-63ba-14b2-779ed3f42a29@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).