Kamble, Nitin A wrote:
Avi, There are some OSes like windows server which impose licensing restriction on number of cpus. These licensing restrictions are based on number of packages/sockets. And look into the cupid data to decide which cpus are thread siblings, core siblings and packages siblings. With current KVM/Qemu implementation it is hiding all this cupid information from the guests. So guest sees each cpu as a single package. And the license restrictions inside the OS is limiting no of cpus the guest can run. These cupid bits should be exposed to the guest so that the OS would see the thread or core sibling information correctly to utilize more cpus.Is anybody is working on this?
Not that I know of. Indeed finer control over cpuid is needed. We need to support at least three modes:
- default: expose some machine that is likely to be widely supported - host: expose as much of the host cpu as we can - managed: management application controls everything -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
