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.
Description of problem:
Boot a RHEL6.3 guest and suspend guest to mem, I used Amit's private seabios tree that enabled S3. But guest got reboot instead wakeup. This issue happens no matter guest is attached with virtio driver or not. Re-test with kernel-250, have not this problem. So should be a regression, not sure whether related the "KVM steal time suspend/resume bugfix" patches in kernel-251.
seabios tree that enabled S3:
https://bugzilla.redhat.com/show_bug.cgi?id=761586#c7
Version-Release number of selected component (if applicable):
Host:
kernel-2.6.32-251.el6.x86_64
qemu-kvm-0.12.1.2-2.246.el6.x86_64
seabios-0.6.1.2-12.enableS3S4.v1.el6.x86_64
Guest:
kernel-2.6.32-251.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Boot a guest even there's no virtio driver
/usr/libexec/qemu-kvm -M rhel6.3.0 -cpu Conroe -enable-kvm -m 4G -smp 2,sockets=1,cores=2,threads=1 -name rhel6.3 -uuid 4c84db67-faf8-4498-9829-19a3d6431d9d -rtc base=localtime,driftfix=slew -drive file=/home/rhel6.3-64-virtio.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=native -device ide-drive,bus=ide.0,unit=1,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,id=net0,mac=00:1a:2a:42:10:66,bus=pci.0,addr=0x3 -boot c -monitor stdio -drive file=/home/boot.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -spice port=5930,disable-ticketing -vga qxl -global qxl-vga.vram_size=33554432 -qmp tcp:0:4444,server,nowait
2. Inside guest: echo mem > /sys/power/state
3. Resume guest by click PS/2 mouse or enter some keys with keyboard or send "system_wakeup" qemu command.
Actual results:
Guest reboot.
Expected results:
Guest should resume and come back to the state before s3.
Additional info:
Re-test with virtio block and virtio nic, hit the same problem.
Re-test with kernel-250, succeed to resume with the given command line.
(In reply to comment #3)
> Update:
> Test on the host installed kernel-152. then suspend host to mem. Host can
> resume successfully.
Sorry for the typo, host kernel should be kernel-2.6.32-251.el6.x86_64.
QE has confirmed the guest resumes from s3 as expected (without reboots) if kvmclock is disabled by adding '-cpu host,-kvmclock' to the qemu invocation.
There is also a separate bug where with virtio devices, the mouse and keyboard stop responding after resume from s3, this may be related to spice or virtio-serial, a new bug will be opened for that.
Comment 6RHEL Program Management
2012-03-21 22:29:29 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Hi, Marcelo and Amit
I'm verifying this bug with the kernel-260, but blocked by bug 808391. Could you guys help look at bug 808391? It's not only 1/20 reproduced. Sometimes it happens at the first time s3, and sometimes it will happens after 1 or more cycles s3/resume and then reboot guest.
And I tested rhel6.3-32 guest, sometimes guest will still reboot instead of wakeup. But it's not 100% reproduced. I hit it twice after 15~20 times attempts.
So, I will re-assign this bug.
(In reply to comment #14)
> And I tested rhel6.3-32 guest, sometimes guest will still reboot instead of
> wakeup. But it's not 100% reproduced. I hit it twice after 15~20 times
> attempts.
> So, I will re-assign this bug.
Please collect logs with the rhel6.3-32 bits guest (which appears immune to bug 808391) and kernel newer than kernel-2.6.32-258.el6.
Marcelo,
I could not reproduce it after update guest kernel to latest 262 version after 40 times repeat. Will test 64bit rhel6.3 guest later and if both of them pass, I will change the status to VERIFIED.
(In reply to comment #16)
> Marcelo,
> I could not reproduce it after update guest kernel to latest 262 version after
> 40 times repeat. Will test 64bit rhel6.3 guest later and if both of them pass,
> I will change the status to VERIFIED.
OK, please do that. It should be enough to verify on 32-bits (BZ 808391 is a separate bug).
Because the fix is already submitted, change back to ON_QA.
Bug 808391 is moved to 6.4.0, so you cannot complete the testing until 6.4. Should you mark this fix verified based on only the 32-bit tests? That should be appropriate for S3, which is not supported anyway.
Hi, Karen and Marcelo
In kernel-251:
rhel6.3-32: not very easy to reproduce, i just reproduced twice after about 30 times attempts.
rhel6.3-64: 100% reproduced on all my attempts.
In kernel-262:
rhel6.3-32: Based on comment 16, can not reproduce after 40 times repeat.
rhel6.3-64: can not reproduce this bug. Although it may suffer bug 808391, but in some rounds of test, guest hits neither 808391 nor this bug 803132.
So, based on above, I would like to set the status to VERIFIED. Please correct me if it's wrong to do this.
Thanks,
Qunfang
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/RHSA-2012-0862.html