Vdsm should enable dynamic_ownership libvirt option and pass ownership and permission management of host devices to libvirt. That not only avoids the need to handle ownership and permissions of host devices in Vdsm, but it's also necessary for features such as Q35 support or secure boot support.
Regarding verification, it's important to test that: - snapshots with memory work with all the supported storage kinds (NFS, iSCSI, GlusterFS, ...); - CD-ROM works, both empty and with a media attached; - disk hot plugs work, including block storage; - passthrough host devices can be successfully attached to a VM: SCSI, USB, PCI (IOMMU); - mediated devices can be attached; - /dev/hwrng can be attached.
Verified upstream: ovirt-engine-4.3.0-0.0.master.20181101091940.git61310aa.el7 vdsm-4.30.1-34.gitad59c72.el7.x86_64 libvirt-client-4.5.0-10.el7.x86_64 qemu-kvm-common-ev-2.10.0-21.el7_5.7.1.x86_64 sanlock-3.6.0-1.el7.x86_64 Verification scenario: Manual tests: 1. USB passthrough 2. CDROM attached to VM with and without media 3. Disk hotplug (NFS and iSCSI) 4. VFIO 5. mdev, also with multiple devices on the same VM 6. Intel GVTg 7. add/remove NFS storage also NFSv4.2 - V 8. add/remove iSCSI storage - V 9. HWRNG 10. v2v from Xen and VMware 11. Import from KVM 12. VM sanity (snapshots, templates, clone etc.) Automation tests: No related issues observed in automation results analysis.
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.