From: Eric Blake <eblake@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v3 3/3] qapi: Allow introspecting fix for savevm's cooperation with blockdev
Date: Thu, 10 Oct 2019 13:11:27 -0500 [thread overview]
Message-ID: <0785d26d-6495-3b23-40d7-a19bcd02181e@redhat.com> (raw)
In-Reply-To: <be94d24847d38cb5a1172ed22d0f86e7c0ec8562.1570705279.git.pkrempa@redhat.com>
On 10/10/19 6:05 AM, Peter Krempa wrote:
In addition to Markus' review,
> 'savevm' was buggy as it considered all monitor-owned block device nodes
> for snapshot. With introduction of -blockdev the common usage made all
With the introduction of -blockdev, the common usage
> nodes including protocol and backing file nodes monitor-owned and thus
nodes be monitor-owned
> considered for snapshot.
>
> This is a problem since the 'file' protocol nodes can't have internal
> snapshots and it does not make sense to take snapshot of nodes
> representing backing files.
>
> This was fixed by commit 05f4aced658a02b02 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 | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/qapi/misc.json b/qapi/misc.json
> index 6bd11f50e6..5d0070aa43 100644
> --- a/qapi/misc.json
> +++ b/qapi/misc.json
> @@ -1020,6 +1020,12 @@
> #
> # @cpu-index: The CPU to use for commands that require an implicit CPU
> #
> +# Features:
> +# @savevm-blockdev-monitor-nodes: If present, the HMP command savevm only
> +# snapshots monitor-owned nodes if they have no
> +# parents. This allows to use 'savevm' with
> +# -blockdev. (since 4.2)
s/to use/the use of/
> +#
> # Returns: the output of the command as a string
> #
> # Since: 0.14.0
> @@ -1047,7 +1053,8 @@
> ##
> { 'command': 'human-monitor-command',
> 'data': {'command-line': 'str', '*cpu-index': 'int'},
> - 'returns': 'str' }
> + 'returns': 'str',
> + 'features': [ 'savevm-blockdev-monitor-nodes' ] }
>
> ##
> # @change:
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-10-10 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 11:05 [PATCH v3 0/3] qapi: Add detection for the 'savevm' fix for blockdev Peter Krempa
2019-10-10 11:05 ` [PATCH v3 1/3] qapi: Add feature flags to commands in qapi Peter Krempa
2019-10-10 13:54 ` Markus Armbruster
2019-10-10 11:05 ` [PATCH v3 2/3] tests: qapi: Test 'features' of commands Peter Krempa
2019-10-10 13:53 ` Markus Armbruster
2019-10-11 7:46 ` Peter Krempa
2019-10-11 8:06 ` Markus Armbruster
2019-10-10 11:05 ` [PATCH v3 3/3] qapi: Allow introspecting fix for savevm's cooperation with blockdev Peter Krempa
2019-10-10 13:52 ` Markus Armbruster
2019-10-10 18:11 ` Eric Blake [this message]
2019-10-10 14:01 ` [PATCH v3 0/3] qapi: Add detection for the 'savevm' fix for blockdev Markus Armbruster
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=0785d26d-6495-3b23-40d7-a19bcd02181e@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.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).