VMware Cloud Community
THAGDF
Contributor
Contributor

ESX 4 Internal monitor error *** vcpu-0:VMM

Hello @ all,

i have installed a ESX 4.0 Server on my physical ESX 3.5 U4 Server. The Setup and all other things are working fine. But if I try to start a VM on my virtual ESX 4 Server, then I get the following error event:

Message from test1: *** VMware

ESX internal monitor error *** vcpu-0:VMM

fault: regs=0x2e00, exc=14, eip=0xb4e42 Please

report this problem by selecting menu item

Help > VMware on the Web > Request Support,

or by going to the Web page

"http://www.vmware.com/info?id=8&logFile=/vm-

mfs/volumes/4a968343%2dac8088fa%2d5617%2d0050-

56980c49/VM/vmware%2elog&coreLocation=/vmfs/vo-

lumes/4a968343%2dac8088fa%2d5617%2d005056980c4-

9/VM/vmware%2dcore%5b0%2d1%5d%2egz". Please

provide us with the log file

(/vmfs/volumes/4a968343-ac8088fa-5617-005056980-

c49/VM/vmware.log) and the core file(s)

(/vmfs/volumes/4a968343-ac8088fa-5617-005056980-

c49/VM/vmware-core[0-1].gz,

/vmfs/volumes/4a968343-ac8088fa-5617-005056980c4-

9/VM/vmware-vmx-zdump.001). If the problem is

repeatable, please set 'Use Debug Monitor' to

'Yes' in the 'Misc' section of the Configure

Virtual Machine Web page. Then reproduce the

incident and file it according to the

instructions. To collect data to submit to VMware

support, run "vm-support". We will respond on

the basis of your support entitlement. We

appreciate your feedback, -- the VMware ESX

team.

info

31.08.2009 10:13:55

User

I tried different VM-System like Red Hat, Win2K3 etc. but always I get this error code and the virtual machine is powered off autmoatically.

Many thanks in advance!

Greetz

Sebastian

Reply
0 Kudos
5 Replies
admin
Immortal
Immortal

This is a bug in ESX 3.5. Please file an SR.

Reply
0 Kudos
THAGDF
Contributor
Contributor

Is there a possibility to fix the bug? What do you mean with "file an SR"? Sorry I didn't get that.

Thanks for your answer!

Reply
0 Kudos
THAGDF
Contributor
Contributor

Or maybe is there a work-around or something else? It would be a problem in my infrastructure to update the ESX-Version.

Reply
0 Kudos
admin
Immortal
Immortal

There is no workaround, short of upgrading to ESX 4.0. Although this is not a supported configuration, there is a possibility that the bug will be fixed if there are customer complaints. Without such complaints, the bug will probably not get fixed. An SR is a "service request."

Reply
0 Kudos
THAGDF
Contributor
Contributor

Ok thanks for your answers. Then I must think about an update.

Reply
0 Kudos