- Users - oVirt List Archives

Two Hosts with Self Hosted Engine - HA / Failover & NFS
by shanep＠lifestylepanel.com 06 Mar '19

06 Mar '19

Is it possible to have only two physical hosts with NFS and be able to do VM HA / Failover between these hosts? Both hosts are identical with RAID Drive Arrays of 8TB. If so, can anybody point me to any docs or examples on exactly how the Storage setup is done so that NFS will replicate across the hosts? If not what file system should I use to achieve this? Thanks Shane

2 1

Quota Actual Consumption
by Andrey Rusakov 06 Mar '19

06 Mar '19

Hi, Is it possible to configure oVirt to work Quota with actual vCPU Consumption. Currently i got 1 VM with 2 vCPU and 8Gb. In VM stats - 0% of CPU in use 0% of RAM in Use (it is fresh Linux instalaltion) In Quota consumption i can see 40% of CPU (vCPU quota = 5) 27% of RAM (Memory quota 30Gb) Is it possible to adjust Quata management to work with Actual workload, instead of VM Configuration? P.S. Seems like it is working for Storage, as i can see 0% Consumption in Quota (1Gb of thick disk with 20Gb Max and 200Gb in Quota)

1 1

Install Hyerpvisor via PXE boot
by wodel youchi 06 Mar '19

06 Mar '19

Hi, Is it possible to install oVirt Hypervisor using PXE boot install. I did a simple dhcpd+tftp+httpd install and I configured a test with CentOS 7 and it works both for legacy and efi. When I tried with the Hypervisor ISO, the image booted but I didn't any package for installation, digging a little I found the ks.cfg which contain this : cd /tmp rpm2cpio /run/install/repo/Packages/redhat-virtualization-host-image-update*|cpio -ivd squashfs=$(find|grep squashfs|grep -v meta) ln -s $squashfs /tmp/squashfs %end liveimg --url=file:///tmp/squashfs I modified my grub.cfg like this : menuentry 'Install oVirtH 4.2' --class fedora --class gnu-linux --class gnu --class os { linuxefi /networkboot/ovhyper4.2/vmlinuz inst.ks=http://192.168.1.50/pub/oh42/ks.cfg inst.stage2=http://192.168.1.50/pub/oh42/ initrdefi /networkboot/ovhyper4.2/initrd.img } This time I got Fatal error : file:///tmp/squashfs not found. Regards.

1 0

OVN Deployment
by Bryan Sockel 06 Mar '19

06 Mar '19

Hi, I am looking to implement OVN with in my setup, but could use some guidance on the implementation. As part of the implementation i am planning on moving from engine being installed on a physical server to running as a VM with in my environment. I do not need to retain any historical data. The plan would be to import the vm's into a new deployment of oVirt after getting everything setup. Currently i have a single host i plan on using for the initial deployment, but as vm's are moved over, i will be adding additional hosts. With the deployment of oVirt 4.3.x the ovn provider is installed correctly. Is there a problem with installing the OVN Controller on the Hosted Engine? Has any one found a good guide for setting up and deploying ovn in an oVirt hosted-engine environment? Thank You, Bryan Sockel

2 1

Re: Hosted engine not starting after 4.3 Upgrade - cannot find OVF_STORE
by Jayme 06 Mar '19

06 Mar '19

