VMware ESXi crashing after running for a min or so.

Hello and thank you. Your time and expertise is always much appreciated.

I have an HP ProLiant 150 G6
Intel Xeon E5504 2.0 GHz
16gb RAM, Raid 5

I'm running ESXi 4.1 Kernel 348481

I downloaded and Installed
HP ESXi Installable CD for ESXi 4.1 Update 1
Image for ESXi 4.1 Update 1 installation that includes HP Insight Manager providers, documentation for installation, and drivers required for use with HP ProLiant servers.

The install went very smooth, no issues. Got the server booted but about 1 min to 1.5 mins into running it crashes.

I would really appreciate some input and help with solving this problem. Getting the server this far has been a chalange. I felt victorius when VM booted. However, my victory was short lived. Very frustrating.

I did do some trouble shooting but nothing worked thus far.
Below are my findings:

This is my first HP VMware install. I've done a few on Dell T610 & R610.
My first instinct was to check the CPU settings in the bios to ensure that virtualization is enabled.

In Advanced CPU settings I did find that:
Intel (R) Virtualization Tech was disabled. I enabled it.
Intel (R) Vt-d (Virtualization Tech for direct I/O) was enabled.
Having the Virtualization Tech enabled or disabled does not seem to make a difference.

When VM crashes. It comes up with a PINK screen.
Below is an image of that screen
 #pf exception 14 esxi crash screen
It did give me an option to view the vmkernel log.
Below are images of the log. (a few pages form the end of the log as well as pages that contain erros or at least what i think are errors)
 vmkernel log vmkernel log vmkernel log vmkernel log vmkernel log vmkernel log vmkernel log vmkernel log vmkernel log
Please any input as to why the server crashes would be much appreciated.
I have nothing to go on at this point.
I figured I try EX before googeling the issue and goign on a wild goose chase.

Many Thanks In Advance..

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Danny McDanielClinical Systems AnalystCommented:
ML150 G6 isn't supported for ESXi 4.x according to the VMware support matrix  http://www.vmware.com/resources/compatibility/search.php
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Although your server has not been tested and certified for use with ESXi 4.1 U1. This server does work with ESXi 4.1 U1 and ESXi 5.0.

Do not use the HP Version with the Embedded Agents, it will cause the ESXi server to crash, shortly after startup. The OEM HP version of VMware ESXi 4.1 causes all 100, 300 series and Microserver to crash shortly after startup due to the Agents!

Download the VMware Version from VMware without the Agents. (OEM CIM Providers), and you'll be fine.

The free download is available from here

Just register.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
loshdogAuthor Commented:
Hello Hanccocka

You have saved me hrs. of trouble shooting once again.

I don't know why I would ever think to use HP software on HP hardware and expect it to work. :)

Thank you very much...
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Thanks for your kinds words, you are not the first and certainly not the last VMware Administrator/Engineer, that experiences this issue. It's odd, that you think the VMware ESXi 4.1 U1 installation is working on your server, turn your back, and it's PSODed! (as the agents kick in!).

One of our Engineers had this issue last week, because the installation media had got mixed up, and he didn't know which version he had installed, that was causing this issue!

HP Agents can cause lots of issues, especially if not compatible with the hardware!

So Glad you've got it solved! All the Best...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.