Mirek - in your opinion, is this different than bug 2131982? If so, then please be sure this bug gets added to the machine type epic; otherwise, close as duplicate.

Yes, this is different. We can introduce new machine type after rebase is done but compatibility has to be solved before rebase.

There is nothing that needs to be updated as of now (-rc2 time), and I don't see anything on the list that would need to be included.

Moving to POST; I expect we can simply close this when 7.2 is out.

Pre-verify with qemu-kvm-7.2.0-2.el9

# /usr/libexec/qemu-kvm -M ?
Supported machines are:
virt                 RHEL 9.2.0 ARM Virtual Machine (alias of virt-rhel9.2.0)
virt-rhel9.2.0       RHEL 9.2.0 ARM Virtual Machine (default)
virt-rhel9.0.0       RHEL 9.0.0 ARM Virtual Machine
none                 empty machine

Test Environment:
Host Distro: RHEL-9.2.0-20221220.0 BaseOS aarch64
Host Kernel: kernel-5.14.0-217.el9.aarch64
QEMU: qemu-kvm-7.2.0-2.el9.aarch64
edk2: edk2-aarch64-20220826gitba0e0e4c6a-2.el9.noarch
Guest: RHEL.9.2.0

Results Analysis:
From 83 tests executed, 82 passed and 0 warned - success rate of 98.80% (excluding SKIP and CANCEL)
The failed case is due to an existing all platform bug

New bugs(0):
Existing bugs(0):

Job link:
http://10.0.136.47/7363114/results.html

Will also update the test result of virt-9.0.0 machine type later, because it also includes a change: compat_props_add(mc->compat_props, hw_compat_rhel_9_1, hw_compat_rhel_9_1_len);

Test result of virt-rhel9.0.0: http://10.0.136.47/7365959/results.html

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 (Moderate: qemu-kvm security, 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/RHSA-2023:2162