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:
libvirt fails to handle latest upstream qemu
Version-Release number of selected component (if applicable):
qemu: upstream commit 585f60368f23e6603cf86cfdaeceb89d1169f4b8 + newer
libvirt-0.10.2-4.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. create a guest
2. switch <emulator> to upstream qemu
3. enable sga
Actual results:
error: Failed to start domain fedora-org-virtio
error: internal error qemu does not support SGA
Expected results:
guest boots.
Additional info:
RHEL libvirt still uses the old way of determining QEMU capabilities by parsing -help, -device ?, -M ?, ... output and since upstream QEMU already started to change the behavior and output of these commands, libvirt from RHEL is unable to detect some capabilities and as time goes on, upstream QEMU will become totally unusable in combination with this was of capabilities probing.
Upstream libvirt already supports (in current git, to be released as 1.0.0 in two weeks time) capabilities probing through QMP for QEMU >= 1.2.0. Since this support was added after the last rebase for RHEL-6.4, i.e., after 0.10.2 was released, this functionality is not included in libvirt for RHEL. And because such code will never be used in RHEL anyway, I don't see a compelling reason to backport this it.
I understand why you want this and we are not trying to artificially break compatibility between RHEL's libvirt and upstream QEMU. However, it's hard to justify backporting patches just to keep libvirt working with the most recent QEMU release. Such support will only get to RHEL when we rebase to a newer libvirt.