Bug 915140

Summary:	ACPI power off doesn't work after do S3 during migration
Product:	Red Hat Enterprise Linux 6	Reporter:	Sibiao Luo <sluo>
Component:	qemu-kvm	Assignee:	Amit Shah <amit.shah>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	acathrow, amit.shah, areis, bsarathy, chayang, flang, juzhang, kraxel, mdeng, michen, mkenneth, pbonzini, quintela, qzhang, sluo, virt-maint, xfu
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	867787
Clones:	1074906 (view as bug list)		Environment:
Last Closed:	2014-06-05 22:16:15 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:
Bug Depends On:	867787, 875096, 1074901
Bug Blocks:	761491, 912287, 915139, 1074906

Comment 1 Sibiao Luo 2013-02-25 03:31:00 UTC

ACPI power off doesn't work after do S3 during migration. guest fail to shutdown successfully, it will stay at 'Power down'.

Comment 3 RHEL Program Management 2013-03-01 06:47:29 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 Paolo Bonzini 2014-03-10 14:23:03 UTC

Does this reproduce in RHEL7 too?

Comment 7 Sibiao Luo 2014-03-11 09:34:04 UTC

(In reply to Paolo Bonzini from comment #6)
> Does this reproduce in RHEL7 too?
yes, thanks for your kindly reminds, refer to Bug 1074906.

Comment 8 Ademar Reis 2014-06-05 22:16:15 UTC

S3/S4 support is tech-preview in RHEL6 and it'll be promoted to fully supported
at some point, but only in RHEL7.

Therefore we're closing all S3/S4 related bugs in RHEL6. New bugs will be
considered only if they're regressions or break some important use-case or
certification.

RHEL7 is being more extensively tested and effort from QE is underway in
certifying that this particular bug is not present there.

Please reopen with a justification if you believe this bug should not be
closed. We'll consider them on a case-by-case basis following a best effort
approach.


Thank you.