Bug 1107821
Summary: | rdma migration: seg if destination isn't listening | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Dr. David Alan Gilbert <dgilbert> |
Component: | qemu-kvm | Assignee: | Dr. David Alan Gilbert <dgilbert> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.1 | CC: | hhuang, huding, juzhang, michen, mrezanin, qzhang, rbalakri, shu, virt-maint, xfu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-1.5.3-69.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-03-05 08:10:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dr. David Alan Gilbert
2014-06-10 17:54:43 UTC
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 |