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

virsh hypervisor-cpu-compare reports unexpected msg if use just the cpu element from domcaps,

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 domcapabilities --xpath /domainCapabilities/cpu) 

Expected results

CPU described in /dev/fd/63 is identical to the CPU provided by hypervisor on the host

Actual results

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

The usage is incorrect , so the document should be more clearly to tell that we should use  <cpu></cpu> element as a part of FILE in virsh hypervisor-cpu-compare FILE