Red Hat Bugzilla – Bug 834511
Disallow system to enter S3 or S4 states if virtio devices present
Last modified: 2013-01-07 23:37:44 EST
virtio drivers in the RHEL5 kernel are not capable of saving and restoring state information across system suspend states.
Instead of falsely advertising suspend support, and then failing on restore, disallow suspend of the OS itself.
This means that the OS will refuse to enter S3 (suspend-to-memory) and S4 (suspend-to-disk) states if any virtio devices are found.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Setting to Assigned first according to comment 7.
> Verified on kernel-2.6.18-330.el5 (guest kernel), s4 passed, but there's
> some problem with s3, amit is helping to check it.
> RHEL5.9-32 & 64:
> S3: Guest calltrace at the second time doing s3.
Even after S3, guest network remains available. The display doesn't come back, though. I'm suspecting it's a cirrus driver problem. That's a separate bz, and for the purposes of this bz, as long as s3 and s4 states aren't entered, we can leave this as it is.
We could open a new bug for the cirrus behaviour, but I doubt it'll be fixed for RHEL5, especially given that we'll disable bios advertisement of s3/s4 for RHEL5 guests.
Setting to ON_QA again.
Ok, I will set this bug to VERIFIED according to comment 7,comment 9, comment 10. Create bug 842942 to track the call trace issue.
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.