DSAN-DX Mobo
2x Intel Xeon L5420 (Quad Core)
I "successfully" installed ESX 3.5 U3, but I get a cryptic message (in red) on the main ESX screen:
TSC: 23215500 cpu0:0) SMP:437: Invalid HT Config (numHT4, numPCPUS 😎
Seems like a license issue, but I obtained a 16 processor license from VMWARE sales, and still it says 2 CPUs, 1 core per CPU, hyperthreading disabled (which it should be). The rep also mentioned that the cores (or hyperthreading) doesn't matter, the support is per CPU socket. But he also stated that U3 only supports 6 cores....assuming total, rather than per CPU.
Seems that the SMP component of the Linux Kernel didn't install or something. Has anyone ever seen this error??
Thanks.
Someone probably has a fix. By the time you get that response, you can just as easily reinstall. That's what I would do just start over, and make sure VT extensions are enabled in the bios.
Seems that the SMP component of the Linux Kernel didn't install or something. Has anyone ever seen this error??
BTW ESX is NOT any way shape or form Linux. It use a grub and a service console that resembles Linux, but the kernel is NOT Linux.
VT is enabled in BIOS, required to install 64-bit XP VM. I tried disabling it and the 64-bit VMs would not start anymore.
I have installed ESX 3 times now.
I disabled hyperthreading in the properties and got the red message to go away, but I still have only 1 processor core per socket.
Thanks.
That's odd.. BIOS firmware up to date?
I got way more errors before I updated the BIOS. It wouldn't even boot up with the old BIOS (unmountable boot volume or something).
It is odd. It just sits...waiting to be fixed.
Updated to BIOS version 0402, even though it didn't have anything useful.
Then performed upgrade install....NO HELP.
I FINALLY figured it out by searching the Internet, and ironically finding some vmware links, using google.
The problem at hand:
MAX CPUID was set to <Enabled> in the BIOS.
MAX CPUID is meant to be set to enabled so that older operating systems do not see extra information when polling the CPU (that's paraphrased).
When I set to it to enabled it lost its extra cores.
But why did I set it to that you might ask? Because it gave me some other cryptic crash if it was disabled. That information was:
AP 4 prevented from starting
could not start pcpu 4
SO, I changed MAX CPUID back to <disabled> and then FIXED my original problem.
I found the solution to my original problem via this thread:
and this one:
http://communities.vmware.com/thread/181995
Basically, my CPU's had different stepping (same model) and/or insufficient thermal paste (I found both to be the situation).
CPU 1 (L5420 2.50GHz)
Core Stepping: C0
CPUID String: 10676h
SLARP
CPU 2 (L5420 2.50GHz)
Core Stepping: E0
CPUID String: 1067Ah
SLBBR
I found this information by burning an iso image of a utility at this link:
and verifying by checking my stepping codes at this link:
I switched (and repasted) CPU1 and CPU2 to OPPOSITE the configuration listed above.
Problem solved!!
Original readout:
Processor Sockets 2
Processor Cores per Socket: 1
Logical Processors 2
Final readout:
Processor Sockets 2
Processor Cores per Socket: 4
Logical Processors 8
I have the same problem. You've solved it. But how? I have E5420 cpu and 12Mb
dseb-dg Asus motherboard.
Should I set the bios or something in the vmware. and if so where really.
Max CPU = disabled, but otherwise I do not know.
can you help me?
vmboot utility show this.
Family: 06 Model 17 stepping: a
ID1ECX ID1EDX ID81ECX ID8EDX
SSE SUPPORT: SSE1 --> SSE4.1
SUPPORT NX /XD YES
SUPPORT CMPXCHG16B YES
SUPPORT RDTSCP NO
HYPERTHREADING YES
SUPPORT FLES MIGRATION YES
SUPPORT 64BIT LONGMODE YES
SUPPORT 64BIT VMWARE YES
SUPPORTED EVC MODES XEON CORE2 XEON 45NM CORE2
but according to intel, I have no HYPERTHREADING
Necropost alert....
I just picked up a Dell CS24-SC server and ran into this issue after installing ESXi 5.5. The server has two Xeon quad-core L5420's but ESXi was only seeing two single-core cpu's. Once I went into the server's BIOS and disabled MAX CPUID it now sees everything correctly.
This is a generic BIOS screenshot showing what the value typically looks like: