Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Interpreting virtual machine monitor and executable failures (1019471)

Last Updated: 3/9/2015Categories: TroubleshootingTotal Views: 44469Language:
Chinese (Simplified)Portuguese (European)SpanishEnglish

8 like this article

Subscribe to get an email
newsletter with new updates

8 people found this helpful Please provide article feedback:

Purpose

This article provides a high level overview of the components of a virtual machine and provides information about the errors that can be reported by the components.

Resolution

What is a virtual machine?

A virtual machine is a tightly isolated software container that can run its own operating systems and applications as if it were a physical computer. A virtual machine behaves exactly like a physical computer and contains it own virtual (that is, software-based) CPU, RAM hard disk and network interface card (NIC).

What are the components of a virtual machine?

A virtual machine is composed of several processes or userworlds that run in the VMkernel. Combined, the processes collectively make up a group. The following is a summary of components of a virtual machine:

Virtual Machine Executable (VMX) process - A process that runs in the VMkernel that is responsible for handling I/O to devices that are not critical to performance. The VMX is also responsible for communicating with user interfaces, snapshot managers, and remote console.

Virtual Machine Monitor (VMM) process - A process that runs in the VMkernel that is responsible for virtualizing the guest OS instructions, and manages memory. The VMM passes storage and network I/O requests to the VMkernel, and passes all other requests to the VMX process. There is a VMM for each virtual CPU assigned to a virtual machine.

Mouse Keyboard Screen (MKS) process - A process that is responsible for rendering the guest video and handling guest operating system user input.

Interpreting a VMM Process Error

If the VMM process experiences an error, the backtrace of the process is documented in the /var/log/messages in ESX/ESXi 4.x and earlier . For ESXi 5.x and above it is located at /var/log/vmkernel.log
The backtrace information looks similar to:

Nov 19 17:49:14 esx01 vmkernel: 3:01:10:57.942 cpu4:1256)WARNING: World: vm 1256: 6012: vmm1:ExchSRV01:vcpu-1:VMM64 fault 6: src=MONITOR rip=0xfffffffffc07696a regs=0xfffffffffc008ac0
Nov 19 17:49:14 esx01 vmkernel: 3:01:10:57.942 cpu4:1256)World: 6015: vmm group leader = 1255, members = 2
Nov 19 17:49:14 esx01 vmkernel: 3:01:10:57.942 cpu4:1256)Backtrace for current CPU #4, worldID=1256, ebp=0x37a3f7c
Nov 19 17:49:14 esx01 vmkernel: 3:01:10:57.942 cpu4:1256)0x37a3f7c:[0x63c1cb]World_VMMPanic+0xa7(0xdae840, 0x0, 0x0, 0x0, 0x0)
Nov 19 17:49:14 esx01 vmkernel: 3:01:10:57.943 cpu4:1256)0x37a3fa4:[0x63c1cb]World_VMMPanic+0xa7(0x29, 0x3eb72fd4, 0x7b00412f, 0x3eb1854c, 0x4020)
Nov 19 17:49:14 esx01 vmkernel: 3:01:10:57.943 cpu4:1256)0x37a3fdc:[0x61de1a]VMKCall+0x8a(0x29, 0x3eb72fd4, 0x82, 0x3eb667e0, 0x3eb1854c)

The following is an explanation of each section of the backtrace:

vm 1256: 6012:
This section of the event describes the virtual machine ID and the userworld ID that experienced the error. In this example, the userworld ID of the process that experienced the error is 6012, and the virtual machine ID is 1256.

vmm1:virtulam:vcpu-1:
This section of the event describes the virtual CPU and the virtual machine name that experienced the error. In this example, the error occurred on virtual CPU 1, and the virtual machine name started with the text ExchSRV01 (the name may be truncated).

VMM64 fault 6: src=MONITOR rip=0xfffffffffc07696a
This section of the event describes the actual error experienced by the process. In this example, the VMM process experienced a VMM64 fault 6. These error messages are very specific and can be searched for in the knowledge base.

World: 6015: vmm group leader = 1255, members = 2
This section of the event describes the group of processes that make up the virtual machine.

Backtrace for current CPU #4, worldID=1256, ebp=0x37a3f7c
This section of the event describes the physical CPU that was running the instruction at the time of the error. If multiple virtual machines are experiencing similar errors, this section of the error message can potentially identify faulty hardware. For more information, see Determining if virtual machine and ESX host unresponsiveness is caused by hardware issues (1003560).

