From: "Denis V. Lunev" <den@openvz.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: 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] blk: do not select PFLASH device for internal snapshot
Date: Tue, 12 Jan 2016 18:10:26 +0300 [thread overview]
Message-ID: <56951762.9070603@openvz.org> (raw)
In-Reply-To: <20160112141607.GD4841@noname.redhat.com>
On 01/12/2016 05:16 PM, Kevin Wolf wrote:
> Am 12.01.2016 um 07:03 hat Denis V. Lunev geschrieben:
>> 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.
>>
>> Good description has been provided on topic by Laszlo Ersek, see below:
>>
>> "It is true that a pflash drive is "just a drive" *internally* to QEMU.
>> It is also true that it more or less takes the same -drive options as
>> any other *disk* drive. But those facts are just implementation details.
>>
>> The relevant trait of pflash storage files is that they are not *disk
>> images*, on the libvirt domain XML level. They are not created in
>> storage pools, you cannot specify their caching attributes, you don't
>> specify their guest-visible frontend in separation (like virtio-blk /
>> virtio-scsi / pflash). Those details are hidden (on purpose).
>>
>> Consequently, pflash storage files are expected to be *small* in size
>> (in practice: identically sized to the varstore template they are
>> instantiated from). They are created under /var/lib/libvirt/qemu/nvram.
>> Although you can edit their path in the domain XML, they are not
>> considered disks."
>>
>> Thus we should avoid selection of "pflash" drives for VM state saving.
>>
>> For now "pflash" is read-write raw image as it configured by libvirt.
>> Thus there are no such images in the field and we could safely disable
>> ability to save state to those images inside QEMU.
> This is obviously broken. If you write to the pflash, then it needs to
> be snapshotted in order to keep a consistent state.
>
> If you want to avoid snapshotting the image, make it read-only and it
> will be skipped even today.
>
> Kevin
you interpret the patch a bit wrong.
It will be snapshoted once I'll raw image with qcow2 image, but this image
will not be selected for state saving, i.e. it will remain compact.
Den
next prev parent reply other threads:[~2016-01-12 15:10 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 [this message]
2016-01-12 15:28 ` Kevin Wolf
2016-01-14 11:33 ` [Qemu-devel] [PATCH 1/1] RESUME " Denis V. Lunev
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=56951762.9070603@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).