From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Jeff Cody <jcody@redhat.com>, Eric Blake <eblake@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexandre DERUMIER <aderumier@odiso.com>
Subject: Re: [Qemu-devel] qcow2: online snasphots : internal vs external ?
Date: Mon, 27 Aug 2012 12:13:15 +0200 [thread overview]
Message-ID: <503B483B.2070103@redhat.com> (raw)
In-Reply-To: <CAJSP0QUx8E5J_RGct8uZbxWG3Y8gEBQyEne7uMEenp4h2T0FaA@mail.gmail.com>
Il 27/08/2012 11:04, Stefan Hajnoczi ha scritto:
>> > Also I see that snapshot_blkdev qmp command give in his description:
>> > "Otherwise the snapshot will be internal! (currently unsupported)."
>> >
>> > is Live internal snapshots on the roadmap ?
> I'm not aware of anyone working on adding internal snapshot in the
> near future. Patches are welcome.
The main problem with internal snapshots is that it's difficult to work
with two snapshots at the same time, especially if you need to write to
two of them. IIUC this is why people concentrated more on external
snapshots.
It's not intrinsic to internal snapshots, more like a wart of the
implementation, but not an easily fixed one.
Paolo
next prev parent reply other threads:[~2012-08-27 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10f390de-14b5-45c6-8d24-202e40cc2598@mailpro>
2012-08-25 13:25 ` [Qemu-devel] qcow2: online snasphots : internal vs external ? Alexandre DERUMIER
2012-08-25 14:01 ` Stefan Hajnoczi
2012-08-25 17:06 ` Alexandre DERUMIER
2012-08-26 7:07 ` Stefan Hajnoczi
2012-08-26 9:56 ` Alexandre DERUMIER
2012-08-27 9:04 ` Stefan Hajnoczi
2012-08-27 9:26 ` Alexandre DERUMIER
2012-08-27 10:10 ` Paolo Bonzini
2012-08-27 13:12 ` Alexandre DERUMIER
2012-08-27 10:13 ` Paolo Bonzini [this message]
2012-08-27 16:12 ` Kevin Wolf
2012-08-28 8:11 ` Stefan Hajnoczi
2012-08-28 8:22 ` Alexandre DERUMIER
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=503B483B.2070103@redhat.com \
--to=pbonzini@redhat.com \
--cc=aderumier@odiso.com \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).