Quantcast
Channel: Ocsinventory Q&A - Recent questions and answers in OCS Inventory NG agent
Viewing all articles
Browse latest Browse all 4573

Incorrectly detected CPUs in CentOS (6 & 7) under VMware

$
0
0

Hi

I've succesfully installed ocs unix-agent on some CentOS 6 and 7 using epel and remi repository.

# rpm -qa|grep ocsinventory-agent
ocsinventory-agent-2.1.1-1.el6.remi.x86_64

and

# rpm -qa|grep ocs
ocsinventory-agent-2.1.1-1.el7.remi.x86_64

Some of the systems are physical, under VMware ESX and under Xen full virtualization. Everything's fine in physical and Xen servers. But something is amiss on systems under VMware. It shows more CPUs than actually installed.

For example this is the output from /proc/cpuinfo: (4 CPUs detected)

# cat /proc/cpuinfo|grep model\ name
model name      : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
model name      : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
model name      : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
model name      : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz

But when I ran ocsinventory-agent, this is what I get from the .ocs file: (5 CPUs?)

<CPUS>
      <CORES>4</CORES>
      <CPUARCH>x86_64</CPUARCH>
      <CPUSTATUS>Enabled</CPUSTATUS>
      <CURRENT_SPEED>2933</CURRENT_SPEED>
      <DATA_WIDTH>64</DATA_WIDTH>
      <HPT>on</HPT>
      <L2CACHESIZE>12288</L2CACHESIZE>
      <MANUFACTURER>Intel</MANUFACTURER>
      <SOCKET>ZIF Socket</SOCKET>
      <SPEED>2933</SPEED>
      <TYPE>Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz</TYPE>
      <VOLTAGE>3.3 </VOLTAGE>
    </CPUS>
    <CPUS>
      <CORES>4</CORES>
      <CPUARCH>x86_64</CPUARCH>
      <CPUSTATUS>Enabled</CPUSTATUS>
      <CURRENT_SPEED>2933</CURRENT_SPEED>
      <DATA_WIDTH>64</DATA_WIDTH>
      <HPT>on</HPT>
      <L2CACHESIZE>12288</L2CACHESIZE>
      <MANUFACTURER>Intel</MANUFACTURER>
      <SOCKET>ZIF Socket</SOCKET>
      <SPEED>2933</SPEED>
      <TYPE>Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz</TYPE>
      <VOLTAGE>3.3 </VOLTAGE>
    </CPUS>
    <CPUS>
      <CORES>4</CORES>
      <CPUARCH>x86_64</CPUARCH>
      <CPUSTATUS>Enabled</CPUSTATUS>
      <CURRENT_SPEED>2933</CURRENT_SPEED>
      <DATA_WIDTH>64</DATA_WIDTH>
      <HPT>on</HPT>
      <L2CACHESIZE>12288</L2CACHESIZE>
      <MANUFACTURER>Intel</MANUFACTURER>
      <SOCKET>ZIF Socket</SOCKET>
      <SPEED>2933</SPEED>
      <TYPE>Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz</TYPE>
      <VOLTAGE>3.3 </VOLTAGE></CPUS>
    <CPUS>
      <CORES>4</CORES>
      <CPUARCH>x86_64</CPUARCH>
      <CPUSTATUS>Enabled</CPUSTATUS>
      <CURRENT_SPEED>2933</CURRENT_SPEED>
      <DATA_WIDTH>64</DATA_WIDTH>
      <HPT>on</HPT>
      <L2CACHESIZE>12288</L2CACHESIZE>
      <MANUFACTURER>Intel</MANUFACTURER>
      <SOCKET>ZIF Socket</SOCKET>
      <SPEED>2933</SPEED>
      <TYPE>Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz</TYPE>
      <VOLTAGE>3.3 </VOLTAGE>
    </CPUS>
    <CPUS>
      <CORES>4</CORES>
      <CPUARCH>x86_64</CPUARCH>
      <CPUSTATUS>Enabled</CPUSTATUS>
      <CURRENT_SPEED>2933</CURRENT_SPEED>
      <DATA_WIDTH>64</DATA_WIDTH>
      <HPT>on</HPT>
      <L2CACHESIZE>12288</L2CACHESIZE>
      <MANUFACTURER>Intel</MANUFACTURER>
      <SOCKET>ZIF Socket</SOCKET>
      <SPEED>2933</SPEED>
      <TYPE>Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz</TYPE>
      <VOLTAGE>3.3 </VOLTAGE>
    </CPUS>

And is also shown as 5 CPUs in the OCS-ng Web:

5 Result(s)(Download)

ManufacturerTypeSerial numberFrequencyCores numberL2 cache sizeArchitectureData widthCurrent address widthLogical CPUSVoltageCurrent speedSocket type
IntelIntel(R) Xeon(R) CPU X5670 @ 2.93GHz2933412288x86_6464003.32933ZIF Socket
IntelIntel(R) Xeon(R) CPU X5670 @ 2.93GHz2933412288x86_6464003.32933ZIF Socket
IntelIntel(R) Xeon(R) CPU X5670 @ 2.93GHz2933412288x86_6464003.32933ZIF Socket
IntelIntel(R) Xeon(R) CPU X5670 @ 2.93GHz2933412288x86_6464003.32933ZIF Socket
IntelIntel(R) Xeon(R) CPU X5670 @ 2.93GHz2933412288x86_6464003.32933ZIF Socket

All those doesn't happened on physical and Xen VMs, only on VMWare.

Is this known bug? Is there any update or workaround that I can apply?

Thank you.


Viewing all articles
Browse latest Browse all 4573

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>