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:
Trivially able to seg qemu by attempting to migrate to a destination that isn't listening

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.0.0-1.el7ev.test.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Get a pair of machines connected via ib
2. Start a qemu 
3. migrate -d rdma:ibpair:4444
   where 'ibpair' is the IP address of the other host, which you can ping via it's ib interface but doesn't have a receiving QEMU running.

Actual results:
seg

Expected results:
a nice error

Additional info:
Probably https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg02994.html

Fixed by http://patchwork.ozlabs.org/patch/321271/ that never got merged upstream.

Fix included in qemu-kvm-1.5.3-69.el7

Verified on qemu-kvm-1.5.3-75.el7.x86_64:

if des has no qemu-kvm listening:

(qemu) migrate x-rdma:192.168.100.1:5555
source_resolve_host RDMA Device opened: kernel name mlx4_0 uverbs device name uverbs0, infiniband_verbs class device path /sys/class/infiniband_verbs/uverbs0, infiniband class device path /sys/class/infiniband/mlx4_0, transport: (2) Ethernet
rdma_get_cm_event != EVENT_ESTABLISHED after rdma_connect: Resource temporarily unavailable
RDMA ERROR: connecting to destination!
migrate: RDMA ERROR: connecting to destination!


There is proper error report, and qemu-kvm works correctly.

During test, found another issue:

Bug 1152969 - Qemu-kvm got stuck when migrate to wrong RDMA ip

symptom is different, list here for reference.

According to comment 5, this bug has been fixed, as to problem in comment 6, the bug has been fixed either.

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.

https://rhn.redhat.com/errata/RHSA-2015-0349.html