Quantcast
Channel: VMware Communities : Popular Discussions - VMware Server 1
Viewing all articles
Browse latest Browse all 74849

CPU Usage 100%. vmware.log reporting the number of CPUs / CPU configuration inaccurately. Wrong threads per core / not seeing both processors. Help!

$
0
0

After rebuilding our VM Server (running 1.04) we are experiencing 100% CPU Load within our MS SBS 2003 VM (2 processors assigned). The host is a Supermicro P4DP8 with 2 Xeon 2.4GB processors with HT turned off 4GB RAM (2GB allocated to the VM). The CPU load in the web management interface is reporting 160% +.

 

We noticed a discrepancy in how the vmware.log file reports the CPUs after rebuilding. Old logs, prior to rebuild read:

 

 

 

-


Nov 12 13:38:10: vmx| CPU #0 TSC = 398269318202

 

Nov 12 13:38:10: vmx| CPU #1 TSC = 398269318202

 

Nov 12 13:38:10: vmx| TSC delta 0

 

 

Nov 12 13:38:10: vmx| VMMon_GetkHzEstimate: Calculated 2337700 kHz

 

 

Nov 12 13:38:10: vmx| cpuids[0].id81.ecx = 0x1

 

 

Nov 12 13:38:10: vmx| cpuids[1].id81.ecx = 0x1

 

 

Nov 12 13:38:10: vmx| pcpu #0 CPUID numEntries=10 GenuntelineI

 

 

Nov 12 13:38:10: vmx| pcpu #0 CPUID version=0x6fb id1.edx=0xbfebfbff id1.ecx=0xe3fd id1.ebx=0x20800

 

 

Nov 12 13:38:10: vmx| pcpu #0 CPUID id80.eax=80000008 id81.edx=0x20100000 id81.ecx=0x1

 

 

Nov 12 13:38:10: vmx| pcpu #1 CPUID numEntries=10 GenuntelineI

 

 

Nov 12 13:38:10: vmx| pcpu #1 CPUID version=0x6fb id1.edx=0xbfebfbff id1.ecx=0xe3fd id1.ebx=0x1020800

 

 

Nov 12 13:38:10: vmx| pcpu #1 CPUID id80.eax=80000008 id81.edx=0x20100000 id81.ecx=0x1

 

 

Nov 12 13:38:10: vmx| CPUID id1.edx: 0xbfebfbff id1.ecx: 0xe3fd id81.edx: 0x20100000 id81.ecx: 0x1

 

 

Nov 12 13:38:10: vmx| CPUID id88.ecx: 0 id88.edx: 0

 

 

Nov 12 13:38:10: vmx| ACL_InitCapabilities: here 1 (bug 63252)

 

 

Nov 12 13:38:10: vmx| changing directory to z:\virtual machines\io\iomain\.

 

 

Nov 12 13:38:10: vmx| Config file: z:\virtual machines\io\iomain\windows server 2003 small business.vmx

 

 

Nov 12 13:38:11: vmx| VMDB: Connected to serverd

 

 

Nov 12 13:38:11: vmx| IPCHandleConnection: ReadFile failed (code 109)

 

 

Nov 12 13:38:11: vmx| VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOn without reset

 

 

Nov 12 13:38:11: vmx| PowerOn

 

 

Nov 12 13:38:11: vmx| Host: WIN32 highest NUMA node 0

 

 

Nov 12 13:38:11: vmx| Host: WIN32 NUMA node 0, CPU mask 0x0000000000000003

 

 

Nov 12 13:38:11: vmx| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 1.

 

 

Nov 12 13:38:11: vmx| HOSTINFO: This machine has 2 physical CPUS, 2 total cores, and 2 logical CPUs.

 

 

 

 

-


The VM performed fine under this config. However, after rebuild this section of the log reads:

 

-


Nov 27 16:16:55: vmx| CPU #0 TSC = 484956781052

 

Nov 27 16:16:55: vmx| CPU #1 TSC = 484956781052

 

Nov 27 16:16:55: vmx| TSC delta 0

 

 

Nov 27 16:16:55: vmx| VMMon_GetkHzEstimate: Calculated 2399810 kHz

 

 

Nov 27 16:16:55: vmx| cpuids[0].id81.ecx = 0x0

 

 

Nov 27 16:16:55: vmx| cpuids[1].id81.ecx = 0x0

 

 

Nov 27 16:16:55: vmx| pcpu #0 CPUID numEntries=2 GenuntelineI

 

 

Nov 27 16:16:55: vmx| pcpu #0 CPUID version=0xf24 id1.edx=0x3febfbff id1.ecx=0x0 id1.ebx=0x2080b

 

 

Nov 27 16:16:55: vmx| pcpu #0 CPUID id80.eax=80000004 id81.edx=0x0 id81.ecx=0x0

 

 

Nov 27 16:16:55: vmx| pcpu #1 CPUID numEntries=2 GenuntelineI

 

 

Nov 27 16:16:55: vmx| pcpu #1 CPUID version=0xf24 id1.edx=0x3febfbff id1.ecx=0x0 id1.ebx=0x602080b

 

 

Nov 27 16:16:55: vmx| pcpu #1 CPUID id80.eax=80000004 id81.edx=0x0 id81.ecx=0x0

 

 

Nov 27 16:16:55: vmx| CPUID id1.edx: 0x3febfbff id1.ecx: 0 id81.edx: 0 id81.ecx: 0

 

 

Nov 27 16:16:55: vmx| CPUID id88.ecx: 0 id88.edx: 0x7b7040

 

 

Nov 27 16:16:55: vmx| ACL_InitCapabilities: here 1 (bug 63252)

 

 

Nov 27 16:16:55: vmx| changing directory to c:\virtual machines\iomain\.

 

 

Nov 27 16:16:55: vmx| Config file: c:\virtual machines\iomain\windows server 2003 small business.vmx

 

 

Nov 27 16:16:56: vmx| VMDB: Connected to serverd

 

 

Nov 27 16:16:56: vmx| IPCHandleConnection: ReadFile failed (code 109)

 

 

Nov 27 16:16:56: vmx| VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOn without reset

 

 

Nov 27 16:16:56: vmx| PowerOn

 

 

Nov 27 16:16:56: vmx| Host: WIN32 highest NUMA node 0

 

 

Nov 27 16:16:56: vmx| Host: WIN32 NUMA node 0, CPU mask 0x0000000000000003

 

 

Nov 27 16:16:56: vmx| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2.

 

 

Nov 27 16:16:56: vmx| HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 2 logical CPUs.

 

 

 

 

-


The host info section caught our eye-instead of seeing 2 processors with 1 thread per core VM Server is now reporting one CPU with 2 threads. This is not correct, and we feel it may be related to our problem. What's baffling is it is the same hardware config. and an identical (so we think) build before and after!

 

 

 

 

 

If we temporarily turn on HT in the BIOS this section of the log reports "This machine has 2 physical CPUS, 2 total cores, and 4 logical CPUs."

 

 

We've also tried HT on while specifying the CPUs to use and not use in the VMX. Still the VM's performance was awful.

 

 

We rolled back to 1.03 and even tried 2 beta with the same result and same reporting of the CPU config.

 

 

 

 

 

 

 

 

The host is 32-bit Win XP SP2.

 

 

Any recommendations would be greatly appreciated as we are stumped.,

 

 

Thanks in advance for you time,

 

 

Dan Broderick


Viewing all articles
Browse latest Browse all 74849

Trending Articles