Powering on a VM fails with Error "Insufficient Resources"

Products

• VMware vCenter Server

Issue/Introduction

Powering on a VM fails with Error "Insufficient Resources" 

/var/log/vmware/vpxd/vpxd.log shows 'InsufficientResourcesFault' 

[timestamp] info vpxd[07070] [Originator@6876 sub=cdrsPlmt opID=################-########] Vm [vim.VirtualMachine:##-######,VMNAME1] failed constraint check false on host [vim.HostSystem:host-######,hostname] with <obj xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/#########-########" xmlns="urn:vim25" versionId="7.0.3.0" xsi:type="LocalizedMethodFault"><fault xsi:type="InsufficientResourcesFault"></fault><localizedMessage></localizedMessage></obj>
[timestamp] info vpxd[07070] [Originator@6876 sub=cdrsPlmt opID=################-########] Vm [vim.VirtualMachine:##-#####,VMNAME2] failed constraint check false on host [vim.HostSystem:host-######,hostname] with <obj xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/#########-########" xmlns="urn:vim25" versionId="7.0.3.0" xsi:type="LocalizedMethodFault"><fault xsi:type="InsufficientResourcesFault"></fault><localizedMessage></localizedMessage></obj>

Disabling DRS allows the VMs to be powered on 

Environment

vCenter Server 

Cause

This is due to an advanced parameter on DRS Advanced settings 'LimitVMsPerESXHostPercent'. The LimitVMsPerESXhost option is implemented as part of DRS constraint check. If the number of virtual machines on the host exceeds the limit specified by the LimitVMsPerESXhost option, no additional virtual machines can be powered on or migrated to the host by DRS.

 

Resolution

Delete the LimitVMsPerESXHostPercent option from the DRS Advanced Options 

• In the vSphere Client, navigate to the vCenter Server instance.
• Select the Impacted Cluster
• Select the Configure tab
• Under Services -> Select vSphere DRS
• Click Edit Settings
• Advanced options -> Select the Option LimitVMsPerESXHostPercent and Delete it.

 

Additional Information

: You can use a new advanced option TryBalanceVmsPerHost to replace LimitVMsPerESXhost option starting vCenter server 6.5.0b release