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

My Subscriptions

Loading

Knowledge Base

Investigating power on permissions for ESX/ESXi virtual machines (1003739)

Last Updated: 8/9/2017Categories: TroubleshootingTotal Views: 20864Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Unable to power on a virtual machine.

When trying to connect to the console of a virtual machine from vCenter Server/VirtualCenter you receive the error:

Error connecting: You need execute access in order to connect with the VMware console. Access denied for config file

Resolution

vCenter Server/VirtualCenter Permissions

Permissions can be set in vCenter Server/VirtualCenter to control Power On operations with virtual machine.

To check if there are sufficient permissions set in vCenter Server/VirtualCenter:

Connect to the vCenter Server/VirtualCenter using vSphere Client/Virtual Infrastructure Client.

Log in as an user with administrator privileges.

Select the Datacenter and click Permissions.

Check if the user account used to log in has at least read-only rights at this level.

Click on the ESX/ESXi host where the virtual machine resides and click the Permissions tab.

Check if the user account used to log in has Virtual Machine user rights at that level.

Check to make sure that the user is not part of a group that has been assigned a restrictive role. This could limit privileges in parts of the inventory hierarchy.

ESX/ESXi File System Permissions

Permissions on configuration files (.vmx ) and their affects on virtual machine functionality

The permissions set on the configuration file (.vmx ) of the virtual machine 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:
o Start, stop, reset, and suspend the virtual machine through the management interface, remote console, and API.
o Access the configuration files of the virtual machine as read only.

Read and Write (r w)
Users can:
o Access the virtual machine from the management interface.
o View the details and event logs.
o Configure the virtual machine and save the changes through the management interface.
o Connect to a virtual machine via API.
o From the command-line interface, access and modify the files that make up the virtual machine.

Users cannot:
o Connect to the virtual machine through the remote console.
o 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.

Note: All the directories leading to the .vmx file must have execute permissions for the particular area (user, group, or others) for the changes to be valid and for users to access it. Unix file permissions cannot cover all possibilities, such as granting only remote console access for a user. Consider using vCenter Server/VirtualCenter for a specific and more elaborate permission set.

Known Issues

When trying to connect to the console of a virtual machine from vCenter Server/VirtualCenter:

Error connecting: You need execute access in order to connect with the VMware console. Access denied for config file.

Resolution: Check the permissions for the virtual machines configuration file.

By default a virtual machine has the following permissions set:

-rw-r--r-- 1 root root 1821 Feb 28 18:13 vm1.vmx

Run 'chmod 755 /vmfs/volumes/<Datastore>/vm/vm.vmx' where <Datastore> is the volume that the virtual machine is located on.

When you perform 'chmod 755 filename' command you allow everyone to read and execute the file, owner is allowed to write to the file as well.

-rwxr-xr-x 1 root root 1821 Feb 28 18:13 vm1.vmx

Related Information

调查打开 ESX/ESXi 虚拟机电源的权限

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

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

KB
•
Microsoft Windows プラットフォームに vCenter Inventory Service 5.5 をインストールする (2058269)

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 VirtualCenter

VMware vCenter Server

VMware vCenter Lab Manager

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.0

VMware VirtualCenter 2.5.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

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