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.
DescriptionMiroslav Rezanina
2021-11-12 06:52:22 UTC
With rebase to QEMU 6.2.0 we have to update compatibility bits for qemu-kvm package so we keep old machine types stable.
Please add necessary changes to ensure all machine types are compatible with previous versions.
There is an error when migrating between 6.1 and 6.2. Thomas, can you help confirm this is related to machine compat?
Setup:
-------
Both hosts:
kernel-5.14.0-32.el9.s390x
libvirt-7.10.0-1.el9.s390x
compose ID RHEL-9.0.0-20211214.2
Source host: qemu-kvm-6.1.0-7.el9.s390x
Destination host: qemu-kvm-6.2.0-1.el9.s390x
Migrate VM w/ vsock device from source to host:
-----------------------------------------------
[source-host]# virsh migrate avocado-vt-vm1 --live --verbose qemu+ssh://<destination-ip>/system
error: internal error: qemu unexpectedly closed the monitor: 2021-12-21T16:19:58.347819Z qemu-kvm: Features 0x130000002 unsupported. Allowed features: 0x139000000
qemu-kvm: Failed to load virtio-vhost_vsock:virtio
qemu-kvm: error while loading state for instance 0x0 of device '/fe.0.0008/virtio-vhost_vsock'
qemu-kvm: load of migration failed: Operation not permitted
Additional info:
1. CPU definition (will attach full domain xml) and machine type 8.5 used for migration:
<os>
<type arch='s390x' machine='s390-ccw-virtio-rhel8.5.0'>hvm</type>
<boot dev='hd'/>
</os>
<cpu mode='custom' match='exact' check='partial'>
<model fallback='forbid'>gen15a-base</model>
<feature policy='require' name='vx'/>
<feature policy='require' name='vxeh'/>
</cpu>
2. Migration succeeds when both source and destination have the same component versions.
3. A VM can be started successfully on the destination host with the same domain xml (w/ vsock device).
4. virsh dumpxml --migratable contains vsock device.
Can't reproduce with QEMU 6.0 <> 6.2.
As discussed on IRC, as 6.2 will be released but 6.1 not, I'm lowering severity to low.
Not reproduced with:
Source:
libvirt-7.6.0-2.el9.s390x
qemu-kvm-6.0.0-13.el9_b.5.s390x
Destination:
libvirt-7.10.0-1.el9.s390x
qemu-kvm-6.2.0-1.el9.s390x
# avocado run --vt-type libvirt --vt-machine-type s390-virtio virsh.migrate_vm.positive_testing.live_migration.bi_directional.without_postcopy --vt-connect-uri qemu:///system
JOB ID : 1406ddabe2aee3b98c3ced43b7d31e0c2aead7a7
JOB LOG : /root/avocado/job-results/job-2021-12-23T08.40-1406dda/job.log
(1/1) type_specific.io-github-autotest-libvirt.virsh.migrate_vm.positive_testing.live_migration.bi_directional.without_postcopy: PASS (144.81 s)
RESULTS : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB TIME : 145.14 s
(Double checked in test log that the domain was set up w/ vsock, cpu and machine type as indicated in description.)
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 (new packages: qemu-kvm), 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://access.redhat.com/errata/RHBA-2022:2307