The first clue would be to look at the error message, but you only posted "0xbad.....". Would be nice to see the whole error.
sorry, did not think the status was terribly important and it had scrolled by before getting the entire message
here is the exact message
Warning: Mod: 2434: Initialization of vmkernel failed, Status 0xbad001e
btw: is there a way to pause the screen during boot to give time to look over the various and numerous messages for additional clues?
the server is actually an sc1420 and has two cpus installed.
i also tracked the status 0xbad001e to another thread which indicated adding /vmkernel/checkCPUIDLimit = "FALSE" in /etc/vmware/esx.conf
this did not change the problem
i went into the bios and disabled the second cpu, this did not change the problem either.
although it was prior to adding the second cpu the system did install using a scsi drive under 3.0.0 I suppose i need to go back to the scsi drive and ensure this platform still works, perhaps the use of the ide is a false avenue and the problem is really the cpus now.
The code 0xbad001e is an "Unsupported CPU" error message.
i can believe this but is there something to be done to get around this check.
it was working for sure on 3.0.0, perhaps 3.0.1 is doing something more, or might it be the addition of the second cpu that has mucked it up.
The second CPU has to be identical to CPU 1. Same make, model, stepping, etc. While you can have slight differences in CPUs between hosts (Vmotion can acoount for this), when within the same host they must be identical. Because ESX3 job scheduling is more dynamic than on ESX2, VM processes/threads can be migrated between CPUs for better performance and load balancing. So a job spawned on CPU1 with (A) parameters is migrated to CPU2 with (B) parameters, the process can fail.
Thats why VMware put the CPU check in. Imagine being a VMware support tech trying to figure out why a ESX has sporadic failures, when in fact its because you are using two similar (but not the same) CPUs. He would go crazy trying to figure that one out.