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 3Richard W.M. Jones
2012-04-17 12:13:54 UTC
Does this fail?
while guestfish -a /dev/null run -v > /tmp/fish.out 2>&1 ; do echo -n . ; done
Comment 4Richard W.M. Jones
2012-04-17 14:38:09 UTC
(In reply to comment #3)
> Does this fail?
>
> while guestfish -a /dev/null run -v > /tmp/fish.out 2>&1 ; do echo -n . ; done
In answer, Pádraig tried it and yes it does fail after a few
iterations ("fewer than 6" according to Pádraig).
I tried it on 6.2 (but on baremetal) and it ran for hundreds of
iterations, so this could be a kernel regression, but I still
need to check I can reproduce the issue on 6.3 beta 1 + baremetal.
Comment 5Richard W.M. Jones
2012-04-17 17:06:08 UTC
Created attachment 578109[details]
guestfish messages from failed boot
Seems to only happen in a nested VM, and rather easy to trigger.
libguestfs-tools-c-1.16.18-2.el6.x86_64
qemu-kvm-0.12.1.2-2.272.el6.x86_64
kernel 2.6.32-262.el6.x86_64
Comment 6RHEL Program Management
2012-05-03 05:16:02 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 7Richard W.M. Jones
2012-09-28 12:33:30 UTC
Still seeing this one with:
kernel-2.6.32-309.el6.x86_64
qemu-kvm-0.12.1.2-2.316.el6.x86_64
although it took me 200 iterations to hit it.
I'm going to try adding noapic to the command line.
Comment 8Richard W.M. Jones
2012-09-28 13:13:29 UTC
Crashes with noapic too, in a different way!
Comment 9Richard W.M. Jones
2012-10-11 09:15:33 UTC
As I don't have a way to fix this, or even to reproduce
it reliably, and the evidence points to an obscure timing
issue within qemu, I'm afraid all I can do is defer this
to RHEL 6.5 and reassign it to qemu.
(In reply to comment #10)
> Is that important enough not to close it?
+1
I'm closing it, please reopen if you believe it's actually important and can be reproduced in a non-nested environment.