Bug 2022602
| Summary: | Update machine type compatibility for QEMU 6.2.0 update [s390x][RHEL-9.0.0] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Miroslav Rezanina <mrezanin> | ||||
| Component: | qemu-kvm | Assignee: | Thomas Huth <thuth> | ||||
| qemu-kvm sub component: | Machine Types | QA Contact: | smitterl | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | low | ||||||
| Priority: | high | CC: | bfu, coli, jinzhao, juzhang, lijin, ngu, smitterl, thuth, virt-maint, yfu | ||||
| Version: | 9.0 | Keywords: | RFE, Triaged | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 9.0 | ||||||
| Hardware: | s390x | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | qemu-kvm-6.2.0-1.el9 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 2022606 (view as bug list) | Environment: | |||||
| Last Closed: | 2022-05-17 12:25:10 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2031043 | ||||||
| Attachments: |
|
||||||
|
Description
Miroslav Rezanina
2021-11-12 06:52:22 UTC
Added the machine type epic to the blocks list for tracking... as agreed assign to me, ETA for pre-verification 12/22 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.
Created attachment 1847211 [details]
domain xml
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 |