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.
Description of problem:
With current RHEL-6.2 builds, libvirt sets the multifunction=on parameter for all PCI devices. This causes QEMU to set
QEMU_PCI_CAP_MULTIFUNCTION_BITNR
in the 'caps_present' field of the PCI device capabilities. When this is set for any QXL device, the Windows QXL driver will fail to activate the device returning a 'Code 10' error. Google suggests this error usually means the driver failed to find the device.
cf this thread
http://post-office.corp.redhat.com/archives/spice-list/2011-July/msg00106.html
Best guess is that this is a bug in the Win32 QXL driver, but there's of course a possibility that its a bug in the QEMU host side QXL driver instead.
Version-Release number of selected component (if applicable):
QXL driver version 4.5.52942.0, date 5/16/2011
How reproducible:
Always
Steps to Reproduce:
1. Start a QEMU binary with a WinXP guest and QXL driver installed, adding 2 extra heads:
-device qxl,id=video1,vram_size=33554432,bus=pci.0,multifunction=on,addr=0x6.0x0'
-device qxl,id=video2,vram_size=33554432,bus=pci.0,multifunction=off,addr=0x7.0x0'
2. Attempt to activate the additional QXL devices in the Windows XP guest
3.
Actual results:
Only the device with 'multifunction=off' will be able to start
Expected results:
Both extra displays start
Additional info:
> With current RHEL-6.2 builds, libvirt sets the multifunction=on parameter for
> all PCI devices.
This is actually incorrect. While libvirt in 6.2 has support for multifunction, it won't actually enable it since the RHEL6.2 KVM binary is too old.
So while, there is clearly a bug in QXL somewhere, it should not impact guests on a RHEL6.2 host, only Fedora 15+ hosts and future RHEL6.3 if multifunction is backported.