From: Stefan Hajnoczi <stefanha@gmail.com>
To: Mike Young <myoung@wildernessvoice.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Derivative snapshots or snapshots for versioning
Date: Wed, 25 May 2011 08:21:33 +0100 [thread overview]
Message-ID: <BANLkTimTDn6NHD6cmvRFD_Lg86MzvAJFpg@mail.gmail.com> (raw)
In-Reply-To: <CA013583.4446F%myoung@wildernessvoice.com>
On Tue, May 24, 2011 at 5:14 PM, Mike Young <myoung@wildernessvoice.com> wrote:
> I'm trying to see if I can I do a derivative snapshot as a means of
> versioning. I wish to do this vs dd or cp as it's much faster. I do not
> intend to apply a snapshot back to an original volume.
> So, let's say I have original_volume.img and I create a snapshot using the
> –b option: "qemu-img create –f qcow2 –b original_volume.img snapshot1.img",
I would not call the new file "snapshot1.img" since the frozen disk
image should be original_volume.img. You can write to snapshot1.img
but it is not safe to original_volume.img because snapshot1.img will
then become inconsistent (you've changed the blocks that it was based
on).
> but now I wish to create a snapshot2 from snapshot1.img. Is there a way to
> do this?
qemu-img create -f qcow2 -b snapshot1.img snapshot2.img
Note that you should not write to snapshot1.img anymore. However, you
could say:
qemu-img create -f qcow2 -b snapshot1.img snapshot2a.img
qemu-img create -f qcow2 -b snapshot1.img snapshot2b.img
Don't write to snapshot1.img but you can run VMs using snapshot2a.img
and snapshot2b.img independently.
> Also, is there a way to generate 100% snapshot of the original volume (an
> exact replica), so that a 40G original results in a 40G snapshot?
cp original.qcow2 clone.qcow2
Stefan
next prev parent reply other threads:[~2011-05-25 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 16:14 [Qemu-devel] Derivative snapshots or snapshots for versioning Mike Young
2011-05-25 7:21 ` Stefan Hajnoczi [this message]
2011-05-25 11:50 ` Mike Young
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=BANLkTimTDn6NHD6cmvRFD_Lg86MzvAJFpg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=myoung@wildernessvoice.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).