On 01/06/2010 12:21 PM, Daniel P. Berrange wrote:
On Wed, Jan 06, 2010 at 11:54:16AM +0200, Avi Kivity wrote:
On 01/06/2010 11:44 AM, Daniel P. Berrange wrote:
This is all a very long way of saying that mgmt apps based on libvirt
won't care about model names exposed in /proc/cpuinfo so there's no
particular need to have a direct mapping from them to QEMU for libvirt's
needs.
There is still a need to query qemu, since it will filter out bits that
kvm.ko or the hardware don't support.
If there was a more verbose version of '-cpu ?' which also gave the CPUID
masks associated with each supported CPU model, that would be useful info
avoiding need for libvirt to hardcode the mapping to QEMU
Yes, that's what I'm thinking of. Along with enumerating all the other
qemu capabilities.
--
error compiling committee.c: too many arguments to function
