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.
DescriptionDr. David Alan Gilbert
2015-04-10 12:23:23 UTC
Created attachment 1013118[details]
xml for broken vm
Description of problem:
This VM migrates fine usign TCP but with RDMA it fails
Version-Release number of selected component (if applicable):
source: qemu-kvm-rhev-2.1.2-23.el7_1.1.x86_64
dest: qemu-kvm-rhev-2.3.0-0.el7.dgilbert20150410a.x86_64
How reproducible:
100%
Steps to Reproduce:
1. See xml attached; 7.1 machine type vm started on 7.1
2. migrate to 7.2 using RDMA - virsh migrate --live --migrateuri rdma://ibpair f20-414 qemu+ssh://ibpair/system --listen-address 192.168.99.13
Actual results:
Migration fails, error seen in source logs:
RDMA ERROR: ram blocks mismatch #3! Your QEMU command line parameters are probably not identical on both the source and destination.
Expected results:
A working migration
Additional info:
Comment 2Dr. David Alan Gilbert
2015-04-10 14:33:42 UTC
hmm, the RDMA code seems to be keying off the 'offset' which I think is the offset in RAMBlock address space - that's not in any way intended to stay the same across versions
'mismatch #3' is when qemu_rdma_registration_stop failed to find a matching RAMBlock.
Comment 3Dr. David Alan Gilbert
2015-04-17 11:04:02 UTC
Just confirmed this also affects 7.1 by itself with hotplug, hotplug a device on the source, but have it on the command line on the destination and it fails in a similar way.
Comment 8Miroslav Rezanina
2015-07-24 11:08:07 UTC
source host:
qemu-kvm-1.5.3-60.el7.x86_64
Reproduced with qemu-kvm-rhev-2.3.0-8.el7.x86_64 on target host:
(qemu) migrate -d x-rdma:192.168.0.21:6666
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: (1) Infiniband
(qemu)
(qemu)
(qemu)
(qemu)
(qemu) info migrateRDMA ERROR: ram blocks mismatch #1! Your QEMU command line parameters are probably not identical on both the source and destination.
Verify failed with qemu-kvm-rhev-2.3.0-13.el7.x86_64 on target host:
(qemu) migrate -d x-rdma:192.168.0.21:6666
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: (1) Infiniband
(qemu) RDMA ERROR: ram blocks mismatch #1! Your QEMU command line parameters are probably not identical on both the source and destination.
David, could you have a look?
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/RHBA-2015-2546.html
Created attachment 1013118 [details] xml for broken vm Description of problem: This VM migrates fine usign TCP but with RDMA it fails Version-Release number of selected component (if applicable): source: qemu-kvm-rhev-2.1.2-23.el7_1.1.x86_64 dest: qemu-kvm-rhev-2.3.0-0.el7.dgilbert20150410a.x86_64 How reproducible: 100% Steps to Reproduce: 1. See xml attached; 7.1 machine type vm started on 7.1 2. migrate to 7.2 using RDMA - virsh migrate --live --migrateuri rdma://ibpair f20-414 qemu+ssh://ibpair/system --listen-address 192.168.99.13 Actual results: Migration fails, error seen in source logs: RDMA ERROR: ram blocks mismatch #3! Your QEMU command line parameters are probably not identical on both the source and destination. Expected results: A working migration Additional info: