Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

Tips for editing a .vmx file (1714)

Last Updated: 4/21/2020Categories: Best PracticesTotal Views: 479155Language:
Chinese (Simplified)JapaneseEnglish

26 like this article

Subscribe to get an email
newsletter with new updates

26 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Details

This article provides tips for editing a virtual machine's configuration file (.vmx).

Solution

Working with the .vmx file

Some workaround procedures include steps that require you to edit .vmx files.

Note these important characteristics of the .vmx file:

The .vmx file is typically located in the directory where you created the virtual machine.

In Windows XP and Server 2003, the default location for the file is:

C:\Documents and Settings\your_user_name\My Documents\Virtual Machines\virtual_machine_name.vmx

In Windows Vista, Windows 7, and Windows Server 2008, the default location for the file is:

C:\Users\your_user_name\My Documents\Virtual Machines\virtual_machine_name.vmx

In Linux, run the vmware-cmd -l command to list the full path to all registered .vmx files.

For ESXi/ESX, the vmInventory.xml (located in /etc/vmware/hostd) contains the .vmx file path of every virtual machine registered to it.

The virtual machine actively writes to its .vmx file. Never edit this file while its virtual machine is running.

Changes to the file are usually version specific. If you upgrade, the workaround you implemented may no longer work.

Before you edit the .vmx file:

Always power off the virtual machine.

Make sure you are logged on as a user with the correct permission level to edit the file.

Make a backup copy of the .vmx file. If your edits break the virtual machine, you can roll back to the original version of the file.

For more information on using the vi editor to edit files, see Editing files on an ESX host using vi or nano (1020302).

Note: VMware also recommends making a backup copy of the edited file. If future administrative changes to the virtual machine overwrite your edited version, you can cut and paste the specific section you want from the backup copy into the current file. Do not replace an entire .vmx file with an older backup.

ESXi/ESX with vCenter Server

Manual additions to the .vmx file from ESXi/ESX are not recognized in vCenter Server. This can cause manual additions to the .vmx file to be overwritten. To resolve this issue, make the required changes to the .vmx file and see Reloading a vmx file without removing the virtual machine from inventory (1026043).

Alternatively, to modify the virtual machine's .vmx file:

Remove the virtual machine from vCenter Server inventory.

To remove the virutual machine from the vCenter Server inventory, right-click the virtual machine and click Remove from Inventory.

Edit the .vmx file.

Re-register the virtual machine from the ESXi/ESX command line.

To register the virtual machine from the command line:

On ESX 3.x, run the command:

vmware-cmd -s register /vmfs/volumes/datastore/virtual_machine_directory/virtual_machine_name.vmx

Where datastore is the datastore name, virtual_machine_directory is the directory containing the virtual machine files, and virtual_machine_name is the name of the virtual machine files.

For example:

vmware-cmd -s register /vmfs/volumes/Storage1/vm1/vm1.vmx

Output of return code =1 indicates success.

On ESXi 3.5, ESXi/ESX 4.x, and ESXi 5.0/5.1/5.5, run the command:

vim-cmd solo/registervm /vmfs/volumes/datastore/virtual_machine_directory/virtual_machine_name.vmx

For example:

vim-cmd solo/registervm /vmfs/volumes/Storage1/vm1/vm1.vmx

Additional Information

For translated versions of this article, see:

日本語: .vmx ファイルの編集のヒント (2092649)

简体中文: 编辑 .vmx 文件的技巧 (2097315)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workstation

VMware vSphere ESXi

VMware GSX Server

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

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