What were you trying to do that didn't work?

As subject

What is the impact of this issue to you?

The actual CPU model for domain host-model doesn't match the expected result from https://libvirt.org/formatdomain.html

Please provide the package NVR for which the bug is seen:

rhel9:
libvirt-10.10.0-3.el9.x86_64
qemu-kvm-9.1.0-7.el9.x86_64

rhel10:
libvirt-10.10.0-2.el10.x86_64
qemu-kvm-9.1.0-8.el10.x86_64

How reproducible is this bug?:

100%

Steps to reproduce

1. Get the host cpu model on AMD EPYC 7313 16-Core Processor

# virsh capabilities --xpath /capabilities/host/cpu/model
<model>EPYC-Milan-v2</model>

1. Start a domain with host-model cpu then check its live CPU xml:

# virsh dumpxml rhel-caps --xpath //cpu
<cpu mode="host-model" check="partial"/>
# virsh dumpxml rhel-caps --xpath //cpu/model
<model fallback="forbid">EPYC-Milan</model>

As the libvirt domain XML doc, the expected live CPU model is EPYC-Milan-v2

host-model
    The host-model mode is essentially a shortcut to copying host CPU definition from capabilities XML into domain XML. Since the CPU definition is copied just before starting a domain, exactly the same XML can be used on different hosts while still providing the best guest CPU each host supports.

Expected results

EPYC-Milan-v2

Actual results

EPYC-Milan