From: "Richard W.M. Jones" <rjones@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img: Implement 'diff' operation.
Date: Thu, 17 May 2012 15:01:36 +0100 [thread overview]
Message-ID: <20120517140136.GD15276@amd.home.annexia.org> (raw)
In-Reply-To: <CAFEAcA_KC9nJht9Q7ZmZ-E_wYapdNNE-X+7JXEbDgxvzzgSE5A@mail.gmail.com>
On Thu, May 17, 2012 at 02:52:56PM +0100, Peter Maydell wrote:
> On 17 May 2012 14:44, Richard W.M. Jones <rjones@redhat.com> wrote:
> > From: "Richard W.M. Jones" <rjones@redhat.com>
> >
> > This produces a qcow2 file which is the different between
> > two disk images. ie, if:
> >
> > original.img - is a disk image (in any format)
> > modified.img - is a modified version of original.img
> >
> > then:
> >
> > qemu-img diff -b original.img modified.img diff.qcow2
> >
> > creates 'diff.qcow2' which contains just the differences. Note that
> > 'diff.qcow2' has 'original.img' set as the backing file.
>
> Any chance of some more detailed explanation in the docs patch
> about what this actually means and why it's useful? I spent
> several minutes going "huh, does it even mean anything to
> calculate the difference between two binary disk images?"
> before realising that it's the presence of the backing file
> that makes it actually make sense...
Well I'll say first of all that I was asked to implement this by a
colleague. Personally, I'm far more organized than this, and I always
use snapshots and backing files if I want to create an efficient COW
from a base template :-)
However my colleague has got himself into a situation where he has
copied (ie. "cp" or equivalent) a guest several times from a template,
and these guests have been running independently. He now wants to
conserve disk space by turning this situation back into one where he
has one backing file + several COW copies.
To do this, he can (with this patch) do:
qemu-img diff -b base.img the_copied_guest.img guest.qcow2
rm the_copied_guest.img
'guest.qcow2' will (in theory at least) be much smaller than the
copied guests he has right now.
Does that make sense?
[BTW I'm still working on this. There are a few spelling mistakes and
it needs a lot more testing. This patch is just for comment at the
moment.]
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
next prev parent reply other threads:[~2012-05-17 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 13:44 [Qemu-devel] [PATCH] qemu-img: Implement 'diff' operation Richard W.M. Jones
2012-05-17 13:52 ` Peter Maydell
2012-05-17 13:58 ` Eric Blake
2012-05-17 14:01 ` Richard W.M. Jones [this message]
2012-05-17 13:57 ` Eric Blake
2012-05-17 14:58 ` Richard W.M. Jones
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=20120517140136.GD15276@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=peter.maydell@linaro.org \
--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).