From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Bug 1253465 <1253465@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1253465] [NEW] qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3
Date: Thu, 21 Nov 2013 17:27:10 +0800 [thread overview]
Message-ID: <528DD1EE.5090508@redhat.com> (raw)
In-Reply-To: <20131121083716.GD27039@stefanha-thinkpad.redhat.com>
On 2013年11月21日 16:37, Stefan Hajnoczi wrote:
> On Wed, Nov 20, 2013 at 11:00:14PM -0000, adrelanos wrote:
>> qemu-img convert in.vmdk -O RAW out.img
>>
>> Fails with:
>> qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3
>>
>> qemu-img version 1.6.1
>
> This is a known issue. VMware has not released the file format
> specification for VMDK version 3. At this point the information needed
> to implement version 3 support is not publicly available.
>
> If you are aware of open source software which already supports version
> 3, please let us know!
>
> Fam: Do you have instructions for exporting version 2 images from
> VMware?
>
Unfortunately I don't know there's a way to export version 2.
But you can still copy out the "raw" formatted VMDK in vSphere datastore
browser (or use ESX shell), I've posted instructions here:
http://famz.cn/?p=45
This is also the way that virt-v2v extracts guest images.
Fam
next prev parent reply other threads:[~2013-11-21 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 23:00 [Qemu-devel] [Bug 1253465] [NEW] qemu-img: 'image' uses a vmdk feature which is not supported by this qemu version: VMDK version 3 adrelanos
2013-11-21 8:37 ` Stefan Hajnoczi
2013-11-21 9:27 ` Fam Zheng [this message]
2017-01-07 21:36 ` [Qemu-devel] [Bug 1253465] " Patrick Schleizer
2017-01-08 1:42 ` Fam Zheng
2017-02-01 9:19 ` Thomas Huth
2017-04-03 4:17 ` Launchpad Bug Tracker
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=528DD1EE.5090508@redhat.com \
--to=famz@redhat.com \
--cc=1253465@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).