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
libvirt should fail migration and provide error msg when migration from a newer host to an older.
Version:
rhel6.5:libvirt-0.10.2-29.el6_5.2.x86_64
rhel7.0:libvirt-1.1.1-14.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1:prepare two host,on with rhel6.5, the other is rhel7.0
2:prepare a healthy guest on rhel6.5 host
3:migrate the guest to rhel7.0, it can worked well.
4:migrate the guest back to rhel6.5
# virsh migrate --live rhel6 qemu+ssh://10.66.84.16/system --verbose
root.84.16's password:
Migration: [100 %]
it seems worked, but actually, qemu-kvm can't support this, after migration, the guest can't be used.
so libvirt should forbid this action, and provide some error msg to customer.
Actual results：
Expected results:
Additional info:
Knowing what versions of qemu-kvm are able to migrate between each other is not a libvirt's business. I'm moving this bug to QEMU for investigating why the guest doesn't work after migration while migration seems to have succeeded.