Description of problem: VM vGPU hook (custom propeties: mdev_type) is not applied on the VM, the VM will run but without Nvidia instance of vGPU. Version-Release number of selected component (if applicable): vdsm-4.20.2-74.git2be4775.el7.centos.x86_64 vdsm-hook-vfio-mdev-4.20.2-74.git2be4775.el7.centos libvirt-client-3.2.0-14.el7_4.2.x86_64 qemu-kvm-rhev-2.9.0-14.el7.x86_64 sanlock-3.5.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Browse Webadmin -> VMs tab -> select VM -> edit -> custom properties: add mdev_type to VM with valid Nvidia instance. 2. Run VM 3. Observe VM qemu-kvm process. Actual results: VM should run with Nvidia GPU instance attached. Expected results: VM is running without Nvidia GPU. Additional info: engine and vdsm logs attached (vdsm.log VM start 2017-08-16 13:07:19,786+0300)
ovirt-engine build: ovirt-engine-4.2.0-0.0.master.20170811144920.gita423008.el7.centos
Created attachment 1314051 [details] vdsm.log
Created attachment 1314052 [details] engine.log
Verification builds: ovirt-engine-4.2.0-0.0.master.20170820180837.git59243e9.el7.centos libvirt-client-3.2.0-14.el7_4.2.x86_64 vdsm-4.20.2-90.git6511af5.el7.centos.x86_64 qemu-kvm-rhev-2.9.0-14.el7.x86_64 sanlock-3.5.0-1.el7.x86_64 Nvidia GRIDSW_5.0 Beta Release KVM Drivers (R384)
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.