Red Hat Bugzilla – Bug 1012822
RHEL5.10 guest cannot resume after S3
Last modified: 2013-09-30 00:22:05 EDT
Description of problem:
RHEL5.10(32 bit) guest cannot resume after S3.
Version-Release number of selected component (if applicable):
The host kernel is kernel-3.10.0-28.el7.x86_64
The version of qemu-kvm is qemu-kvm-rhev-1.5.3-6.el7.x86_64
The guest kernel is kernel-2.6.18-371.el5PAE
Steps to Reproduce:
1. Boot RHEL5.10 (32 bit) guest
/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm -m 2048 -smp 4,sockets=2,cores=2,threads=1 -name rhel5.10-32 -uuid 6afa5f93-2d4f-420f-81c6-e5fdddbd1c83 -drive file=/home/RHEL-Server-5-10.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=40c061dd-5d60-4fc5-865f-55db700407f0,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -device pci-assign,host=00:19.0 -vnc :1 -monitor stdio
2. On guest, do S3
The guest cannot resume.
The guest can resume normally.
We disabled RHEL5 as a guest S3/S4 in https://bugzilla.redhat.com/show_bug.cgi?id=834511
The guest should not even enter S3 state because of that commit. Does pm-suspend actually succeed for you?
(In reply to Amit Shah from comment #1)
> We disabled RHEL5 as a guest S3/S4 in
> The guest should not even enter S3 state because of that commit. Does
> pm-suspend actually succeed for you?
When first run "pm-suspend", guest changes black and then comes back to desktop immediately but guest and the network are always working.
When second run "pm-suspend", guest displays black screen for long time and does not resume. Kernel gets calltrace same as Bug 842942.
OK, so it's the same thing reported earlier, and it's most likely failing due to the console devices. We won't support s3/s4 on rhel5 guests, and hence won't dig into this further.
*** This bug has been marked as a duplicate of bug 842942 ***