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

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Mapping a virtual machine world number to a virtual machine name (1001101)

Last Updated: 10/4/2016Categories: How toTotal Views: 1Language:
JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

Log entries from the VMkernel often refer to virtual machines by their world number, rather than by their name. For example, a world number often prefixes a log message, identifying the component or virtual machine which caused the logging to occur. The log message would have this format:

cpu<N>: <world number>) <Severity>: <Component>: <Log message>

It is often useful to determine which virtual machine is associated with a particular world or cartel number. Cartels are groups of coexisting worlds, such as those comprising a single virtual machine. A world is similar to a process, but running under the VMkernel.

For more information about the location of the VMkernel logs for your specific version of ESX/ESXi, see Location of log files for VMware products (1021806).

Solution

Virtual machine names and world numbers can be correlated using several methods. Each virtual machine is comprised of several worlds. Most utilities refer to the virtual machine by its cartel ID and/or by the world number for its vCPU 0. Some methods are only available on specific versions of ESX/ESXi. Choose the method appropriate for your environment:

VMkernel logs during virtual machine startup

Virtual machine's logs during virtual machine startup

The esxcli command-line utility on ESXi 5.0

The vmdumper command-line utility on ESX/ESXi 3.0-5.0

The vm-support command-line utility on ESX/ESXi 2.0-4.1

VMkernel logs during virtual machine startup

Prerequisites

A virtual machine was previously running on this host.

The VMkernel logs are available from the timeframe when the virtual machine started. For more information, see Location of log files for VMware products (1021806).

On ESX/ESXi 3.0 - 5.0, the VMkernel logs a message during virtual machine startup containing both the virtual machine's world number and display name. To find this information:

Open the VMkernel log from the ESX/ESXi host.

Identify the startup of the virtual machine's virtual CPUs by the log message.

Example:

cpu<N>: 1264298) World: vm 1268395:<nnnn>: Starting world vmm0:<VirtualMachineName> with flags <mmmm>

Two worlds are listed. The first world number is the virtual machine cartel (in this example, 1264298). The second world number (in this example, 1268395) is the Virtual Machine Monitor (VMM) for each vCPU (in this example, vmm0). A separate line is logged for each virtual CPU started.

Virtual machine's log during virtual machine startup

Prerequisite

Virtual machine logs are available from the timeframe when the virtual machine started. For more information, see Location of log files for VMware products (1021806).

On ESXi 3.5 - 5.0, the virtual machine logs a message during startup containing the virtual machine's world number, along with display name and other configuration information. To find this information:

Locate the the virtual machine's vmware*.log file. Normally, this file is located in the same directory as the virtual machine's .vmx configuration file.

Open the virtual machine's vmware*.log file.

Identify the startup of the virtual machine's virtual CPUs by the VMMon_Start log message. This message appears similar to this:

<date and time stamp>| vcpu-0| VMMon_Start: vcpu-<N>: worldID=1268395

The world number logged is associated with the Virtual Machine Monitor (VMM) for each vCPU (in this example, vcpu0). A separate line is logged for each virtual CPU started.

Identify the virtual machine's configuration section, which reports the display name of the virtual machine. It appears similar to this:

<date and time stamp>| vmx| DICT displayName=<VirtualMachineName>

Identify the name of the ESX/ESXi host which the virtual machine was running on. This information is on a which appears similar to this:

<date and time stamp>| vmx| Hostname=<ESXHostname>

The esxcli command-line utility on ESXi 5.0

Prerequisites

A console session open to the ESXi host, either at the local console or via SSH. For more information, see the Managing vSphere with Command-Line Interfaces section of the vSphere Command-Line Interface Documentation.

A virtual machine currently running on this host.

The hostd management service running.

On ESXi 5.0, the esxcli command-line utility can be used locally or remotely to display a list of the virtual machines which are currently running on the host. To display this list:

Log in to the ESX/ESXi host console as root, or open a console at the location that esxcli or vCLI is installed.

Obtain a list of all running virtual machines, identified by their World ID, Cartel ID, display name and path to the .vmx configuration file using this command:

esxcli [connection_options] vm process list

The output appears similar to this:

VirtualMachineName
World ID: 1268395
Process ID: 0
VMX Cartel ID: 1264298
UUID: ab cd ef ...
Display Name: <VirtualMachineName>
Config File: </path/VirtualMachineName>.vmx

Two worlds are listed. The first world number (in this example, 1268395) is the Virtual Machine Monitor (VMM) for vCPU 0. The second world number (in this example, 1264298) is the virtual machine cartel ID.

The vmdumper command-line utility on ESX/ESXi 3.0-5.0

Prerequisites

A console session open to the ESX/ESXi host, either at the local console or via SSH. For more information, see Tech Support mode for Emergency Support (1003677) or Using Tech Support Mode in ESXi 4.1 (1017910).

A virtual machine currently running on this host.

On ESX/ESXi 3.0 - 5.0, the vmdumper command-line utility can be used on the host console to display a list of the virtual machines which are currently running on the host. To display this list:

Log in to the ESX/ESXi host console as root.

Obtain a list of all running virtual machines, identified by their World ID, path to the .vmx configuration file, display name and Cartel ID using the command:

ESXi: /sbin/vmdumper -l

ESX: /usr/lib/vmware/bin/vmdumper -l

The output appears similar to this:

wid=<nnnnnn> pid=-1 cfgFile="/vmfs/volumes/<path/to/VirtualMachineName>.vmx" uuid="ab cd ef ..." displayName="<VirtualMachineName>" vmxCartelID=<nnnnnn>

Example:

wid=1268395 pid=-1 cfgFile="</path/VirtualMachineName>.vmx" uuid="..." displayName="..." vmxCartelID=1264298

Two worlds are listed. The first world number (in this example, 1268395) is the Virtual Machine Monitor (VMM) for vCPU 0. The second world number (in this example, 1264298) is the virtual machine cartel ID.

Command-line utility: vm-support on ESX/ESXi 2.0 - 4.1

Prerequisites

A console session open to the ESX/ESXi host, either at the local console or via SSH. For more information, see Tech Support mode for Emergency Support (1003677) or Using Tech Support Mode in ESXi 4.1 (1017910).

A virtual machine currently running on this host.

On ESX 2.0 - 4.1 and ESXi 3.5 - 4.1, the vm-support command-line log collection utility can be used to display a list of the virtual machines which are currently running on the host. To display this list:

Logi n to the ESX/ESXi host console as root.

Obtain a list of all running virtual machines, identified by their World ID and display name, using this command:

vm-support -x

The output appears similar to this:

Available worlds to debug:
wid=1268395 <VirtualMachineName>

The world number logged (in this example, 1268395) is associated with the Virtual Machine Monitor (VMM) for the first vCPU (vcpu0). The cartel ID is not reported.

Additional Information
For translated versions of this article, see:

日本語: 仮想マシンのワールド番号を仮想マシン名にマッピングする (2101986)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
ユーザーが Horizon Cloud Hosted 環境でドメイン バインド アカウントの詳細を更新できない (66888)

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

KB
•
滚动维护任务卡在静默状态 (66843)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant