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

virsh hypervisor-cpu-compare reports host CPU as superset of guest CPU configuration from virsh capabilities output

What is the impact of this issue to you?

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

]# rpm -q libvirt qemu-kvm;uname -r
libvirt-10.10.0-6.el9.x86_64
qemu-kvm-9.1.0-14.el9.x86_64
5.14.0-565.el9.x86_64

How reproducible is this bug?:

100%

Steps to reproduce

~]# virsh hypervisor-cpu-compare <( virsh capabilities --xpath /capabilities/host/cpu ) 

Expected results

 The CPU provided by hypervisor on the host is incompatible with the CPU described in ...

Actual results:

The CPU provided by hypervisor on the host is a superset of CPU described in /dev/fd/63