Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

Virtual machine does not power on when there is high CPU reservation

Unable to power on virtual machine
The following error messages are displayed:
- operation is not allowed in current state
- CPU min outside valid range
- Failed to find a host for powering on the virtual machine
- Invalid CPU allocation requested for VM
A message similar to the following may be reported in /var/log/vmware/hostd.log

msg = 'Group host/user: Invalid cpu allocation requested for VM vmm0:V0D0-MVCSSA0-01. (min: 6400 mhz, max: 4294967295, minLimit: 4294967295, shares: 4294967292)\nCould not power on VM : CPU min outside valid range.\nFailed to power on VM',
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   reason = 'Group host/user: Invalid cpu allocation requested for VM vmm0:V0D0-MVCSSA0-01. (min: 6400 mhz, max: 4294967295, minLimit: 4294967295, shares: 4294967292)\nCould not power on VM : CPU min outside valid range.\nFailed to power on VM',
   messageInfo = (vim.vm.Message) []

This issue occurs when the CPU reservation of a virtual machine is greater than the total CPU available on a single processor.

To resolve this issue from vSphere Client:

Connect to the ESX or vCenter Server host with appropriate administrative credentials.
Select the virtual machine from the inventory.
Right-click on the virtual machine and click Edit Settings.
On the Virtual Machine Properties dialog, click the Resources tab.
Select CPU from list under the Settings column.
Use the slider or the Reservation text box to lower the CPU reservation value.

To resolve this issue from the service console:

Establish an SSH session to your ESX host. For more information, see Opening a command or shell prompt (1003892).
Log in as root.
Run the following command to list the location of the configuration files for the virtual machines registered on that ESX host:

vmware-cmd -l
Record the location of the .vmx file (configuration file) for the virtual machine you are troubleshooting.

For example:

/vmfs/volumes/46b2f3eb-ced4c7d8-c1d2-111122223333/<vm-name>/<vm-name>.vmx
If the virtual machine is not registered on the ESX host and you want to search its configuration file, run the following command and press Enter:

find /vmfs -name "*.vmx”
Make a backup copy of the <vm-name>.vmx file.
Open the <vm-name>.vmx file in a text editor and locate the line:

sched.cpu.min = "3230"
The value identified in the quotes exceeds the amount of physical CPU for one core. Lower the reservation by changing this value.
Save the file and exit the editor.
Power on the virtual machine.

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

1 2 3 4 5

1 2 3 4 5

Actions

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)