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.
Hi, Haim
I can reproduce this issue with qemu-kvm-348 and qemu-kvm-355_4.2 build. And I don't think this is a problem. because in from qemu-kvm-350, data-plane patches are backport and there a new parameters "dev-prop: x-data-plane = off" introduced for virtio block.
So when do migration between older qemu-kvm (lower than qemu-kvm-350) and newer version (>= qemu-kvm-350), the virtio block device parameters are changed so migration load failed.
"(qemu) info qtree" compare:
# diff qemu-kvm-348.txt qemu-kvm-355_4.2.txt
......
63a64
> dev-prop: serial = "5fa9eac5-720d-448c-8"
64a66
> dev-prop: x-data-plane = off
......
And also, as customers will not use our internal build, so we just need to make sure migration between final builds pushed out with errata have no problem is ok.
So I tested the following combination of cross version migration:
(1) qemu-kvm-355(released 6.4) <-> qemu-kvm-355_4.1
(2) qemu-kvm-355(released 6.4) <-> qemu-kvm-355_4.2
(3) qemu-kvm-355_4.1 <-> qemu-kvm-355_4.2
Al the above 3 items passed after ping-pong migration with the same command line as bug description.
=================
Hi, Juan
Could you have a double confirm?
Thanks,
Qunfang
Hi, Juan
This issue may be not related to x-data-plane property, may be related to bug 869981.
Because I just re-test again with rhel6.3 host <-> rhel6.4.z cross version migration, migration succeeds though there's "data-plane" property in "info qtree" output of rhel6.4, but not existed in the output of rhel6.3.
Anyway, there's no problem between any of the following host versions: rhel6.3 release; rhel6.4 release, rhel6.4-z build.
(In reply to comment #2)
[...]
> Anyway, there's no problem between any of the following host versions:
> rhel6.3 release; rhel6.4 release, rhel6.4-z build.
That's correct. We don't support internal builds, created during the development phase. If the migration works betweenn 6.3 and 6.4{,.z}, then there's no problem.