Todd And Margo Chester
2011-Dec-03 01:53 UTC
[libvirt-users] Can I configure cores instead of CPU's
> -------- Original message -------- > Subject: Re: [libvirt-users] Can I configure cores instead of CPU's > From: Todd And Margo Chester <toddandmargo at gmail.com> > To: "libvirt-users at redhat.com" <libvirt-users at redhat.com> > CC: > > > Hi All, > > Scientific Linux 6.1 x64 > qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64 > > My XP-Pro guest will only let me use two CPUs. > Is there a way I can tell Virt-Manager to use > one CPU with six cores instead of four separate > CPUs? > > I can manually insert things with > virsh edit KVM-WinXP > > Currently, I have: > <vcpu>6</vcpu> > > I found an example of a run string: > > -smp 2,sockets=2,cores=1,threads=1 > > But I will be darned if I can figure out the virsh xml syntax. > > Many thanks, > -TOn 12/02/2011 05:32 PM, Frank Hauptle wrote: > Yes under advanced in cpu in virt manager are socket /core > settings. i use a fedora virt manager to connect to sl61 > libvirt. more options that way. I configured my processor in virt-mamager: CPU's: Current Allocation: 2 Manual set CPU Topology: Sockets: 1 Cores: 6 Threads: 1 or from my XML file <vcpu>1</vcpu> <cpu> <topology sockets='1' cores='6' threads='1'/> </cpu> I still get two CPUs in my guest XP-Pro. What am I doing wrong? -T
Todd And Margo Chester
2011-Dec-04 05:49 UTC
[libvirt-users] Can I configure cores instead of CPU's
> On 3/12/2011 9:53 AM, Todd And Margo Chester wrote: >>> -------- Original message -------- >>> Subject: Re: [libvirt-users] Can I configure cores instead of CPU's >>> From: Todd And Margo Chester<toddandmargo at gmail.com> >>> To: "libvirt-users at redhat.com"<libvirt-users at redhat.com> >>> CC: >>> >>> >>> Hi All, >>> >>> Scientific Linux 6.1 x64 >>> qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64 >>> >>> My XP-Pro guest will only let me use two CPUs. >>> Is there a way I can tell Virt-Manager to use >>> one CPU with six cores instead of four separate >>> CPUs? >>> >>> I can manually insert things with >>> virsh edit KVM-WinXP >>> >>> Currently, I have: >>> <vcpu>6</vcpu> >>> >>> I found an example of a run string: >>> >>> -smp 2,sockets=2,cores=1,threads=1 >>> >>> But I will be darned if I can figure out the virsh xml syntax. >>> >>> Many thanks, >>> -T >> On 12/02/2011 05:32 PM, Frank Hauptle wrote: >> > Yes under advanced in cpu in virt manager are socket /core >> > settings. i use a fedora virt manager to connect to sl61 >> > libvirt. more options that way. >> >> >> I configured my processor in virt-mamager: >> >> CPU's: Current Allocation: 2 >> Manual set CPU Topology: >> Sockets: 1 >> Cores: 6 >> Threads: 1 >> >> or from my XML file >> >> <vcpu>1</vcpu> >> <cpu> >> <topology sockets='1' cores='6' threads='1'/> >> </cpu> >> >> I still get two CPUs in my guest XP-Pro. >> >> What am I doing wrong? >> >> -TOn 12/03/2011 07:40 PM, Frank Hauptle wrote:> I'm not even sure XP could differentiate > between a core and a socket as multicore CPU's were not common to x86 in > 2000 when XP was released. > > If you want to see if it really worked, download a knoppix CD and mount > the ISO in the CDrom of that > VM, then set it to boot from the CDROM. > > When knoppix boots up, open a terminal and type: > > cat /proc/cpuinfo > > See what it gives you. > > I think the hardware info GUI app in knoppix will give you more info too. > > cheers > > > FrankHi Frank, I have FC16 live CD as a guest. /proc/cpuinfo said I had four cpu's. Given a bit of time I can give you the full report if that would help. My host CPU is an i7-960 (four real cores, eight hyperthreaded cores.) -T
Todd And Margo Chester
2011-Dec-05 00:32 UTC
[libvirt-users] Can I configure cores instead of CPU's
> On 3/12/2011 9:53 AM, Todd And Margo Chester wrote: >>> -------- Original message -------- >>> Subject: Re: [libvirt-users] Can I configure cores instead of CPU's >>> From: Todd And Margo Chester<toddandmargo at gmail.com> >>> To: "libvirt-users at redhat.com"<libvirt-users at redhat.com> >>> CC: >>> >>> >>> Hi All, >>> >>> Scientific Linux 6.1 x64 >>> qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64 >>> >>> My XP-Pro guest will only let me use two CPUs. >>> Is there a way I can tell Virt-Manager to use >>> one CPU with six cores instead of four separate >>> CPUs? >>> >>> I can manually insert things with >>> virsh edit KVM-WinXP >>> >>> Currently, I have: >>> <vcpu>6</vcpu> >>> >>> I found an example of a run string: >>> >>> -smp 2,sockets=2,cores=1,threads=1 >>> >>> But I will be darned if I can figure out the virsh xml syntax. >>> >>> Many thanks, >>> -T >> On 12/02/2011 05:32 PM, Frank Hauptle wrote: >> > Yes under advanced in cpu in virt manager are socket /core >> > settings. i use a fedora virt manager to connect to sl61 >> > libvirt. more options that way. >> >> >> I configured my processor in virt-mamager: >> >> CPU's: Current Allocation: 2 >> Manual set CPU Topology: >> Sockets: 1 >> Cores: 6 >> Threads: 1 >> >> or from my XML file >> >> <vcpu>1</vcpu> >> <cpu> >> <topology sockets='1' cores='6' threads='1'/> >> </cpu> >> >> I still get two CPUs in my guest XP-Pro. >> >> What am I doing wrong? >> >> -TOn 12/03/2011 07:40 PM, Frank Hauptle wrote: >I'm not even sure XP could differentiate > between a core and a socket as multicore CPU's were not common to x86 in > 2000 when XP was released. > > If you want to see if it really worked, download a knoppix CD and mount > the ISO in the CDrom of that > VM, then set it to boot from the CDROM. > > When knoppix boots up, open a terminal and type: > > cat /proc/cpuinfo > > See what it gives you. > > I think the hardware info GUI app in knoppix will give you more info too. > > cheers > > > Frank Hi Frank, Don't have knoppix, but do have FC16-Live-CD. The rules for CPU count in XP-Pro are as follows: the physically chip that you install on your motherboard is referred to by M$ as a CPU. XP-Pro will only allow up to two CPUs. Each physical CPU may have as many processors on it as will fit. M$ calls these processors "cores". XP-Pro does not limit cores as long as they do not span more than two CPU's. My host machine has one CPU and four cores (eight if you consider the hyperthreading). KVM is presenting my XP-Pro guest multiple CPUs, not cores. XP will not use more than two CPUs by design. What I am after is a way to have KVM present my guest one CPU with four cores. Not four independent CPUs. I have attached /proc/cpuinfo from Fedora Core 16 guest, along with my /proc/cpuinfo from my host. What am I doing wrong? Many thanks, -T ---->> cat /proc/cpuinfo from FC16 Guest: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version (cpu64-rhel6) stepping : 3 cpu MHz : 3067.098 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl pni cx16 hypervisor lahf_lm bogomips : 6134.19 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version (cpu64-rhel6) stepping : 3 cpu MHz : 3067.098 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl pni cx16 hypervisor lahf_lm bogomips : 6134.19 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version (cpu64-rhel6) stepping : 3 cpu MHz : 3067.098 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl pni cx16 hypervisor lahf_lm bogomips : 6134.19 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version (cpu64-rhel6) stepping : 3 cpu MHz : 3067.098 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl pni cx16 hypervisor lahf_lm bogomips : 6134.19 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ---->> cat /proc/cpuinfo from Local Host (i7-960) processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6134.19 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6132.39 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 2 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6132.40 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6132.39 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 4 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6132.38 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 5 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 1 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6132.39 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 6 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 2 cpu cores : 4 apicid : 5 initial apicid : 5 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6132.39 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 cpu MHz : 1600.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 6132.39 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: