From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
mdbooth@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Enhancing qemu-img convert format compatibility
Date: Mon, 18 Apr 2011 12:12:56 +0100 [thread overview]
Message-ID: <BANLkTim7ktFXSrVpSGgX2encjg1-0c75_Q@mail.gmail.com> (raw)
In-Reply-To: <20110418110351.GA27395@amd.home.annexia.org>
On Mon, Apr 18, 2011 at 12:03 PM, Richard W.M. Jones <rjones@redhat.com> wrote:
> On Mon, Apr 18, 2011 at 11:18:42AM +0100, Stefan Hajnoczi wrote:
>> qemu-img is a pretty good Rosetta stone for image formats but it is
>> missing support some format versions. In order to bring qemu-img
>> up-to-date with the latest disk image formats we will need to find
>> specific image files and/or software versions that produce image files
>> that qemu-img cannot understand today.
>>
>> If you have image files that qemu-img is unable to manipulate, please
>> respond with details of the software and version used to produce the
>> image. If possible please include a link to a small example image
>> file.
>
> Stefan,
>
> We found that using the vSphere 4.x "Export to OVF" option would
> produce a VMDK file that qemu-img could not convert to raw.
Excellent, thanks for sharing this. I hope we can build a picture of
where there is missing support and address this in the "Improved Image
Format Compatiblity" project for Google Summer of Code:
http://wiki.qemu.org/Google_Summer_of_Code_2011#Improved_image_format_compatibility
Stefan
prev parent reply other threads:[~2011-04-18 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 10:18 [Qemu-devel] Enhancing qemu-img convert format compatibility Stefan Hajnoczi
2011-04-18 11:03 ` Richard W.M. Jones
2011-04-18 11:12 ` Stefan Hajnoczi [this message]
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=BANLkTim7ktFXSrVpSGgX2encjg1-0c75_Q@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=mdbooth@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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).