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 1100642 - After migration failed in last phase, didn't resume VM on source host
Summary: After migration failed in last phase, didn't resume VM on source host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.5
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1098833
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-23 09:28 UTC by Jan Kurik
Modified: 2019-04-28 10:02 UTC (History)
19 users (show)

Fixed In Version: libvirt-0.10.2-29.el6_5.9
Doc Type: Bug Fix
Doc Text:
Cause: Libvirt did not properly cancel migration of QEMU domains in case it detected an error which did not also cause QEMU to cancel the migration by itself. For example, crashed libvirt daemon on destination host would cause libvirt to cancel migration while QEMU will continue sending data to the destination QEMU. Consequence: Once QEMU finishes sending the data and pauses guest CPUs, the domain will likely be left in paused state because libvirt tried to resume the domain before QEMU paused it. Fix: If libvirt detects an error during migration, it tells QEMU to cancel ongoing migration. Result: When libvirt resumes a domain after failed migration, the migration process in QEMU is already canceled and thus QEMU does not stop guest CPUs afterwards and the domain remains running.
Clone Of:
Environment:
Last Closed: 2014-06-10 12:24:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0682 0 normal SHIPPED_LIVE libvirt bug fix update 2014-06-10 16:23:28 UTC

Description Jan Kurik 2014-05-23 09:28:51 UTC 
This bug has been copied from bug #1098833 and has been proposed
to be backported to 6.5 z-stream (EUS).
Comment 6 zhoujunqin 2014-05-30 05:57:16 UTC 
I can reproduce this bug with libvirt-0.10.2-29.el6_5.8 and can get the expect result with the libvirt-0.10.2-29.el6_5.9, so mark this bug verified. BTW, For more detials about the reproduce steps and verify steps, you can refer the comment 19 in bug 1098833.
Comment 8 errata-xmlrpc 2014-06-10 12:24:25 UTC 
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-2014-0682.html
Note You need to log in before you can comment on or make changes to this bug.