Currently, if someone wants to use vGPU passthrough, it is needed to ssh to the host where the specific device is installed and find the mdev type to be able to use it in the edit VM dialog. This RFE simplifies it a bit by showing the mdev type in the host devices tab, so the user does not need to leave the UI to find all information needed.
(In reply to Tomas Jelinek from comment #0) > Currently, if someone wants to use vGPU passthrough, it is needed to ssh to > the host where the specific device is installed and find the mdev type to be > able to use it in the edit VM dialog. > > This RFE simplifies it a bit by showing the mdev type in the host devices > tab, so the user does not need to leave the UI to find all information > needed. An additional enhancement would be, if all of the available instance_types are listed in a dropdown box for the mdev_type (instead of adding that manually). Although it is a custom property, moving this to the "Console" Tab also makes sense. Thoughts?
As we have discussed offline, it does make sense, but it is too late for it into 4.2.
Verified: ovirt-engine-4.2.0-0.0.master.20171106202508.gitf5140b9.el7.centos vdsm-4.20.6-33.git54a784e.el7.centos.x86_64 libvirt-client-3.2.0-14.el7_4.4.x86_64 qemu-kvm-common-ev-2.9.0-16.el7_4.8.1.x86_64 Test case added to external trackers.
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.