Virtual machine does not power on when there is high CPU reservation
book
Article ID: 313075
calendar_today
Updated On:
Products
VMware vCenter ServerVMware vSphere ESXi
Issue/Introduction
Unable to power on virtual machine
The following error messages are displayed:
CPU min outside valid range
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:VM1. (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:VM1. (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) []
Environment
VMware vSphere ESXi 6.x VMware vSphere ESXi 7.x VMware vCenter Server 7.x VMware vCenter Server 6.x
Resolution
This issue occurs if the CPU min value is outside the valid range that the PCPU cannot serve.
The CPU min value may become invalid if:
The virtual machine was migrated from one host to another and PCPU capacity of the destination host is less than that of the source host.
The PCPU values were changed after the virtual machine was created and the current PCPU capability is insufficient to meet the virtual machine requirements.