This is a feature request: When we add a new CPU model or a new version of a CPU model to QEMU, we need to manually add a corresponding copy of that CPU model definition to libvirt's cpu_map.xml. This increases the effort and time required to ship important bug fixes to customers (e.g. when a bug fix requires the introduction of a new CPU model version). libvirt should be able to expose new CPU models from QEMU through its existing CPU model API automatically, without the need to ship a cpu_map.xml update.
Bulk update: Move RHEL-AV bugs to RHEL8. Added RHV as dependent product and left in RHEL8. If a Resolution/Testing is required for RHEL9, then a clone will need to be created.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
See https://listman.redhat.com/archives/libvir-list/2022-June/232626.html for a proposal to address this
NB: Removed RHV as dependent product since this is a RHEL9 issue
(In reply to Tim Wiederhake from comment #8) > See https://listman.redhat.com/archives/libvir-list/2022-June/232626.html > for a proposal to address this Note, this proposal is incomplete https://listman.redhat.com/archives/libvir-list/2022-July/232891.html
Lets close this one correspondingly to qemu-kvm counterpart (bug 1697663). We will create new set of feature requests, once we get better understanding of what is actually the desired goal and how to implement it through the stack. Thanks.