VMWare ESX server Illegal Opcode

I have a vmware ESX server that stopped responding this morning.  When we rebooted it, it still did not respond to the virtual center server or to pings.  I ILOed into the remote console and see a red screen with Illegal OpCode at the top and a bunch of hex codes.  Does anyone have any idea how to resolve this?  (I can reinstall ESX if that's the only solution, but I have to do it over the wire as the server is 500 miles from me).

The hex codes are :
EAX=00000000     EBX=00007000     ECX=00646165     EDX=00000080
EBP=000004E3     ESI=00007C05     EDI=0000FBF1    
DS=0000      ES=0800       FS=0000     GS=0003
CS:EIP=0000:0000836C        SS:ESP=0000:00001FFE
EFLAGS=00000246
ericb76Asked:
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.

bleeuwenCommented:
You should contact HP or VMWare with this problem. Probably a hard- or software error
0

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
vmwarun - ArunCommented:
Check bleeuwen's Second link since one of the posters has said that he has fixed the issue by regenerating MBR

Hey, hope this helps because I just had to register to post this :PI had the same thing occur tonight... which freaked me out a bit.I managed to fix the problem though (this was on a HP Proliant DL385G2).It seems like it arises from the server trying to boot from its HDD -and when it looks to the address where the bootable code should be (i.e.grub/initrd whatevr). And it gets something which isn't bootable - so itreplies 'illegal opcode' and hangs.So I booted into Ubuntu using a 7.04 live CD (taking note to use a64bit one), and from there I used grub to regenerate an appropriateMBR.grub> device (hd0) /dev/cciss/c0d0grub> root(hd0)grub> setup ( hd0,0)Once that was done the server stopped ecountering the 'illegal opcodes'which were the result of it looking at the corrupted MBR/whatever, andseeing something other than a properly configured bootable image.So then instead of getting a red-screen of death, I got the grub menu.Sorry I wrote this the other night and then fell asleep at my deskbefore hitting send.
0
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
VMware

From novice to tech pro — start learning today.