[ovirt-users] Re: No bootable disk OVA
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 :-) ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/5S43YMWAHW5O5TGDWE67T2B2ZZRY3H5N/
[ovirt-users] Re: ovirt with rocky linux kvm
Hey, This post is confusing. I'm assuming you installed a couple of Rocky Linux servers. This would have happened after June 21, 2021, when the first stable release of Rock Linux was released. You write that oVirt 4.3.10.4-1.el7, released on 2020-05-22, was chosen to manage those servers. Why would you manage servers with oVirt? oVirt is a virtualisation environment, and the hosts used to run virtual machines on should be either a Linux Enterprise server or the oVirt Node. And why use such an old oVirt enviroment? If you want something to manage Linux servers, I would expect you to use Katello/Foreman. But I'm not sure if it will work for Rocky Linux and Almalinux, especially in the lights of Red Hats latest announcements. Can you clarify if you want to use the Rock Linux servers as hosts in oVirt or whether or not you are looking for a platform to manage the Rocky Linux servers? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/A4IJ4TEHQWZC4CTXLVYPPGMKSZCCP25D/
[ovirt-users] GPU Passthrough issues with oVirt 4.5
Hello, does anyone is having issues with device passthrough on oVirt 4.5? I can passthrough the devices without issue to a given VM, but inside the VM it fails to recognize all the devices. In my case I’ve added 4x GPUs to a VM, but only one show up, and there’s the following errors inside the VM: [ 23.006655] nvidia :0a:00.0: enabling device ( -> 0002) [ 23.008026] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR1 is 0M @ 0x0 (PCI::0a:00.0) [ 23.008035] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR2 is 0M @ 0x0 (PCI::0a:00.0) [ 23.008040] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR3 is 0M @ 0x0 (PCI::0a:00.0) [ 23.008045] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR4 is 0M @ 0x0 (PCI::0a:00.0) [ 23.008049] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR5 is 0M @ 0x0 (PCI::0a:00.0) [ 23.012339] NVRM: The NVIDIA GPU :0a:00.0 (PCI ID: 10de:1db1) NVRM: installed in this system is not supported by the NVRM: NVIDIA 535.54.03 driver release. NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products' NVRM: in this release's README, available on the operating system NVRM: specific graphics driver download page at www.nvidia.com. [ 23.016175] nvidia: probe of :0a:00.0 failed with error -1 [ 23.016838] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR0 is 0M @ 0x0 (PCI::0b:00.0) [ 23.016842] nvidia: probe of :0b:00.0 failed with error -1 [ 23.017211] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR0 is 0M @ 0x0 (PCI::0c:00.0) [ 23.017215] nvidia: probe of :0c:00.0 failed with error -1 [ 23.017248] NVRM: The NVIDIA probe routine failed for 3 device(s). [ 23.214409] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023 [ 23.485704] [drm] [nvidia-drm] [GPU ID 0x0900] Loading driver [ 23.485708] [drm] Initialized nvidia-drm 0.0.0 20160202 for :09:00.0 on minor 1 On the host this shows up on dmesg, but seems right: [ 709.572845] vfio-pci :1a:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 709.572877] vfio-pci :1a:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 709.572883] vfio-pci :1a:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 [ 710.660813] vfio-pci :1d:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 710.660845] vfio-pci :1d:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 710.660851] vfio-pci :1d:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 [ 711.748760] vfio-pci :1e:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 711.748791] vfio-pci :1e:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 711.748797] vfio-pci :1e:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 [ 712.836687] vfio-pci :1c:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 712.836718] vfio-pci :1c:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 712.836725] vfio-pci :1c:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 Thanks. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/OXQGKJWVKRCJ5ABZFEG4TG4VOBKBIO2I/
[ovirt-users] Re: No bootable disk OVA
Hi, On Thu, Jun 29, 2023 at 04:15:35PM -, cell...@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-le...@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/6ANTGWEA34NJ3CWEAVDTNUZ7KSKIUHSE/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/FJHXYR2T4BRQBI6P5CCMXQ3VDARIMOHZ/