qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, 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 18:12:30 +0200	[thread overview]
Message-ID: <503B9C6E.30604@redhat.com> (raw)
In-Reply-To: <CAJSP0QUx8E5J_RGct8uZbxWG3Y8gEBQyEne7uMEenp4h2T0FaA@mail.gmail.com>

Am 27.08.2012 11:04, schrieb Stefan Hajnoczi:
> On Sun, Aug 26, 2012 at 10:56 AM, Alexandre DERUMIER
> <aderumier@odiso.com> wrote:
>> It is possible to achieve the same behaviour with external snapshot ? (I would like to do it online)
>> I don't see how I can rollback to the point of time of the snapshot.
> 
> The snapshot only captures the contents of the disk.  Rollback does
> not make sense without shutting down the guest.  The OS/file system
> would be very confused if the disk contents changed underneath it.
> 
> Existing hotplug can be used.  For example, if we have an external
> snapshot of a virtio-blk drive, we can use hotplug to remove the
> drive, choose the snapshot file and attach it again.  This only works
> for "data" drives, the root file system usually cannot be changed
> while the guest is running.
> 
> You may also wish to look at libvirt for higher level snapshot primitives.
> 
>> 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.

I wonder why nobody mentioned the savevm/loadvm monitor commands, which
do take an internal snapshot of a running VM. They just aren't live, and
when writing out the whole VM state this matters indeed.

However, if a disk-only snapshot is enough (this is what qemu-img
snapshot -c would produce), it would be a trivial patch to add a savevm
option to omit the VM state - and even though the snapshot is then still
not really performed in the background, it should be quick enough to be
workable.

Of course, the other thing is that external snapshots are way better
tested that internal ones. So possibly you need to put some effort in
testing and possibly fixing if you go for internal snapshots (I would
really like to see internal snapshots improved; even just that they can
be deleted without major hassle makes them the better option in many cases)

Kevin

  parent reply	other threads:[~2012-08-27 16:12 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
2012-08-27 16:12             ` Kevin Wolf [this message]
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=503B9C6E.30604@redhat.com \
    --to=kwolf@redhat.com \
    --cc=aderumier@odiso.com \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=pbonzini@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).