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.
Bug 915139 - Do S3 will comeback(wakup) automatically after migration
Summary: Do S3 will comeback(wakup) automatically after migration
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Hai Huang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 867787 875096 915140 1074901 1074906
Blocks: 761491 912287
TreeView+ depends on / blocked
 
Reported: 2013-02-25 03:24 UTC by Sibiao Luo
Modified: 2014-03-11 09:21 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 867787
Environment:
Last Closed: 2014-03-10 14:24:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Sibiao Luo 2013-02-25 03:26:09 UTC
Run state is not checked on destination machine -- if incoming VM is in suspended state, the dest should continue to be in suspended state. 
so there is problem that it will comeback(wakup) automatically after migration.

Comment 3 RHEL Program Management 2013-03-01 06:47:38 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 5 Orit Wasserman 2013-05-07 15:19:46 UTC
Fixing this issue will require a change to migration protocol.
postponed due to capacity.

Comment 8 Paolo Bonzini 2014-03-10 14:23:07 UTC
This is just how migration will work in RHEL6... is there a bug for RHEL7?  There are more chances of fixing it there.  If you create such a bug, we can close this one as DEFERRED.

Comment 9 Paolo Bonzini 2014-03-10 14:24:12 UTC
Yes, there is bug 875096.


Note You need to log in before you can comment on or make changes to this bug.