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.
DescriptionRichard W.M. Jones
2014-10-15 07:38:36 UTC
Description of problem:
I suspect we need to carry this patch in RHEL 7.1:
https://lists.gnu.org/archive/html/qemu-devel/2014-10/msg00518.html
It's not accepted upstream yet, waiting on a few more ACKs.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.1.2-4.el7.x86_64
How reproducible:
Not reproducible. It's a bug that probably only breaks
big-endian architectures.
Comment 2Richard W.M. Jones
2014-11-03 12:00:51 UTC
Since it looks as if this patch is about to go upstream, I'm
providing dev-ack.
Note that the final version is a bit different from the one
posted first. The final version is:
https://github.com/stefanha/qemu/commit/f76faeda4bd59f972d09dd9d954297f17c21dd60
Miya: Can someone in your team consider this bug for QA ack?
It's difficult to QA since it doesn't cause a failure on x86
systems. Perhaps it's best to just check that the patch was
included.
Comment 3Richard W.M. Jones
2014-11-04 10:06:36 UTC
Now upstream (commit f76faeda4bd59f972d09dd9d954297f17c21dd60).
Comment 4Miroslav Rezanina
2014-11-13 09:06:31 UTC
Verify:
Version of components:
qemu-kvm-rhev-2.1.2-8.el7.x86_64
# rpm -ql qemu-kvm-rhev-2.1.2-8.el7.x86_64 --changelog |grep 1152901
- kvm-block-curl-Improve-type-safety-of-s-timeout.patch [bz#1152901]
- Resolves: bz#1152901
----------
Also checked the qemu-kvm-rhev-2.1.2-8.el7.src.rpm. Decompress this rpm. Could find the same patch code(https://github.com/stefanha/qemu/commit/f76faeda4bd59f972d09dd9d954297f17c21dd60) in file ./kvm-block-curl-Improve-type-safety-of-s-timeout.patch
Based on above show, this bz has been verified.
========
Reproduce:
qemu-kvm-rhev-2.1.2-1.el7.x86_64
# rpm -ql qemu-kvm-rhev-2.1.2-1.el7.x86_64 --changelog|grep 1152901
No output.
So reproduced it.
=====================
Hi Richard,
As you have mentioned in comment 2, does above verify method is correct or not? Thanks.
Best Regards,
Jun Li
Comment 7Richard W.M. Jones
2014-11-21 09:18:10 UTC
Yes that's fine.
We didn't actually demonstrate a bug. It probably only affects
big endian systems.
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/RHSA-2015-0624.html