From: Max Reitz <mreitz@redhat.com>
To: lihuiba <magazine.lihuiba@163.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: Re: [Qemu-devel] qcow2 snapshot + resize
Date: Mon, 4 Jan 2016 18:38:08 +0100 [thread overview]
Message-ID: <568AAE00.7040800@redhat.com> (raw)
In-Reply-To: <bc4838b.c8a7.151ed1a4a56.Coremail.magazine.lihuiba@163.com>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
On 29.12.2015 10:38, lihuiba wrote:
> Hi,
>
> In our production environment, we need to extend a qcow2 image with
> snapshots in it. This feature, however, is not implemented yet.
>
> So I want to ask, if this feature is under active development?
No, it is not.
> How can I
> help with this feature?
Well, you can implement it. ;-)
> It seems that, this feature is not too difficult as long as cluster_size
> is kept unchanged. Is this correct?
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.
I can take a look, but I can't say anything about whether or when
anything will come out of it.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-04 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 9:38 [Qemu-devel] qcow2 snapshot + resize lihuiba
2016-01-04 17:38 ` Max Reitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-05 12:10 lihuiba
2016-01-05 13:55 ` Eric Blake
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
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=568AAE00.7040800@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.