From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: SAURAV LAHIRI <saurav_lahiri@yahoo.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Issue with snapshot outside qcow2 disk - qemu 0.14.0
Date: Thu, 10 Mar 2011 10:59:04 +0100 [thread overview]
Message-ID: <4D78A0E8.7000606@redhat.com> (raw)
In-Reply-To: <AANLkTinkrhi0si34BRdhtx93uGiXMwyRMCW6q9vHDc6p@mail.gmail.com>
On 03/10/11 10:58, Stefan Hajnoczi wrote:
> On Thu, Mar 10, 2011 at 9:32 AM, Jes Sorensen <Jes.Sorensen@redhat.com> wrote:
>> On 03/10/11 10:27, Stefan Hajnoczi wrote:
>>> I have CCed Jes who has been working on a live snapshot mechanism. He
>>> recently added the snapshot_blkdev monitor command that takes a
>>> snapshot of a block device while the VM is running. A new image file
>>> is created based off the original image file (which will no longer be
>>> modified), all new disk writes go to the new image file. It is safe
>>> to perform read-only access to the original image file. There
>>> currently is no support to merge the snapshot changes back into the
>>> original image while the VM is running, but I think that is the next
>>> planned step.
>>
>> Yes, keep in mind that the live snapshot is only for external snapshot
>> files, it doesn't deal with internal snapshots.
>
> Yep, that's why I'm interested in Saurav's use case. Many use cases
> work with either internal or external snapshot but it depends on the
> details.
Actually I think there's very little reason to keep internal snapshot
support. It doesn't buy us much, but it adds unnecessary complexity.
Cheers,
Jes
next prev parent reply other threads:[~2011-03-10 9:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 18:06 [Qemu-devel] Issue with snapshot outside qcow2 disk - qemu 0.14.0 SAURAV LAHIRI
2011-03-09 19:53 ` Stefan Hajnoczi
2011-03-10 1:51 ` SAURAV LAHIRI
2011-03-10 9:27 ` Stefan Hajnoczi
2011-03-10 9:32 ` Jes Sorensen
2011-03-10 9:58 ` Stefan Hajnoczi
2011-03-10 9:59 ` Jes Sorensen [this message]
2011-03-10 19:57 ` SAURAV LAHIRI
2011-03-10 21:04 ` Stefan Hajnoczi
2011-03-11 6:31 ` Jes Sorensen
2011-03-11 9:39 ` SAURAV LAHIRI
2011-03-11 9:50 ` Jes Sorensen
2011-03-11 11:55 ` Stefan Hajnoczi
2011-03-11 19:12 ` SAURAV LAHIRI
2011-03-11 17:12 ` SAURAV LAHIRI
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=4D78A0E8.7000606@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=saurav_lahiri@yahoo.com \
--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).