From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H5dxY-0004Tw-ES for qemu-devel@nongnu.org; Sat, 13 Jan 2007 03:09:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H5dxU-0004Ph-Hm for qemu-devel@nongnu.org; Sat, 13 Jan 2007 03:09:50 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H5dxT-0004PK-GC for qemu-devel@nongnu.org; Sat, 13 Jan 2007 03:09:47 -0500 Received: from [64.233.182.184] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H5dxS-000656-IZ for qemu-devel@nongnu.org; Sat, 13 Jan 2007 03:09:47 -0500 Received: by nf-out-0910.google.com with SMTP id c31so2579552nfb for ; Sat, 13 Jan 2007 00:09:45 -0800 (PST) Message-ID: Date: Sat, 13 Jan 2007 10:09:42 +0200 From: Marius MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_61518_27555078.1168675782327" Subject: [Qemu-devel] bug in qemu-img ? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_61518_27555078.1168675782327 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, I hope you can enlight me a little bit :). I'm trying to use qemu-img to create two disk images: a base image and a snapshot image (diff image or copy on write, name it the way you want). I think either qemu-img has a bug if the snapshot image has type vmdk or this format is not supported/suitable for this. My script is: qemu-img create -f vmdk hda-base 1G qemu-img create -b hda-base -f vmdk hda-diff 1G The output is: Formating 'hda-base', fmt=vmdk, size=1048576 kB Formating 'hda-diff', fmt=vmdk, backing_file=hda-base, size=1048576 kB So, apparently everything went ok. However, in hda-diff file there is no reference to hda-base file (a binary comparison will reveal this fact). My question is: isn't there support for backing files if image type is VMDK? It would be very useful this if you want to mount the image in windows (using vmware mount utility). If vmdk image type doesn't support a backing file (case in which it would be nice for qemu-img to exit with an error), is there a way to mount a disk image in Windows without converting it first to vmdk (using qemu-img convert)? This operation is time consuming if the image is big. Marius ------=_Part_61518_27555078.1168675782327 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello,
I hope you can enlight me a little bit :).
I'm trying to use qemu-img to create two disk images: a base image and a snapshot image (diff image or copy on write, name it the way you want).
I think either qemu-img has a bug if the snapshot image has type vmdk or this format is not supported/suitable for this. My script is:

qemu-img create -f vmdk hda-base 1G
qemu-img create -b hda-base -f vmdk hda-diff 1G

The output is:

Formating 'hda-base', fmt=vmdk, size=1048576 kB
Formating 'hda-diff', fmt=vmdk, backing_file=hda-base, size=1048576 kB

So, apparently everything went ok. However, in hda-diff file there is no reference to hda-base file (a binary comparison will reveal this fact).
My question is: isn't there support for backing files if image type is VMDK?
It would be very useful this if you want to mount the image in windows (using vmware mount utility).

If vmdk image type doesn't support a backing file (case in which it would be nice for qemu-img to exit with an error), is there a way to mount a disk image in Windows without converting it first to vmdk (using qemu-img convert)? This operation is time consuming if the image is big.



Marius
------=_Part_61518_27555078.1168675782327--