It seems that OVF import only supports the stream format and not monolithicSparse,
could someone confrm that?
I ask as we are trying to give a hand-crafted OVF to ESXi for import. We use qemu-img
to create the vmdk and monolithicSparse is all qemu can create. ESXi complains that
One option is maybe is to use vmkfstools <your sparse.vmdk> <new.vmdk> to do
the conversion, but here is the kicker - we have to do this conversion on an old linux
build server with no root access to install nice new tools and we would need to ssh out
to our ESXi box to do the conversion, which we want to avoid as we have thousands of
potential users building this thing...
If we could install vmkfstools with non root access, that might be an option. Or we go
off and try to extend qemu-img as a last resort.
Open to any and all ideas here as we're stumped with lack of ability to create something
that will pass OVF format checks.
Really the plan is still (at some point) to write extensions for qemu to do this which
would have the benefit of qemu being able to support a wider variety of vmdk disk
I don't see any other option (other than vmware fixing this!)
Quite why vsphere/esxi has this restriction is beyond me - it plainly supports the
monolithic types, just on import it wants to be fussy
If you want to mail me to discuss more: n m c g i l firstname.lastname@example.org
Try cloning the vmdk. I had to clone the disk to a current vmdk version before esxi5.1 would recognize it and boot properly. See KB 1028042
To convert a virtual machine disk from one type to another: