From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>,
Richard Palethorpe <richiejp@f-m.fm>,
qemu-devel@nongnu.org
Cc: armbru@redhat.com, dgilbert@redhat.com, rpalethorpe@suse.com,
quintela@redhat.com, Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] Add save-snapshot, load-snapshot and delete-snapshot to QAPI
Date: Thu, 11 Jan 2018 13:46:38 +0100 [thread overview]
Message-ID: <5cf19623-72ac-fb8b-2054-a60d42419ec6@redhat.com> (raw)
In-Reply-To: <fd5f5f12-e081-6f19-54af-3b560139bb78@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On 2018-01-08 14:52, Eric Blake wrote:
> On 01/07/2018 06:23 AM, Richard Palethorpe wrote:
>> Add QAPI wrapper functions for the existing snapshot functionality. These
>> functions behave the same way as the HMP savevm, loadvm and delvm
>> commands. This will allow applications, such as OpenQA, to programmatically
>> revert the VM to a previous state with no dependence on HMP or qemu-img.
>
> That's already possible; libvirt uses QMP's human-monitor-command to
> access these HMP commands programmatically.
>
> We've had discussions in the past about what it would take to have
> specific QMP commands for these operations; the biggest problem is that
> these commands promote the use of internal snapshots, and there are
> enough performance and other issues with internal snapshots that we are
> not yet ready to commit to a long-term interface for making their use
> easier. At this point, our recommendation is to prefer external snapshots.
We already have QMP commands for internal snapshots, though. Isn't the
biggest issue that savevm takes too much time to be a synchronous QMP
command?
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2018-01-11 12:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 12:23 [Qemu-devel] [PATCH 1/2] Add save-snapshot, load-snapshot and delete-snapshot to QAPI Richard Palethorpe
2018-01-07 12:23 ` [Qemu-devel] [PATCH 2/2] Add test cases for saving, loading and deleting snapshots using QAPI Richard Palethorpe
2018-01-08 13:52 ` [Qemu-devel] [PATCH 1/2] Add save-snapshot, load-snapshot and delete-snapshot to QAPI Eric Blake
2018-01-10 16:19 ` Richard Palethorpe
2018-01-10 16:48 ` Eric Blake
2018-02-03 13:28 ` Markus Armbruster
2018-01-11 12:46 ` Max Reitz [this message]
2018-01-11 13:04 ` Daniel P. Berrange
2018-01-11 13:23 ` Dr. David Alan Gilbert
2018-01-11 13:36 ` Daniel P. Berrange
2018-01-11 16:55 ` Juan Quintela
2018-02-12 13:25 ` Richard Palethorpe
2018-02-13 10:50 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2018-02-13 11:43 ` Dr. David Alan Gilbert
2018-02-13 11:51 ` Daniel P. Berrangé
2018-02-13 13:20 ` Kevin Wolf
2018-02-13 13:25 ` Daniel P. Berrangé
[not found] ` <20180213143001.GA2354@rkaganb.sw.ru>
2018-02-13 14:36 ` Daniel P. Berrangé
2018-02-13 14:45 ` Kevin Wolf
2018-02-13 14:48 ` Daniel P. Berrangé
2018-02-13 14:51 ` Denis V. Lunev
2018-02-13 14:59 ` Dr. David Alan Gilbert
2018-02-13 15:01 ` Denis V. Lunev
2018-02-13 15:05 ` Dr. David Alan Gilbert
[not found] ` <20180213151352.GF2307@rkaganb.sw.ru>
2018-02-13 15:27 ` Dr. David Alan Gilbert
2018-02-13 15:29 ` Denis V. Lunev
2018-02-13 16:01 ` Denis Plotnikov
2018-02-15 15:21 ` Dr. David Alan Gilbert
2018-02-13 16:46 ` Eric Blake
2018-02-13 19:45 ` Denis V. Lunev
2018-02-13 14:43 ` Kevin Wolf
2018-02-13 14:50 ` Denis V. Lunev
2018-02-13 14:58 ` Daniel P. Berrangé
2018-02-13 15:23 ` Kevin Wolf
2018-02-13 15:30 ` Daniel P. Berrangé
2018-02-13 15:51 ` Kevin Wolf
2018-02-13 16:14 ` Denis Plotnikov
2018-01-10 6:17 ` [Qemu-devel] " Peter Xu
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=5cf19623-72ac-fb8b-2054-a60d42419ec6@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richiejp@f-m.fm \
--cc=rpalethorpe@suse.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).