We need a new machine type s390-ccw-virtio-rhel8.5.0 on AV. I do not know if this would be an update of en existing or a new machine type. Acceptance Criteria (proposed): a.) qemu-kvm -machine ? lists new machine type, default is -rhel8.5.0 b.) supported cross migration tests pass (host AV 8.4 <> AV 8.5, guest machine type -rhel8.4.0)
Verified this bug with: host kernel: 4.18.0-305.el8.s390x qemu-version: qemu-kvm-6.0.0-17.module+el8.5.0+11173+c9fce0bb.s390x Actual result: [root@l42 kar]# /usr/libexec/qemu-kvm -machine ? Supported machines are: none empty machine s390-ccw-virtio-rhel7.5.0 VirtIO-ccw based S390 machine rhel7.5.0 s390-ccw-virtio-rhel7.6.0 VirtIO-ccw based S390 machine rhel7.6.0 s390-ccw-virtio-rhel8.2.0 VirtIO-ccw based S390 machine rhel8.2.0 s390-ccw-virtio-rhel8.4.0 VirtIO-ccw based S390 machine rhel8.4.0 s390-ccw-virtio VirtIO-ccw based S390 machine rhel8.5.0 (alias of s390-ccw-virtio-rhel8.5.0) s390-ccw-virtio-rhel8.5.0 VirtIO-ccw based S390 machine rhel8.5.0 (default) boot up guest with new rhel8.5.0 machine type: QEMU 6.0.0 monitor - type 'help' for more information (qemu) guest could boot successfully as the result, set this bug to verified
(In reply to bfu from comment #7) > Verified this bug with: > host kernel: 4.18.0-305.el8.s390x > qemu-version: qemu-kvm-6.0.0-17.module+el8.5.0+11173+c9fce0bb.s390x > > Actual result: > [root@l42 kar]# /usr/libexec/qemu-kvm -machine ? > Supported machines are: > none empty machine > s390-ccw-virtio-rhel7.5.0 VirtIO-ccw based S390 machine rhel7.5.0 > s390-ccw-virtio-rhel7.6.0 VirtIO-ccw based S390 machine rhel7.6.0 > s390-ccw-virtio-rhel8.2.0 VirtIO-ccw based S390 machine rhel8.2.0 > s390-ccw-virtio-rhel8.4.0 VirtIO-ccw based S390 machine rhel8.4.0 > s390-ccw-virtio VirtIO-ccw based S390 machine rhel8.5.0 (alias of > s390-ccw-virtio-rhel8.5.0) > s390-ccw-virtio-rhel8.5.0 VirtIO-ccw based S390 machine rhel8.5.0 (default) > > boot up guest with new rhel8.5.0 machine type: > QEMU 6.0.0 monitor - type 'help' for more information > (qemu) > > guest could boot successfully > > as the result, set this bug to verified Boqiao, we usually run a cross migration test for new machine types. I'm on it. Please refer to our scoping https://issues.redhat.com/browse/RHELPLAN-75881
As the cross migration test have passed, change the status of this bug to verified
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 (virt:av bug fix and enhancement update), 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-2021:4684