Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
QEMU's vfio-pci device defaults to display=auto, so any host kernel where the mdev device exposes a display will now require QEMU to support a display configuration consistent with that display. This can be avoided adding a display=off parameter to the device, but I think we've broken backwards compatibility by making the default 'auto'. What host kernel is being used that has GVT-g with display support?
Posted a QEMU patch:
http://lists.nongnu.org/archive/html/qemu-devel/2018-05/msg06443.html
I don't see how to resolve this other than turning the display default to "off", posted upstream, we'll see what fallout this causes and how libvirt will handle it if the default changes. This doesn't seem to be simply a GVT-g bug though, it's a design problem, so re-assigning to me.
Verify this issue against qemu-kvm-rhev-2.12.0-13.el7.x86_64:
# /usr/libexec/qemu-kvm -device vfio-pci,sysfsdev=/sys/bus/mdev/devices/89d223b5-8e86-4682-b703-acf28f1fece8
VNC server running on ::1:5900
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:3443
Description of problem: Fails to start guest with Intel vGPU device Version-Release number of selected component: qemu-kvm-rhev-2.12.0-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare a guest with Intel vGPU device: # virsh dumpxml 1|grep hostdev -a3 ... <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-pci'> <source> <address uuid='7bb8579b-55ca-4f4d-b70f-498a583c1e6e'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </hostdev> ... 2. # virsh start 1 error: Failed to start domain 1 error: internal error: qemu unexpectedly closed the monitor: 2018-05-28T05:31:03.382527Z qemu-kvm: -device vfio-pci,id=hostdev0,sysfsdev=/sys/bus/mdev/devices/7bb8579b-55ca-4f4d-b70f-498a583c1e6e,bus=pci.0,addr=0x3: vfio error: 7bb8579b-55ca-4f4d-b70f-498a583c1e6e: vfio-display-dmabuf: opengl not available Actual results: Guest fails to start Expected results: Guest starts successfully Additional info: qemu-kvm-rhev-2.10.0-21.el7_5.2.x86_64 works well