From: Eric Blake <eblake@redhat.com>
To: lihuiba <magazine.lihuiba@163.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qcow2 snapshot + resize
Date: Tue, 5 Jan 2016 06:55:56 -0700 [thread overview]
Message-ID: <568BCB6C.7010709@redhat.com> (raw)
In-Reply-To: <6ca84848.f052.15211b20317.Coremail.magazine.lihuiba@163.com>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
On 01/05/2016 05:10 AM, lihuiba wrote:
>>> In our production environment, we need to extend a qcow2 image with
>>> snapshots in it.
>> The thing is that one would need to update all the inactive L1 tables. I
>> don't think it should be too difficult, it's just that apparently so far
>> nobody ever had the need for this feature.
Is resizing a snapshot really what you want? Ideally, a snapshot tracks
the data from a point in time, including the metadata of the size being
tracked at that time. Extending the snapshots then reverting to that
snapshot means your guest would see a larger disk on revert than it did
at the time the snapshot was created, which guests might not handle very
well.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-01-05 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 12:10 [Qemu-devel] qcow2 snapshot + resize lihuiba
2016-01-05 13:55 ` Eric Blake [this message]
2016-01-05 17:36 ` John Snow
2016-01-06 2:50 ` lihuiba
2016-01-06 15:04 ` Eric Blake
2016-01-06 16:20 ` Max Reitz
2016-01-06 16:28 ` Eric Blake
2016-01-06 16:30 ` Max Reitz
2016-01-14 12:17 ` Kevin Wolf
2016-01-19 2:42 ` lihuiba
-- strict thread matches above, loose matches on Subject: below --
2015-12-29 9:38 lihuiba
2016-01-04 17:38 ` Max Reitz
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=568BCB6C.7010709@redhat.com \
--to=eblake@redhat.com \
--cc=magazine.lihuiba@163.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).