From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34386) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMz27-0006Mj-BQ for qemu-devel@nongnu.org; Thu, 19 May 2011 04:56:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QMz26-0002FF-C0 for qemu-devel@nongnu.org; Thu, 19 May 2011 04:56:39 -0400 Received: from mail-gy0-f173.google.com ([209.85.160.173]:37321) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMz26-0002F1-9a for qemu-devel@nongnu.org; Thu, 19 May 2011 04:56:38 -0400 Received: by gyg4 with SMTP id 4so957590gyg.4 for ; Thu, 19 May 2011 01:56:37 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20110519041753.18011.86775.malonedeb@wampee.canonical.com> References: <20110519041753.18011.86775.malonedeb@wampee.canonical.com> <20110519041753.18011.86775.malonedeb@wampee.canonical.com> Date: Thu, 19 May 2011 09:56:37 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Bug 784977] [NEW] qemu-img convert fails to convert, generates a 512byte file output List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bug 784977 <784977@bugs.launchpad.net> Cc: Feiran Zheng , qemu-devel@nongnu.org On Thu, May 19, 2011 at 5:17 AM, Andy Brook wrote: > Public bug reported: > > I have a Vmware image, so I have files like 'Ubuntu.vmdk', want to > convert to VirtualBox .vdi format using qemu, the first stage of > extracting the image with 'qemu-img convert Ubuntu.vmdk output.bin' just > generates a 512byte file: > > {quote} > # Disk DescriptorFile > version=3D1 > CID=3D36be9761 > parentCID=3Dffffffff > createType=3D"twoGbMaxExtentSparse" > > # Extent description > RW 4192256 SPARSE "Ubuntu-s001.vmdk" > RW 4192256 SPARSE "Ubuntu-s002.vmdk" > RW 4192256 SPARSE "Ubuntu-s003.vmdk" > RW 4192256 SPARSE "Ubuntu-s004.vmdk" > RW 4192256 SPARSE "Ubuntu-s005.vmdk" > RW 4192256 SPARSE "Ubuntu-s006.vmdk" > RW 4192256 SPARSE "Ubuntu-s007.vmdk" > RW 4192256 SPARSE "Ubuntu-s008.vmdk" > RW 4192256 SPARSE "Ubuntu-s009.vmdk" > RW 4192256 SPARSE "Ubuntu-s010.vmdk" > RW 20480 SPARSE "Ubunt > {quote} > > Here is the input Ubuntu.vmdk file: > {quote} > # Disk DescriptorFile > version=3D1 > CID=3D36be9761 > parentCID=3Dffffffff > createType=3D"twoGbMaxExtentSparse" > > # Extent description > RW 4192256 SPARSE "Ubuntu-s001.vmdk" > RW 4192256 SPARSE "Ubuntu-s002.vmdk" > RW 4192256 SPARSE "Ubuntu-s003.vmdk" > RW 4192256 SPARSE "Ubuntu-s004.vmdk" > RW 4192256 SPARSE "Ubuntu-s005.vmdk" > RW 4192256 SPARSE "Ubuntu-s006.vmdk" > RW 4192256 SPARSE "Ubuntu-s007.vmdk" > RW 4192256 SPARSE "Ubuntu-s008.vmdk" > RW 4192256 SPARSE "Ubuntu-s009.vmdk" > RW 4192256 SPARSE "Ubuntu-s010.vmdk" > RW 20480 SPARSE "Ubuntu-s011.vmdk" > > # The Disk Data Base > #DDB > > ddb.toolsVersion =3D "7240" > ddb.adapterType =3D "lsilogic" > ddb.geometry.sectors =3D "63" > ddb.geometry.heads =3D "255" > ddb.geometry.cylinders =3D "2610" > ddb.virtualHWVersion =3D "6" > {quote} > > No stack trace or other output was found. =A0Anything I can add (other > than the 20G VM image to reproduce and I'll be happy to provide) Please post the output of "qemu-img info Ubuntu.vmdk". I suspect this image file is not being recognized as vmdk and is being treated as a raw image, hence the literal copy of its 512-byte sector size contents. I have CCed Fam who is working on VMDK image format improvements and may be able to help here. Stefan