Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1100671

Summary:	Migration of a VM fails if another API allowed during migration takes a long time to finish
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Kurik <jkurik>
Component:	libvirt	Assignee:	Jiri Denemark <jdenemar>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.0	CC:	acathrow, audgiri, bazulay, dallan, dyuan, ederevea, iheim, jdenemar, jentrena, lpeer, mzhan, ofrenkel, pdwyer, pm-eus, stefanha, tdosek, vfeenstr, ydu, yeylon, zhwang, zpeng
Target Milestone:	rc	Keywords:	Upstream, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libvirt-0.10.2-29.el6_5.9	Doc Type:	Bug Fix
Doc Text:	Cause: Libvirt cancels migration when it cannot access QEMU monitor for more that 30 seconds to get migration status. Consequence: When a user asks libvirt to query some data from QEMU during an ongoing migration and QEMU takes more than 30 seconds to answer this query, the query for migration status times out and libvirt cancels the migration. This is more likely to happen on a loaded host in a RHEV environment which repeatedly asks libvirt for virtual disk statistics. Fix: Since libvirt checks for migration status every 50ms, it is safe to ignore the timeout and just try asking again. Result: Migration in RHEV environment is no longer canceled when QEMU is slow to respond.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-10 12:24:32 UTC	Type:	---
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:	1083238
Bug Blocks:

Description Jan Kurik 2014-05-23 10:37:40 UTC

This bug has been copied from bug #1083238 and has been proposed
to be backported to 6.5 z-stream (EUS).

Comment 6 zhenfeng wang 2014-05-30 03:04:50 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 31 in bug 1083238

Comment 8 errata-xmlrpc 2014-06-10 12:24:32 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

Comment 9 Jiri Denemark 2014-07-24 11:43:29 UTC

*** Bug 1122908 has been marked as a duplicate of this bug. ***