qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] qemu-img convert to VMDK


From: Guilherme Moro
Subject: Re: [Qemu-devel] qemu-img convert to VMDK
Date: Mon, 16 Oct 2017 12:16:19 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 10/14/2017 10:45 AM, Fam Zheng wrote:
On Fri, 10/13 15:20, Guilherme Moro wrote:
Hi,

I'm trying to convert some images from raw to vmdk to run in a ESXi6.5
server but I need to rectify the image before being able to run.

The scenario goes like that:

qemu-img convert -f raw image.raw -O vmdk -o compat6 image.vmdk
ESXi complains with "Failed - File system specific implementation of
LookupAndOpen"[file] failed
running vmkfstools -x repair on the image make it bootable

  I checked the changes, vmkfstools is basically removing the second
descriptor from the end of the file, I'm not familiar enough with the code
and the format to know what this means, maybe compat6 should make qemu-img
avoid to put that in the end of the file (again, mostly guessing).

Anyway we would need an option to make sure that this second descriptor does
not end in the final image.
What do you mean by "second descriptor"? The one at offset 0x200? But other than
this descriptor I don't see a second one. Maybe I'm missing something?

Fam

Hi,

maybe there's something else happening on my side, I will double check, but my converted image have descriptors in the end and in the beginning of the file:

linux-kv33:/data/NFS # tail -c 512 SLES15-JeOS-for-VMware.x86_64-1.3.0-Build.vmdk
encoding="UTF-8"
# Disk DescriptorFile
version=1
CID=f7105bc0
parentCID=ffffffff
createType="monolithicSparse"

# Extent description
RW 50331648 SPARSE "SLES15-JeOS-for-VMware.x86_64-1.3.0.vmdk"

# The Disk Data Base
#DDB

ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "49932"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.adapterType = "ide"

ddb.toolsInstallType = "4"
ddb.toolsVersion = "10282"


linux-kv33:/data/NFS # head -c 1024 SLES15-JeOS-for-VMware.x86_64-1.3.0-Build.vmdk
KDMV�
             �

# Disk DescriptorFile
version=1
CID=f7105bc0
parentCID=ffffffff
createType="monolithicSparse"

# Extent description
RW 50331648 SPARSE "SLES15-JeOS-for-VMware.x86_64-1.3.0.vmdk"

# The Disk Data Base
#DDB

ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "49932"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.adapterType = "ide"


Again, not acquainted with the code as much, but the code seems to indicate VMDK4 files having a footer. Specifically the function vmdk_open_vmdk4 inside block/vmdk.c .

I couldn't trace further if there's any other code *writing*  a footer.

Guilherme



reply via email to

[Prev in Thread] Current Thread [Next in Thread]