Capacity Planner reports wrong CPU info for Fedora system

[neil_murphy]

Hi,

I'm doing a Capacity Planner exercise for a client who has two IBM x3650 servers running Fedora Core. These both have 2 Intel dual core Xeon 5160 processors. Capacity Planner reports the CPU count as 3 however. Surely this should be 4 (2 x 2 cores). Capacity Planner gets its information about CPUs from the /proc/cpuinfo file. I have inspected this file which (I think) correctly lists 4 cores. I have included the output below.

Has anyone any ideas?

Neil.

processor : 0

vendor_id : GenuineIntel

cpu family : 6

model : 15

model name : Intel(R) Xeon(R) CPU 5160 @ 3.00GHz

stepping : 6

cpu MHz : 2997.000

cache size : 4096 KB

physical id : 0

siblings : 2

core id : 0

cpu cores : 2

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca lahf_lm

bogomips : 5988.29

clflush size : 64

processor : 1

vendor_id : GenuineIntel

cpu family : 6

model : 15

model name : Intel(R) Xeon(R) CPU 5160 @ 3.00GHz

stepping : 6

cpu MHz : 1998.000

cache size : 4096 KB

physical id : 0

siblings : 2

core id : 1

cpu cores : 2

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca lahf_lm

bogomips : 5984.98

clflush size : 64

processor : 2

vendor_id : GenuineIntel

cpu family : 6

model : 15

model name : Intel(R) Xeon(R) CPU 5160 @ 3.00GHz

stepping : 6

cpu MHz : 1998.000

cache size : 4096 KB

physical id : 3

siblings : 2

core id : 0

cpu cores : 2

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca lahf_lm

bogomips : 5985.03

clflush size : 64

processor : 3

vendor_id : GenuineIntel

cpu family : 6

model : 15

model name : Intel(R) Xeon(R) CPU 5160 @ 3.00GHz

stepping : 6

cpu MHz : 1998.000

cache size : 4096 KB

physical id : 3

siblings : 2

core id : 1

cpu cores : 2

fdiv_bug : no

hlt_bug : no

f00f_bug : no

coma_bug : no

fpu : yes

fpu_exception : yes

cpuid level : 10

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca lahf_lm

bogomips : 5985.03

clflush size : 64

[Texiwill · Accepted solution]

Hello,

There are 4 cores.... Core 0 - 4, I think capacity planner may have an issue with 0 based counts. I would bring this up with the Capacity planner folks.

Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

[djsCA]

I think it's more likely that it's because of this returning only 3 cpus. It could be using the same information that appears during boot:

$ dmesg |grep -i xeon
Intel(R) Xeon(R) CPU 5160 @ 3.00GHz stepping 06
Intel(R) Xeon(R) CPU 5160 @ 3.00GHz stepping 06
Intel(R) Xeon(R) CPU 5160 @ 3.00GHz stepping 06

/djsCA