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
2012-07-04 19:47:00 UTC
+++ This bug was initially created as a clone of Bug #836710 +++
For a full description of the bug, read this:
https://www.redhat.com/archives/libguestfs/2012-July/msg00020.html
Note that we are very lucky: the bug does NOT affect RHEL 6.3
as far as I can tell from my testing. However I think it'd
be a very good idea to backport the required fixes into
RHEL 6.4, and even consider a 6.3 z-stream fix.
Comment 1RHEL Program Management
2012-07-10 08:07:39 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2RHEL Program Management
2012-07-10 23:48:56 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 5Richard W.M. Jones
2012-11-02 08:15:14 UTC
(In reply to comment #4)
> Rich,
>
> for the qemu version, in your env, the qemu version is
> qemu-system-x86-1.0-17.fc18.x86_64, but in RHEL6.x, qemu-kvm is from
> upstream version qemu-0.12, so i need an upstream version of qemu to
> reproduce this bug, so far, i didn't see how to reproduce and verify this
> bug in rhel6.x? any suggestion for this?
There isn't any version of qemu-kvm in RHEL 6 which exhibits
the crashing bug (luckily!). You could try an upstream version,
but probably a better idea is to modify upstream qemu so it
crashes deliberately on shutdown.
I just had a quick look at the source, and *maybe* adding
a call to abort() in vl.c: qemu_kill_report() ?
I can have a look into this in more detail later.
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.
http://rhn.redhat.com/errata/RHBA-2013-0324.html