GPU Passthrough issues with oVirt 4.5
by Vinícius Ferrão
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 0000:0a:00.0: enabling device (0000 -> 0002)
[ 23.008026] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR1 is 0M @ 0x0 (PCI:0000:0a:00.0)
[ 23.008035] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR2 is 0M @ 0x0 (PCI:0000:0a:00.0)
[ 23.008040] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR3 is 0M @ 0x0 (PCI:0000:0a:00.0)
[ 23.008045] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR4 is 0M @ 0x0 (PCI:0000:0a:00.0)
[ 23.008049] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
NVRM: BAR5 is 0M @ 0x0 (PCI:0000:0a:00.0)
[ 23.012339] NVRM: The NVIDIA GPU 0000: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 0000: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:0000:0b:00.0)
[ 23.016842] nvidia: probe of 0000: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:0000:0c:00.0)
[ 23.017215] nvidia: probe of 0000: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 0x00000900] Loading driver
[ 23.485708] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:09:00.0 on minor 1
On the host this shows up on dmesg, but seems right:
[ 709.572845] vfio-pci 0000:1a:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258
[ 709.572877] vfio-pci 0000:1a:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
[ 709.572883] vfio-pci 0000:1a:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0
[ 710.660813] vfio-pci 0000:1d:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258
[ 710.660845] vfio-pci 0000:1d:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
[ 710.660851] vfio-pci 0000:1d:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0
[ 711.748760] vfio-pci 0000:1e:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258
[ 711.748791] vfio-pci 0000:1e:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
[ 711.748797] vfio-pci 0000:1e:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0
[ 712.836687] vfio-pci 0000:1c:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258
[ 712.836718] vfio-pci 0000:1c:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
[ 712.836725] vfio-pci 0000:1c:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0
Thanks.
2 years
No bootable disk OVA
by cello86＠gmail.com
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
2 years
ovirt template import using ansible
by destfinal＠googlemail.com
Hi,
I use a set of templates, generated in one cluster and re-used in multiple clusters. The clusters do not have direct connections between each other. My dev environment can talk to all the clusters. Currently,
1. I export the templates (as OVAs) to one of the nodes (example: node1.source.cluster), from the ovirt console (https://management.source.cluster)
2. scp the templates to my dev machine (example: scp -r node1.source.cluster:/tmp/ovirt_templates /tmp/ovirt_templates)
3. scp the templates from my dev environment to the target cluster (example: scp /tmp/ovirt_templates node1.target.cluster:/tmp)
4. Import the templates using the ovirt console of the target cluster (https://management.target.cluster)
This is highly a manual job and I am trying to automate the process using ansible. I am unable to work it out using the ovit_template module documentation (https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_tem...) and could not able to see any other module in this relation.
Has anybody done this before and point me to the right direction? Or if there is a better process than what I follow above, please suggest me one.
Please let me know if you need more information in this regard.
Thanks
2 years
Managing Ovirt Networks with Ansible
by William Roberts
Hi Team,
So I'm setting up some automation to build an environment within an ovirt cluster of X amount of nodes. Part of that is the creation of the networks, and subsequently the attaching of those network to each host in the cluster. Seems pretty straight forward except for the fact you need the name of the interfaces to attach the networks to, unfortunately none of the ansible 2.9 modules I've been trying give you that information. Specifically ovirt_host_info, has a list item called "nics" which i assumed would give it but it doesn't return a value. Does anyone know of a module that would give this info? seems like a pretty crucial thing to be missing.
TIA
Will
2 years
securing ovirt vnc console
by Bill James
Our security requirements require that we disable tls1.0 and tla1.1 for VNC
port, 59xx.
I have not yet been able to find where this can be done, only for spice
console.
Can anyone assist in pointing me to what config file controls this?
ovirt-engine 4.3.
2 years
Re: Customizing ovirt vm / user web portal
by R A
Hello,
the idea was to run the vm portal from another host and connect it through REST-API with the host which run ovirt-engine for example for a dev environment.
So it’s not possible?
I guess importing the third Party CA local in to ovirt-engine should also work local with the vmportal.
BR
Peter
Von: Patrick Hibbs <hibbsncc1701(a)gmail.com>
Gesendet: Mittwoch, 28. Juni 2023 10:27
An: R A <Jarheadx(a)hotmail.de>
Betreff: Re: [ovirt-users] Re: Customizing ovirt vm / user web portal
Hello,
oVirt doesn't use the system wide java keystore. It uses it's own at /etc/pki/ovirt-engine/.truststore
If you want your third party cert to work with the java components, such as the disc image uploader function in the admin console, you'll either need to follow the official documentation for altering it. Or import the third party CA manually. (It uses the default keystore password.)
-Patrick Hibbs
2 years
Bcp vm
by Ali Gusainov
Hello experts.
Environment:
2 identical servers running
CentOS Linux release 7.7.1908
oVirt Version:4.3.7.2-1.el7
No clusters configured.
NFS share for backups on third server.
Have some questions.
1. Need to create backups of virtual machines to NFS without downtime. Can an 'OVA export' be a complete policy for backups?
2. Is there a way to export vm to OVA via command line?
2 years
How to add alternate fqdn
by BJ一哥
Version 4.5.1
I try to modify the parameter of SSO_ALTERNATE_ENGINE_FQDNS in
/etc/ovirt-engine/engine.conf.d/11-setup-sso.conf to a new domain name
The web interface opens normally, but the management portal cannot be
accessed. Entering the management portal prompts 500 internal Server error
2 years
HostEngine added alternate fqdn cannot be accessed
by ziyi Liu
I modified the parameter of SSO_ALTERNATE_ENGINE_FQDNS to the new fqdn in /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf.
After modifying the hosts, I can use the new fqdn to open the web but cannot enter the portal management, prompting 500 Internal Server Error
2 years