0x37a3f7c:[0x63c1cb]World_VMMPanic+0xa7(0xdae840, 0x0, 0x0, 0x0, 0x0)
This section of the event describes the functions that are called when the process experiences the error. Lines similar to the above repeat for each function that is called leading up to the error.

If your virtual machine experiences an error similar to the above, search for the error message within the knowledge base. If the error has not been documented in the knowledge base, submit a Support Request. For more information, see Filing a Support Request in Customer Connect (2006985).

Interpreting a Virtual Machine Executable (VMX) Process Error

If the VMX process experiences an error, the backtrace of the process is documented in the virtual machine log file. The backtrace information looks similar to:

Jul 02 17:57:48.800: vmx| Msg_Post: Error
Jul 02 17:57:48.800: vmx| [msg.disk.invalidClusterDisk] VMware ESX cannot open the virtual disk, "/vmfs/volumes/483df5c2-c1afaa7a-e5e2-001d0967f2a4/thickFTVM4/thickFTVM4.vmdk" for clustering. Please verify that the virtual disk was created using the 'thick' option.
Jul 02 17:57:48.800: vmx| [msg.disk.noBackEnd] Cannot open the disk '/vmfs/volumes/483df5c2-c1afaa7a-e5e2-001d0967f2a4/thickFTVM4/thickFTVM4.vmdk' or one of the snapshot disks it depends on.
Jul 02 17:57:48.801: vmx| [msg.disk.configureDiskError] Reason: @&!*@*@(msg.disklib.INVALIDMULTIWRITER)Thin/TBZ disks cannot be opened in multiwriter mode..----------------------------------------
Jul 02 17:57:48.807: vmx| Checkpoint error 0, couldn't continue after checkpoint
Jul 02 17:57:52.414: vmx| Backtrace:
Jul 02 17:57:52.414: vmx| Backtrace[0] 0xffeeaec8 eip 0xc1abca0

When you have identified this information, search the Knowledge Base for the main error to locate articles that pertain to your exact issue. If the error has not been documented within the knowledge base, collect diagnostic information from the VMware ESX host and submit a Support Request. For more information, see Collecting Diagnostic Information for VMware Products (1008524) and Filing a Support Request in Customer Connect (2006985).

Interpreting a Monitor Keyboard Mouse (MKS) Process Error

If the MKS process experiences an error, the backtrace of the process is documented in the virtual machine log file. The backtrace information looks similar to:

Sep 28 11:15:02.928: mks| Msg_Post: Error
Sep 28 11:15:02.928: mks| [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (mks)
Sep 28 11:15:02.928: mks| ASSERT bora/devices/svga/svgaFifo.c:1176 bugNr=6985 Sep 28 11:15:02.928: mks| [msg.panic.haveLog] A log file is available in "vmware.log". [msg.panic.haveCore] A core file is available in "/vmfs/volumes/4a01a03d-c105cb4
5-b3c0-002219543490/Win2K8_64/vmware-vmx-debug-zdump.012". [msg.panic.requestSupport.withLogAndCore] Please request support and include the contents of the log file an
d core file. [msg.panic.requestSupport.vmSupport.vmx86]
Sep 28 11:15:02.930: mks| To collect data to submit to VMware support, run "vm-support".
Sep 28 11:15:02.930: mks| [msg.panic.response] We will respond on the basis of your support entitlement.
Sep 28 11:15:02.930: mks| ----------------------------------------
Sep 28 11:15:02.935: mks| MKS release: start, nesting 0
Sep 28 11:15:03.016: vmx| VTHREAD watched thread 1 "mks" died
Sep 28 11:15:03.423: vcpu-0| VTHREAD watched thread 0 "vmx" died

When you have identified this information, search the Knowledge Base for the main error to locate articles that pertain to your exact issue. If the error has not been documented within the knowledge base, collect diagnostic information from the VMware ESX host and submit a Support Request. For more information, see Collecting diagnostic information for VMware products (1008524) and Filing a Support Request in Customer Connect (2006985).

Related Information

For related information, see Determining why a virtual machine was powered off or restarted (1019064).Determining if virtual machine and ESX host unresponsiveness is caused by hardware issues
Collecting diagnostic information for VMware products
Determining why a virtual machine was powered off or restarted
How to file a Support Request in Customer Connect
Interpretando o monitor da máquina virtual e as falhas executáveis
Interpretar fallas ejecutables y de monitoreo de máquina virtual

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)SpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Support Assistant