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.

Description of problem:
libvirts use 3 URIs for migration:

1) source libvirtd URI
2) destination libvirtd URI
3) destination QEMU URI.

And if the destination QEMU URI is not specified by user, libvirt will try to execute "hostname()" on destination host to guess the hostname, and uses it to
form QEMU URI, (e.g. tcp://10.66.70.98).

So, If destination host is mis-configured, it will return a illed hostname which would not be able to address by source host, as a result, the migration will fail.

The problem here is that qemu discard the errors for migration failing (actually all of the errors related to getaddrinfo(3)/connect(2) failing?), so, libvirt can not get the exact error information for dignose log, an error like "An undefined error has occured" obviously is not what the user want to see. 

To get more info, see:
http://post-office.corp.redhat.com/mailman/private/virt-devel/2011-January/msg00239.html

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

another bug blocked by this problem: https://bugzilla.redhat.com/show_bug.cgi?id=619846

Thanks, Juan.

Hi,Juan/Osier

    would you please tell me is this issue duplicate Bug 584077 - QMP: Improve migrate command error info? seems bz584077 is key reason, libvirt call qmp.

Yes, this is the same as bug 584077.

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