Bug 834511
Summary: | Disallow system to enter S3 or S4 states if virtio devices present | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Amit Shah <amit.shah> |
Component: | kernel | Assignee: | Amit Shah <amit.shah> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.9 | CC: | bcao, juzhang, michen, qzhang, syeghiay, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kernel-2.6.18-325.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-08 04:37:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Amit Shah
2012-06-22 07:36:30 UTC
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 a release. > 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. http://rhn.redhat.com/errata/RHBA-2013-0006.html |