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:
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

How reproducible:
100%

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
# pm-suspend

Actual results:
The guest cannot resume.

Expected results:
The guest can resume normally.

Additional info:

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
> 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?

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 ***