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.
DescriptionDr. David Alan Gilbert
2017-03-02 11:35:42 UTC
Description of problem:
(Split out of 1411275)
Repeatedly rebooting a rhel6 machine type guest will result in a hang about 1 in 20 or so times.
Version-Release number of selected component (if applicable):
How reproducible:
~1/20 times
Steps to Reproduce:
1. Take a 6.9 guest
2. Start it with:
/usr/libexec/qemu-kvm \
-name rhel7 \
-S -machine rhel6.6.0,accel=kvm,usb=off,smm=off \
-realtime mlock=off \
-cpu Opteron_G3 \
-sandbox off \
-m 7680 \
-smp 1, \
-uuid 49a3438a-70a3-4ba8-92ce-3a05e0934608 \
-no-user-config \
-nodefaults \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=discard \
-no-hpet \
-no-shutdown \
-global PIIX4_PM.disable_s3=1 \
-global PIIX4_PM.disable_s4=1 \
-boot order=c,menu=on,splash-time=3000,strict=on \
-drive file=rhel-guest-image-6.9-28.x86_64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=f65effa5-90a6-47f2-8487-a9f64c95d4f5,cache=none,discard=unmap,werror=stop,rerror=stop,aio=threads \
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x9,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \
-chardev stdio,mux=on,id=mon -mon chardev=mon,mode=readline --device isa-serial,chardev=mon \
-k en-us \
-device VGA \
-chardev file,id=bioslog,path=bioslog \
-device isa-debugcon,iobase=0x402,chardev=bioslog \
$*
3. repeatedly log into the guest and type 'reboot'
Actual results:
Expected results:
Additional info:
Already debugged to the 'TimerLast' variable overlaying the code in Seabios and getting incremented before boot.
Comment 2Dr. David Alan Gilbert
2017-03-13 15:54:11 UTC
Fixed in upstream commit c68aff57ce317d9f2d69d20eba893a10d964f316
Comment 5Miroslav Rezanina
2017-03-30 10:39:18 UTC
According to comment0,QE tried to reproduce with different host & unfix seabios seabios-1.9.1-4.el7.x86_64. and Guest reboot continuously for 2 hours. Guest still works well. So, see if QE can do some sanity test to verify this bug? e.g Guest reboot continuously with fixed seabios version(seabios-1.10.2-2.el7) for 24 hours. If guest still works well then we think this bug is fixed.
Comment 13Dr. David Alan Gilbert
2017-04-27 10:16:59 UTC
(In reply to FuXiangChun from comment #12)
> According to comment0,QE tried to reproduce with different host & unfix
> seabios seabios-1.9.1-4.el7.x86_64. and Guest reboot continuously for 2
> hours. Guest still works well. So, see if QE can do some sanity test to
> verify this bug? e.g Guest reboot continuously with fixed seabios
> version(seabios-1.10.2-2.el7) for 24 hours. If guest still works well then
> we think this bug is fixed.
Yes, if it's rebooting well then that's fine; it doesn't need 24h, 100 reboots should do.
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://access.redhat.com/errata/RHBA-2017:1855