From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: Jeff Cody <jcody@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qcow2: online snasphots : internal vs external ?
Date: Sat, 25 Aug 2012 15:01:45 +0100 [thread overview]
Message-ID: <CAJSP0QW1cJnGyOh3-4RNioD+a0dX69fxZgfB4wt7v9SNvxgqKg@mail.gmail.com> (raw)
In-Reply-To: <49196ce6-4486-44b9-af25-28fbcae4efef@mailpro>
On Sat, Aug 25, 2012 at 2:25 PM, Alexandre DERUMIER <aderumier@odiso.com> wrote:
> I'm currently looking to add live snapshot support to proxmox kvm distribution.
>
> Is it possible to use internal snapshots on a running guest running qcow2 disk?
> (qemu-img snapshot -c ) ?
No. qemu-img should not be used if the guest is running.
> Or do I need to use external snapshots with qmp blockdev-snapshot-sync ?
> (Seem more complex to delete old snapshots)
External qcow2/qed snapshots can be created while the guest is running
using snapshot-blockdev-sync, but it is not yet possible to flatten
the chain arbitrarily while the guest is running.
You can use block-stream to populate the top-most image file with data
from its backing image chain. Jeff Cody is working on block-commit
which allows merging down (this is the opposite of block-stream). The
advantage with block-commit is that backing images are often smaller
than the image file, it's therefore more efficient to copy less data
down instead of copying the backing image up into the image file.
Stefan
next prev parent reply other threads:[~2012-08-25 14:01 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 [this message]
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
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=CAJSP0QW1cJnGyOh3-4RNioD+a0dX69fxZgfB4wt7v9SNvxgqKg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=aderumier@odiso.com \
--cc=jcody@redhat.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).