From: "Denis V. Lunev" <den@openvz.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] RESUME blk: do not select PFLASH device for internal snapshot
Date: Thu, 14 Jan 2016 14:33:04 +0300 [thread overview]
Message-ID: <56978770.4070208@openvz.org> (raw)
In-Reply-To: <1452578622-4492-1-git-send-email-den@openvz.org>
On 01/12/2016 09:03 AM, Denis V. Lunev wrote:
> There is a long-long story. OVMF VMs can not be snapsotted using
> 'virsh snapshot' as they have "pflash" device which is configured as
> "raw" image. There was a discussion in the past about that.
results of the discussion are available in this submission:
[PATCH v5 0/8] QMP wrappers for VM snapshot operations
prev parent reply other threads:[~2016-01-14 11:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 6:03 [Qemu-devel] [PATCH 1/1] blk: do not select PFLASH device for internal snapshot Denis V. Lunev
2016-01-12 14:16 ` Kevin Wolf
2016-01-12 14:59 ` Paolo Bonzini
2016-01-12 15:13 ` Denis V. Lunev
2016-01-12 15:16 ` Peter Maydell
2016-01-12 15:26 ` Kevin Wolf
2016-01-12 15:20 ` Kevin Wolf
2016-01-12 15:35 ` Paolo Bonzini
2016-01-12 15:47 ` Denis V. Lunev
2016-01-12 16:35 ` Denis V. Lunev
2016-01-12 16:52 ` Kevin Wolf
2016-01-12 16:58 ` Denis V. Lunev
2016-01-12 17:40 ` Markus Armbruster
2016-01-12 17:50 ` Kevin Wolf
2016-01-12 17:54 ` Denis V. Lunev
2016-01-13 8:09 ` Markus Armbruster
2016-01-13 10:43 ` Laszlo Ersek
2016-01-12 17:53 ` Denis V. Lunev
2016-01-13 10:41 ` Laszlo Ersek
2016-01-13 10:37 ` Laszlo Ersek
2016-01-13 11:11 ` Denis V. Lunev
2016-01-13 12:15 ` Laszlo Ersek
2016-01-12 15:10 ` Denis V. Lunev
2016-01-12 15:28 ` Kevin Wolf
2016-01-14 11:33 ` Denis V. Lunev [this message]
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=56978770.4070208@openvz.org \
--to=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).