622960 – operation failed: Migration unexpectedly failed

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 622960 - operation failed: Migration unexpectedly failed

Summary: operation failed: Migration unexpectedly failed

Keywords:
Status:	CLOSED DUPLICATE of bug 618562
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	libvirt
Sub Component:
Version:	6.0
Hardware:	x86_64
OS:	Linux
Priority:	low
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Daniel Veillard
QA Contact:	Virtualization Bugs
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2010-08-10 21:52 UTC by Patrick Calhoun
Modified:	2010-08-11 15:49 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2010-08-11 15:44:46 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Patrick Calhoun 2010-08-10 21:52:39 UTC

Description of problem:

Cannot live migrate KVM guests.  libvirtError: operation failed: Migration unexpectedly failed

Version-Release number of selected component (if applicable):
libvirt-0.8.1-13.el6.x86_64

How reproducible:

Always

Steps to Reproduce:
1.  Create a guest qemu/kvm VM  (arch/network/storage doesn't seem to matter)
2.  Start guest.
3.  Attempt to live migrate guest
  
Actual results:

Unable to migrate guest:
 Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/migrate.py", line 457, in _async_migrate
    vm.migrate(dstconn, migrate_uri, rate, live, secure)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1387, in migrate
    self._backend.migrate(destconn.vmm, flags, newname, interface, rate)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 511, in migrate
    if ret is None:raise libvirtError('virDomainMigrate() failed', dom=self)
libvirtError: operation failed: Migration unexpectedly failed


Expected results:

Live migration

Additional info:

The two physical machines resolve one-another through /etc/hosts.  The machines are both x86_64, but one has the feature 'dca' according to `virsh capabilities`.  All of the migrations I've tried are through qemu+ssh.

Comment 2 RHEL Program Management 2010-08-10 22:18:34 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Eric Blake 2010-08-10 23:07:15 UTC

Is SELinux enabled (getenforce)?  Are ports 49152-49215 open, or a subset, if you are using the migrate URI to specify a specific port (iptables -L)?  What command line are you using to attempt the migration?  Does /var/log/libvirt/qemu/guest.log or /var/log/messages contain any clues?

At this point, I'm guessing that it is mostly a configuration issue, at which point this would be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=618562 regarding the poor quality of documentation on setting up migration and the poor quality of error reporting on failed migrations.

Comment 4 Patrick Calhoun 2010-08-11 15:18:23 UTC

Here is the migration command I used:
# virsh migrate --live guest qemu+ssh://machineB/system

I assumed that tunneling over ssh would bypass the INPUT chain on the target system, or at least make the traffic appear to be from the "lo" interface.  Apparently, it does not.

A simple `iptables -I INPUT -j ACCEPT` on the systems proved to allow things to work correctly.  (I had SELinux permissive already)


I think you're right, this can be considered a documentation issue.

Comment 5 Eric Blake 2010-08-11 15:44:46 UTC


*** This bug has been marked as a duplicate of bug 618562 ***

Comment 6 Eric Blake 2010-08-11 15:49:29 UTC

One other point - true tunneling through virsh requires use of the --tunnelled argument to 'virsh migrate', but that is still a work in progress to make it more robust.  The command line you issued asked for qemu to set up the migration connection rather than virsh, and qemu requires the awkward large range of ports to be open since it is not piggy-backing on the virsh connection.

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