qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marc Bevand <m.bevand@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC] Allow 'qemu-img convert' to preserve the	backing file
Date: Fri, 30 May 2008 08:43:18 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080530T083619-228@post.gmane.org> (raw)
In-Reply-To: 18493.11264.309358.483993@mariner.uk.xensource.com

Ian Jackson <Ian.Jackson <at> eu.citrix.com> writes:
> 
> If there were a generic way to ask a block driver for a cow format
> what the backing image filename was, then the block driver core could
> do the opening itself.  That would make everything a bit simpler as it
> would move code out of the invididual drivers.

I am done. I implemented this feature in a generic way as you suggested. I am
going to send the patch in a separate email. I am confident in its robustness,
so far I have successfully converted more than 20 copy-on-write qcow1 images to
the qcow2 format. Different sizes, different "ages" (between 0 and 90% of the
sectors rewritten in the COW copies), different guest filesystems, etc. I have
verified no corruption occured by making sure a final conversion to the raw
format led to the expected MD5 checksum.

-marc

  reply	other threads:[~2008-05-30  8:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28  5:02 [Qemu-devel] [RFC] Allow 'qemu-img convert' to preserve the backing file Marc Bevand
2008-05-28  9:53 ` Ian Jackson
2008-05-28  9:55   ` Ian Jackson
2008-05-30  8:43     ` Marc Bevand [this message]
2008-05-30  9:21       ` [Qemu-devel] [PATCH] New qemu-img convert -B option to preserve the COW aspect of images and/or re-base them Marc Bevand
2008-05-28 11:58   ` [Qemu-devel] [RFC] Allow 'qemu-img convert' to preserve the backing file Jamie Lokier
2008-05-28 13:22     ` Ian Jackson

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=loom.20080530T083619-228@post.gmane.org \
    --to=m.bevand@gmail.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).