Cause: When libvirt could not find a suitable CPU model for host CPU, it would not provide CPU topology in host capabilities even though the topology was detected correctly.
Consequence: Applications that want to examine host CPU topology but otherwise do not care about CPU model could not see the topology in host capabilities.
Fix: Host capabilities XML now contains host CPU topology even if host CPU model is unknown.
Result: Applications can rely on host CPU topology to always be present in capabilities XML unless detecting the topology itself failed.
This bug has been copied from bug #866999 and has been proposed
to be backported to 6.3 z-stream (EUS).
Sent for review: http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-October/msg01258.html
Verified on libvirt-0.9.10-21.el6_3.6.x86_64 (rhel6.3).
The VM's xml given by "virsh capabilities" now contains the cpu topology:
<topology sockets='1' cores='1' threads='1'/>
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.