No bootable disk OVA
Hi all, we imported a rhel 9.2 image from an OVA generated on vmware and we tried to create a new VM but we had a no bootable disk error. The OVA has been imported with virt-2-v library and if we create a new VM we noticed that the disk is 2 GB size but we resized the disk to 50 GB. The VM has been started with Q35 Chipset with UEFI options and the disk has the flag bootable activated. We're using ovirt 4.5.4-1 Could you help us to sort this issue? Thanks, Marcello
Hi, On Thu, Jun 29, 2023 at 04:15:35PM -0000, cello86@gmail.com wrote:
Hi all, we imported a rhel 9.2 image from an OVA generated on vmware and we tried to create a new VM but we had a no bootable disk error. The OVA has been imported with virt-2-v library
You mean you did not use the oVirt UI? If that's the case, what was the virt-v2v command line you used? Do you have log from virt-v2v? How did you create the disks in oVirt? Tomas
and if we create a new VM we noticed that the disk is 2 GB size but we resized the disk to 50 GB.
The VM has been started with Q35 Chipset with UEFI options and the disk has the flag bootable activated.
We're using ovirt 4.5.4-1
Could you help us to sort this issue?
Thanks, Marcello _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6ANTGWEA34NJ3C...
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 :-)
Hi, we tried to use the vmware ovftool without success. We tried another time with virt-2v and now the template was 50 GB size. Thanks, Marcello
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.
participants (4)
-
cello86＠gmail.com -
change_jeeringly679＠dralias.com -
Thomas Hoberg -
Tomáš Golembiovský