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.
Description of problem:
zerocopy migration doesn't support ipv6, migration would fail
Version-Release number of selected component (if applicable):
hosts info: kernel-4.18.0-408.el8.x86_64 && qemu-kvm-6.2.0-18.module+el8.7.0+15999+d24f860e.x86_64
guest info: kernel-4.18.0-410.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Boot a guest on source host
2.Boot a guest on destination host with '-incoming defer'
3.Enable multifd capability on src and dst host, then enable zero-copy-send on src host
4.Start migration from src to dst host through ipv6 address
(dst qemu) {"execute": "migrate-incoming", "arguments": {"uri": "tcp:[::]:4000"}, "id": "y7pmQB4S"}
(src qemu) {"execute": "migrate", "arguments": {"uri": "tcp:[2620:52:0:4982:f4d:42ef:2c85:e89d]:4000"}, "id": "idd8hXvl"}
Actual results:
Migration would fail:
(qemu) 2022-08-03T08:13:13.022219Z qemu-kvm: Wrong cmsg in errqueue: Protocol wrong type for socket
2022-08-03T08:13:13.022290Z qemu-kvm: failed to save SaveStateEntry with id(name): 1(ram)
(qemu) info migrate
globals:
store-global-state: on
only-migratable: off
send-configuration: on
send-section-footer: on
decompress-error-check: on
clear-bitmap-shift: 18
Migration status: failed
total time: 0 ms
Expected results:
Migration will succeed
Additional info:
I would clone this bug for RHEL 9.1.0 if can reproduce
(In reply to Leonardo Bras from comment #1)
> Hello Li Xiaohui,
>
> I think I got the issue. Please try this brew and see if migration succeeds
> over IPV6:
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=46954537
Hi leonardo, thanks for your quick debug and fix. I may have to test several days later since some high priority bugs also need to be handled.
This bug should be fixed on RHEL-8.7 since I tried the 6.2.0-20.module+el8.7.0+16689+53d59bc2, didn't hit this bug, zerocopy migration through ipv6 succeeded.
So I would mark this bug as currentrelease.
Description of problem: zerocopy migration doesn't support ipv6, migration would fail Version-Release number of selected component (if applicable): hosts info: kernel-4.18.0-408.el8.x86_64 && qemu-kvm-6.2.0-18.module+el8.7.0+15999+d24f860e.x86_64 guest info: kernel-4.18.0-410.el8.x86_64 How reproducible: 100% Steps to Reproduce: 1.Boot a guest on source host 2.Boot a guest on destination host with '-incoming defer' 3.Enable multifd capability on src and dst host, then enable zero-copy-send on src host 4.Start migration from src to dst host through ipv6 address (dst qemu) {"execute": "migrate-incoming", "arguments": {"uri": "tcp:[::]:4000"}, "id": "y7pmQB4S"} (src qemu) {"execute": "migrate", "arguments": {"uri": "tcp:[2620:52:0:4982:f4d:42ef:2c85:e89d]:4000"}, "id": "idd8hXvl"} Actual results: Migration would fail: (qemu) 2022-08-03T08:13:13.022219Z qemu-kvm: Wrong cmsg in errqueue: Protocol wrong type for socket 2022-08-03T08:13:13.022290Z qemu-kvm: failed to save SaveStateEntry with id(name): 1(ram) (qemu) info migrate globals: store-global-state: on only-migratable: off send-configuration: on send-section-footer: on decompress-error-check: on clear-bitmap-shift: 18 Migration status: failed total time: 0 ms Expected results: Migration will succeed Additional info: I would clone this bug for RHEL 9.1.0 if can reproduce