It sure if this is the same bug I hit but check ownership of the cam images. There’s a bug in 4.3 upgrade that changes ownership to root and causes vms to not start until you change back to vdsm On Wed, Mar 6, 2019 at 4:57 AM Shawn Southern <shawn.southern(a)entegrus.com> wrote: > After running 'hosted-engine --vm-start', the status of the hosted engine > VM is: > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : ovirtnode-01 > Host ID : 3 > Engine status : {"reason": "bad vm status", "health": > "bad", "vm": "down_unexpected", "detail": "Down"} > Score : 0 > stopped : False > Local maintenance : False > crc32 : 7e3db850 > local_conf_timestamp : 3509 > Host timestamp : 3508 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=3508 (Tue Mar 5 16:03:30 2019) > host-id=3 > score=0 > vm_conf_refresh_time=3509 (Tue Mar 5 16:03:31 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineUnexpectedlyDown > stopped=False > timeout=Wed Dec 31 20:05:37 1969 > > > The /var/log/libvirt/qemu/HostedEngine.log has no entries since the hosted > engine VM was rebooted. > > /var/log/ovirt-hosted-engine-ha/agent.log: > MainThread::ERROR::2019-03-05 > 16:07:31,916::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Failed scanning for OVF_STORE due to Command Volume.getInfo with args > {'storagepoolID': '00000000-0000-0000-0000-000000000000', > 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': > u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': > u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: > (code=201, message=Volume does not exist: > (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) > MainThread::ERROR::2019-03-05 > 16:07:31,916::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Unable to identify the OVF_STORE volume, falling back to initial vm.conf. > Please ensure you already added your first data domain for regular VMs > MainThread::INFO::2019-03-05 > 16:07:31,971::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineUnexpectedlyDown (score: 0) > MainThread::ERROR::2019-03-05 > 16:07:42,304::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Failed scanning for OVF_STORE due to Command Volume.getInfo with args > {'storagepoolID': '00000000-0000-0000-0000-000000000000', > 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': > u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': > u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: > (code=201, message=Volume does not exist: > (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) > MainThread::ERROR::2019-03-05 > 16:07:42,305::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Unable to identify the OVF_STORE volume, falling back to initial vm.conf. > Please ensure you already added your first data domain for regular VMs > MainThread::INFO::2019-03-05 > 16:07:42,365::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineUnexpectedlyDown (score: 0) > MainThread::ERROR::2019-03-05 > 16:07:51,791::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Failed scanning for OVF_STORE due to Command Volume.getInfo with args > {'storagepoolID': '00000000-0000-0000-0000-000000000000', > 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': > u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': > u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: > (code=201, message=Volume does not exist: > (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) > MainThread::ERROR::2019-03-05 > 16:07:51,792::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Unable to identify the OVF_STORE volume, falling back to initial vm.conf. > Please ensure you already added your first data domain for regular VMs > MainThread::INFO::2019-03-05 > 16:07:51,850::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineUnexpectedlyDown (score: 0) > MainThread::INFO::2019-03-05 > 16:08:01,868::states::684::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) > Engine down, local host does not have best score > MainThread::ERROR::2019-03-05 > 16:08:02,196::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Failed scanning for OVF_STORE due to Command Volume.getInfo with args > {'storagepoolID': '00000000-0000-0000-0000-000000000000', > 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': > u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': > u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: > (code=201, message=Volume does not exist: > (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) > MainThread::ERROR::2019-03-05 > 16:08:02,197::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Unable to identify the OVF_STORE volume, falling back to initial vm.conf. > Please ensure you already added your first data domain for regular VMs > MainThread::INFO::2019-03-05 > 16:08:02,286::states::699::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) > Score is 0 due to unexpected vm shutdown at Tue Mar 5 16:01:19 2019 > MainThread::INFO::2019-03-05 > 16:08:02,286::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineUnexpectedlyDown (score: 0) > MainThread::ERROR::2019-03-05 > 16:08:11,697::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Failed scanning for OVF_STORE due to Command Volume.getInfo with args > {'storagepoolID': '00000000-0000-0000-0000-000000000000', > 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': > u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': > u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: > (code=201, message=Volume does not exist: > (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) > MainThread::ERROR::2019-03-05 > 16:08:11,697::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Unable to identify the OVF_STORE volume, falling back to initial vm.conf. > Please ensure you already added your first data domain for regular VMs > MainThread::INFO::2019-03-05 > 16:08:11,752::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) > Current state EngineUnexpectedlyDown (score: 0) > > I expect the issue is this: > MainThread::ERROR::2019-03-05 > 16:08:11,697::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) > Failed scanning for OVF_STORE due to Command Volume.getInfo with args > {'storagepoolID': '00000000-0000-0000-0000-000000000000', > 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': > u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': > u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: > (code=201, message=Volume does not exist: > (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) > > Where do I go from here? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/RSPFVWDYFDMYN… >

2 1

ipxe-roms-qemu question
by laco.humo＠gmail.com 06 Mar '19

06 Mar '19

Hi all, in the past we have used customized ipxe (to allow boot over network with 10G cards), now we have finally updated our hypervisors to the latest ipxe-roms-qemu Of course the sum now differs and during live-migration the libvirtd throws this error: Mar 4 11:37:14 hypevisor-01 libvirtd: 2019-03-04 10:37:14.084+0000: 15862: error : qemuMigrationJobCheckStatus:1313 : operation failed: migration out job: unexpectedly failed Mar 4 11:37:15 hypevisor-01 libvirtd: 2019-03-04T10:37:13.941040Z qemu-kvm: Length mismatch: 0000:00:03.0/virtio-net-pci.rom: 0x20000 in != 0x40000: Invalid argument Mar 4 11:37:15 hypevisor-0 libvirtd: 2019-03-04T10:37:13.941090Z qemu-kvm: error while loading state for instance 0x0 of device 'ram' Mar 4 11:37:15 hypevisor-0 libvirtd: 2019-03-04T10:37:13.941530Z qemu-kvm: load of migration failed: Invalid argument is there an easy command we can use to identify what guests are still using the old .rom and must be powercycled ? Thank you in advance

1 0

Install oVirt using the Cockpit wizard
by max zhang 06 Mar '19

06 Mar '19

I wanto try to install ovirt4.3.1,follow the manual of ovirt,but I encounted this error: [root@localhost ~]# sudo subscription-manager repos --enable="rhel-7-server-rpms" System certificates corrupted. Please reregister. And I have no idea to deal it Thanks.

1 0

Hosted engine not starting after 4.3 Upgrade - cannot find OVF_STORE
by Shawn Southern 05 Mar '19

05 Mar '19

After running 'hosted-engine --vm-start', the status of the hosted engine VM is: conf_on_shared_storage : True Status up-to-date : True Hostname : ovirtnode-01 Host ID : 3 Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down_unexpected", "detail": "Down"} Score : 0 stopped : False Local maintenance : False crc32 : 7e3db850 local_conf_timestamp : 3509 Host timestamp : 3508 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=3508 (Tue Mar 5 16:03:30 2019) host-id=3 score=0 vm_conf_refresh_time=3509 (Tue Mar 5 16:03:31 2019) conf_on_shared_storage=True maintenance=False state=EngineUnexpectedlyDown stopped=False timeout=Wed Dec 31 20:05:37 1969 The /var/log/libvirt/qemu/HostedEngine.log has no entries since the hosted engine VM was rebooted. /var/log/ovirt-hosted-engine-ha/agent.log: MainThread::ERROR::2019-03-05 16:07:31,916::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Failed scanning for OVF_STORE due to Command Volume.getInfo with args {'storagepoolID': '00000000-0000-0000-0000-000000000000', 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: (code=201, message=Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) MainThread::ERROR::2019-03-05 16:07:31,916::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Unable to identify the OVF_STORE volume, falling back to initial vm.conf. Please ensure you already added your first data domain for regular VMs MainThread::INFO::2019-03-05 16:07:31,971::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineUnexpectedlyDown (score: 0) MainThread::ERROR::2019-03-05 16:07:42,304::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Failed scanning for OVF_STORE due to Command Volume.getInfo with args {'storagepoolID': '00000000-0000-0000-0000-000000000000', 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: (code=201, message=Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) MainThread::ERROR::2019-03-05 16:07:42,305::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Unable to identify the OVF_STORE volume, falling back to initial vm.conf. Please ensure you already added your first data domain for regular VMs MainThread::INFO::2019-03-05 16:07:42,365::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineUnexpectedlyDown (score: 0) MainThread::ERROR::2019-03-05 16:07:51,791::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Failed scanning for OVF_STORE due to Command Volume.getInfo with args {'storagepoolID': '00000000-0000-0000-0000-000000000000', 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: (code=201, message=Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) MainThread::ERROR::2019-03-05 16:07:51,792::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Unable to identify the OVF_STORE volume, falling back to initial vm.conf. Please ensure you already added your first data domain for regular VMs MainThread::INFO::2019-03-05 16:07:51,850::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineUnexpectedlyDown (score: 0) MainThread::INFO::2019-03-05 16:08:01,868::states::684::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Engine down, local host does not have best score MainThread::ERROR::2019-03-05 16:08:02,196::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Failed scanning for OVF_STORE due to Command Volume.getInfo with args {'storagepoolID': '00000000-0000-0000-0000-000000000000', 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: (code=201, message=Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) MainThread::ERROR::2019-03-05 16:08:02,197::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Unable to identify the OVF_STORE volume, falling back to initial vm.conf. Please ensure you already added your first data domain for regular VMs MainThread::INFO::2019-03-05 16:08:02,286::states::699::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Score is 0 due to unexpected vm shutdown at Tue Mar 5 16:01:19 2019 MainThread::INFO::2019-03-05 16:08:02,286::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineUnexpectedlyDown (score: 0) MainThread::ERROR::2019-03-05 16:08:11,697::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Failed scanning for OVF_STORE due to Command Volume.getInfo with args {'storagepoolID': '00000000-0000-0000-0000-000000000000', 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: (code=201, message=Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) MainThread::ERROR::2019-03-05 16:08:11,697::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Unable to identify the OVF_STORE volume, falling back to initial vm.conf. Please ensure you already added your first data domain for regular VMs MainThread::INFO::2019-03-05 16:08:11,752::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineUnexpectedlyDown (score: 0) I expect the issue is this: MainThread::ERROR::2019-03-05 16:08:11,697::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) Failed scanning for OVF_STORE due to Command Volume.getInfo with args {'storagepoolID': '00000000-0000-0000-0000-000000000000', 'storagedomainID': '79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID': u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID': u'48ee766b-185d-4928-a046-b048d65af2a6'} failed: (code=201, message=Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)) Where do I go from here?

1 0

VM With Snapshots Marked As Illegal
by Clint Boggio 05 Mar '19

05 Mar '19

Greetings oVirt Users; Environment: oVirt 4.2.0.2-1 1 Dedicated Engine 6 Hypervisor Nodes iSCSI Storage All running CentOS 7.5 I have a VM with the illegal snapshot error. After doing some research on the condition i have found some methods for fixing the problem by connecting to the database and repairing the fault. I am unable to connect to the engine database from the engine command line with the password in 10-setup-database.conf for whatever reason. (likely user error) I don't really need the disk that is attached to this VM that is at fault as it is a disk that is being utilized by the VM to perform local backups and that function has been moved to an offsite backup solution. If I shut down the afflicted VM, then delete the un-needed disk, will the snapshots be deleteed and thus the problem alleviated ? Or will the system not delete the un-needed disk because of the fault and then not reboot because if the illegal statu of the snapshot ? I have tried to delete the snapshots, and the system refuses to do so. I may need some guidance regarding connecting to my engine database if i cannot delete the un-needed disk. Thank you all for any help in this matter, and if more information is needed please let me know. ~Clint Boggio

2 1

problems getting vGPU working
by cmc 05 Mar '19

05 Mar '19

Hi, I'm having trouble getting my Nvidia vGPU to work on a VM. Setup: RHEV 4.2 on RHEL 7.5, Tesla M60 (switched to graphics mode). I'm using the NVIDIA-GRID-RHEL-7.5-410.92-410.91-412.16.zip package from Nvidia. On the hypervisor, I've installed the NVIDIA-vGPU-rhel-7.5-410.91.x86_64 rpm. vfio kernel modules are loaded, nvidia-smi shows the card, and I can see all the vGPUs via vdsm-client I've created a CentOS 7.4 VM and added a 'B' type vGPU instance in 'custom properties'. I've configured gridd.conf to point to the license server and it reports picking up a license in /var/log/messages. I installed the driver via the .run file (NVIDIA-Linux-x86_64-410.92-grid.run). The nvidia kernel module is loaded, but so also is the 'qxl' paravirtual driver. lspci reports: 00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) 00:07.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla M60] (rev a1) The Xorg.0.log reports: [ 1622.212] (--) PCI:*(0:0:2:0) 1b36:0100:1af4:1100 rev 4, Mem @ 0xf0000000/134217728, 0xfb000000/8388608, 0xfb870000/8192, I/O @ 0x0000c100/32, BIOS @ 0x????????/65536 [ 1622.212] (--) PCI: (0:0:7:0) 10de:13f2:10de:1177 rev 161, Mem @ 0xfa000000/16777216, 0xd0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000c000/128, BIOS @ 0x????????/131072 [ 1622.212] (II) LoadModule: "glx" [ 1622.212] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 1622.213] (II) Module glx: vendor="X.Org Foundation" [ 1622.213] compiled for 1.19.3, module version = 1.0.0 [ 1622.213] ABI class: X.Org Server Extension, version 10.0 [ 1622.213] (II) LoadModule: "nvidia" [ 1622.214] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 1622.214] (II) Module nvidia: vendor="NVIDIA Corporation" [ 1622.214] compiled for 4.0.2, module version = 1.0.0 [ 1622.214] Module class: X.Org Video Driver [ 1622.214] (II) NVIDIA dlloader X Driver 410.92 Thu Dec 20 04:48:17 CST 2018 [ 1622.214] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 1622.214] (++) using VT number 1 [ 1622.214] (EE) No devices detected. [ 1622.214] (EE) Fatal server error: [ 1622.214] (EE) no screens found(EE) [ 1622.214] (EE) Could the qxl module be somehow blocking the nvidia driver? I tried blacklisting the driver in grub, though that didn't work anyway. Thanks in advance for any help. Cam

2 1