On 7/23/2014 6:22 PM, Sai Prajeeth wrote:
Try setting sockets=6,cores=1? I had this issue when running Solaris as guest. For some reason Solaris never detected any of the cores. It could only detect the sockets.
Unlikely to work. Windows 7 (unlike the more expensive server licenses for the same kernel) enforces a license restriction of max 2 physical CPUs, each with unlimited cores (subject to the kernel design maximum of at least 32). But try looking at the command line of the running qemu process. Does it actually specify 2 sockets with 4 cores each, or were the settings somehow mistranslated from libvirt XML to qemu command line? Also, if you are using a computer with more than 2 physical sockets, you may want to check if kvm passes through the physical or the command line CPU topology to the guest.
On Wed, Jul 23, 2014 at 9:38 PM, Scott Zhang <macromars...@gmail.com <mailto:macromars...@gmail.com>> wrote: __ __ Dear all: I have been trying this for whole afternoon and whole night. I have installed windows 7 as guest in kvm using virt-manager which use qemu. And after I alloc it 6 vcpus, I noticed win7 only see 2 cpus in task manager. But in device manager, it shows 6 cpus. After google a lot, looks many people say they workaround this by setting the topology of CPU, which is technical correct. But when I try to set sockets=2,cores=4 and several vairable pairs. None is working. Win7 only see 2 at most. I am using fedora 20 with kernel 3.15 and the default qemu. Can any one help? Thanks Regards 2014-07-24 ------------------------------------------------------------------------ Scott Zhang __
Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded