VMware Cloud Community
vbuser
Contributor
Contributor

ESXi 5.5 installation error "SMP: 1690: Could not start pcpu"

Hi,

I tried to install ESXi 5.5 on a desktop computer from CD. Install throws error screen (error screen.jpg) with message: "SMP: 1690: Could not start pcpu", when it reaches timing scheduler. How can I resolve my installation issue?

Desktop PC technical data:

CPU: Intel Core i7-2600 CPU @ 3.40Hz, Virtualization and Hyperthreading, supported and enabled. (More detailed information: cpu_info.jpg)

Motherboard: MSI P67A-GD65 2.0 with BIOS V1.19 (latest update, 7.03.2012)

Storage: Samsung 256GB SSD 840 PRO series

0 Kudos
13 Replies
SatyS
Hot Shot
Hot Shot

Have a look @VMware KB: ESX Server fails to boot after a clean install due to different CPU steppings

Hope this helps!

-SatyS

If you find this useful,please mark the answer as correct/helpful

Regards,
SatyS
http://myvirtuallearning.wordpress.com/

vbuser
Contributor
Contributor

1. I donwloaded and burned this cpuid.iso to CD (Shared Utilities | United States).

2. I booted the desktop PC with created CD.

3. It shows a screen about calculating CPU frequency... for a while and then it fails with message "Parity Error". Standard and verbose CPUID tool produce the same thing.

Does this indicate some other issues why the original ESXi 5.5 install error "Could not start pcpu" occured?

Maybe some of my BIOS settings are not correct?

0 Kudos
SatyS
Hot Shot
Hot Shot

so,you are not able to get the cpu stepping?

If you find this useful,please mark the answer as correct/helpful

Regards,
SatyS
http://myvirtuallearning.wordpress.com/

0 Kudos
vbuser
Contributor
Contributor

Yes I cant get it. Well it shows a screen before the final "Parity Error", but it flashes so fast I can't see what data it is showing.

Maybe there is some other way?

0 Kudos
vbuser
Contributor
Contributor

More information regarding the initial ESXi 5.5 problem:

After i enable "Limit CPUID Maximum" from the BIOS, installation gave error "Cant detect the last level cache" (error screen 2.jpg).

error screen 2.jpg

0 Kudos
vbuser
Contributor
Contributor

Model and stepping info is shown here?

cpu_info.png

0 Kudos
SatyS
Hot Shot
Hot Shot

Hey,

I see that your setup has "Max CPUID Value Limit " to Enable.

Try disabling above option which will help you to install vmware esxi if it is not specific for your setup.

Hope this helps

-SatyS

If you find this useful,please mark the answer as correct/helpful

Regards,
SatyS
http://myvirtuallearning.wordpress.com/

0 Kudos
vbuser
Contributor
Contributor

I have tried it both ways if i enable it gives error "Cant detect the last level cache":

error screen 2.png

If it is disabled it gives the "Could not start pcpu" error:


error screen.jpg

0 Kudos
flash600
Contributor
Contributor

Hi vbuser,

I've the same problem: esxi 5.5 u1 (last version), hp proliant dl380p gen8 with actual firmwares and bios.

have you found a solution?



0 Kudos
vbuser
Contributor
Contributor

Hi flash,

No I have not found the solution to my problem. I have talked to some people and they said that MSI motherboard is not supported by VMware. Some say that it has to be Intel in order to install ESXi on PC. So I think my problem is based on the fact that my hardware is just not compatible with ESXi. 

0 Kudos
flash600
Contributor
Contributor

hmmm, strange issue...

I've two dl380p gen8, thats is supported by vmware;

I've installed the os with the HP custiomized iso, latest drivers and firmware, and with bios-settings: powerconfig:  "max performance" and "Collaborative Power Control" disabled (HP Advisory: http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/topIssuesDisplay/?javax.portlet....), but the problem exists.

the only goog thing is, that with this settings, the servers after 2-3 resets boots.

0 Kudos
Sequenzial
Contributor
Contributor

Hi all,

I have the same Problem on a Dell Presicion T3500 Workstation...

Die someone find a solution yet?

BR

Seq

0 Kudos
Alistar
Expert
Expert

Hi,

the problem seems to be likely in Time Stamp Counter Synchronization - did you have High Precision Event Timer enabled in BIOS? A little bit more info here: http://support.bull.com/ols/product/platforms/ns/ns-bullion/doc/tdocf/g/PSOD-timedrift

Stop by my blog if you'd like 🙂 I dabble in vSphere troubleshooting, PowerCLI scripting and NetApp storage - and I share my journeys at http://vmxp.wordpress.com/
0 Kudos