Hello, Can you provide more details how you performed the conversion and export? The size could be due to it being thin provisioned. I guess you could just take the vmdk image from VMware and convert it to qcow2 with something like this: qemu-img convert -p -f vmdk -O qcow2 testvm.vmdk testvm.qcow2 You then create a VM on ovirt with the same os type and try and attach the qcow2 file to it. Chances are that the machine will boot and adapt :-)

In my experience OVA exports and imports saw very little QA, even within oVirt itself, right up to OVA exports full of zeros on the last 4.3 release (in preparation for a migration to 4.4). The OVA format also shows very little practical interoperatbility, I've tried and failed in pretty much every direction between VMware, oVirt/RHV, VirtualBox, Xcp-ng and Proxmox. So transporting the disk images and recreating the machine is certainly the more promising option and something that I've used myself, where the guest OS was ready to accept that. Sparse images are another issue, as you have noticed, especially since the normal upload/import interfaces love to expand them. So if there is any resizing to be done, best do it once the disk image is inside oVirt, not before. Migrating (handcrated) images has been regarded as being inferior to automated builds to such a degree, that QA seems to have completely abandoned any effort there, long before oVirt was abandoned itself.