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

Permissions on Configuration Files (.vmx) and Their Effects on Virtual Machine Functionality (1904)

Last Updated: 3/24/2017Categories: TroubleshootingTotal Views: 16503Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

How do Unix file permissions affect a virtual machine's functionality on an ESX Server system?

Solution

The permissions set on the virtual machine's configuration file (.vmx) affect how other users on the system can start the virtual machine, shut it down, or view it in the management interface.

Read (r)
Users can see the virtual machine in the management interface.

Read and Execute (r x)
Users can:

Start, stop, reset, and suspend the virtual machine through the management interface, remote console, and API.

Access the virtual machine's configuration files as read only.

Read and Write (r w)
Users can:

Access the virtual machine from the management interface.

View the details and event logs.

Configure the virtual machine and save the changes through the management interface.

Connect to a virtual machine via API.

From the command-line interface, access and modify the files that make up the virtual machine.

Users cannot:

Connect to the virtual machine through the remote console.

Control the power to the virtual machine.

Read Write and Execute (r w x)
Users have full access to act on and modify the virtual machine.

Important: All the directories leading to the .vmx file must have execute permissions for the particular area (user, group, or others) in order for the changes to be valid and for users to access it (users of the flagship group cannot access it). For the flagship user, set permissions to 710 on all the directories leading to the .vmx file; set permissions to 711 for everyone to view the .vmx file.

Note: Unix file permissions cannot cover all possibilities, such as granting only remote console access for a user. Please consider using VirtualCenter for a specific and more elaborate permission set.

For more information on setting access rights and permissions in VirtualCenter, see Managing VMware VirtualCenter Roles and Permissions.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX Server 2.5.x

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