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.
Comment 8Marc-Andre Lureau
2015-07-09 12:07:21 UTC
(In reply to Fabiano Fidêncio from comment #7)
> (In reply to Marc-Andre Lureau from comment #6)
> > this is solved by the following qemu patch series:
> > https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg00570.html
> >
>
> Do we have a qemu bug for this?
no
> Looks like the patches are not in the latest build.
They are not even in 2.3, they will be in next qemu 2.4 release.
Given the low severity but the risk of the patch, I wouldn't rush it, but wait for the rebase to happen (it could take a while though).
Eventually, I suggest the bug could be moved closed upstream.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 12Christophe Fergeau
2016-04-27 08:55:55 UTC
Currently, qemu-kvm for 7.3 has (heavily patched) qemu 1.5.3, but does not seem to have the patches mentioned in comment #8.
qemu-kvm-rhev (rhevh-rhel-7.3 branch) has qemu 2.5.0. However, http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e95e203 (one of the needed commits) has a version check on spice 0.12.6, so even if we add the needed patches to spice-server, qemu-kvm-rhev is not going to take advantage of them.
We really need to open QEMU bugs if we want to solve this (and the related rhbz#912763 )
Comment 13Christophe Fergeau
2016-04-28 16:52:40 UTC
I've added the needed spice patches in spice-0.12.4-17.el7 so only the QEMU side is missing now.
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://rhn.redhat.com/errata/RHBA-2016-2324.html