On Mon, 09/26 12:56, Peter Lieven wrote: > Hi, > > > i have a VMDK file for a Cisco Prime software appliance that I cannot open in > Qemu, Virtualbox or any other tool except > > for ESXi. Qemu exits with an invalid footer message. At the expected position > and also at the end of the file seems to be > > no footer. The VMDK has a -flex in the filename? Is this anything new that we > can't handle in Qemu?
Looking at the code path it's possible that the image is not compliant to the spec, or using a newer version number that QEMU doesn't support. Could you hexdump the first and the last sectors for me to check? Fam > > > This here is the relevant part of the OVF description: > > > <References> > <File ovf:href="PI-VA-3.1.0.0.132-flex-disk1.vmdk" ovf:id="file1" > ovf:size="3792931840" /> > </References> > > <DiskSection> > <Info>Virtual disk information</Info> > <Disk ovf:capacity="300" ovf:capacityAllocationUnits="byte * 2^30" > ovf:diskId="vmdisk1" ovf:fileRef="file1" > ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"; > ovf:populatedSize="8525510083"/> > <Disk ovf:capacity="300" ovf:capacityAllocationUnits="byte * 2^30" > ovf:diskId="vmdisk-expp" > ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"; > ovf:populatedSize="8525510083"/> > <Disk ovf:capacity="600" ovf:capacityAllocationUnits="byte * 2^30" > ovf:diskId="vmdisk-std" > ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"; > ovf:populatedSize="8525510083"/> > <Disk ovf:capacity="900" ovf:capacityAllocationUnits="byte * 2^30" > ovf:diskId="vmdisk-pro" > ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"; > ovf:populatedSize="8525510083"/> > </DiskSection> > > > Thanks, > > Peter >
