"The total number of virtual CPUs present or requested in the virtual machines' configuration has exceeded the limit on the host" occurs when attempting to power on the Virtual Machine in vCenter Server.
search cancel

"The total number of virtual CPUs present or requested in the virtual machines' configuration has exceeded the limit on the host" occurs when attempting to power on the Virtual Machine in vCenter Server.

book

Article ID: 344239

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Virtual machine power-on operations may fail in a vSphere DRS-enabled cluster with the error: "The total number of virtual CPUs present or requested in the virtual machines' configuration has exceeded the limit on the host." This error is triggered by cluster-level resource admission control policies defined in vSphere DRS, which enforce maximum vCPU-to-pCPU ratios or specific advanced parameter constraints. This article provides steps to identify the active policy and adjust the configuration to allow the power-on operation.

Symptoms :

  • Unable to power On VMs from vCenter server with DRS enabled.
  • Power-on succeeds if DRS is disabled.
  • Can power on the VM directly from ESXi host.
  • Error message: "The total number of virtual CPUs present or requested in virtual machines' configuration has exceeded the limit on the host: [XXX]"
  • From /var/log/vmware/vmware-vpxd/vpxd.log,
    • YYYY-MM-DDTHH:MM:SSinfo vpxd[08244] [Originator@6876 sub=vpxLro opID=PowerOnResolver-applyOnMultiEntity-4254-ngc-84] [VpxLRO] -- BEGIN task-480576 -- datacenter-2 -- vim.Datacenter.powerOnVm -- 52####2e-70ec-6b64-3997-4b52####e89c(520###78-6fe3-fe7f-db7c-d301####ff84)
      YYYY-MM-DDTHH:MM:SS info vpxd[08244] [Originator@6876 sub=vpxLro opID=PowerOnResolver-applyOnMultiEntity-4254-ngc-84-01] [VpxLRO] -- BEGIN lro-3315 -- -- DrmClusterVmPowerOn --
      YYYY-MM-DDTHH:MM:SS error vpxd[08244] [Originator@6876 sub=drmLogger opID=PowerOnResolver-applyOnMultiEntity-4254-ngc-84-01] DrmFault: reason powerOnVm, vm <VM_NAME>, host <IP_ADDRESS>, fault [class Vim::Fault::NumVirtualCpusExceedsLimit:0x000000f7b4e14860]
  • Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

  • VMware vCenter Server 6.x
  • VMware vCenter Server 7.x
  • VMware vCenter Server 8.x

Cause

The error is caused by a violation of cluster-level CPU allocation limits defined in the DRS settings. This can be due to:

  • CPU Over-commitment Ratio:
    • An enforced limit on the maximum vCPU:pCPU ratio for the cluster.
  • Advanced DRS Parameter:
    • The MaxVcpusPerCore advanced parameter is configured, enforcing a strict cap on vCPUs per host core.

Resolution

To resolve this issue, adjust the DRS configuration settings to accommodate the required workload.

  1. Navigate to the vSphere Client and select the Cluster.
  2. Navigate to the Configure tab.
  3. Select vSphere DRS under the Services section.
  4. Click Edit... to open cluster settings.
  5. Expand Advance Options
  6. Disable the CPU over-commitment (or) increase the limit to accommodate more vCPUs per cluster:
    • Review the MaxVcpusPerCore advanced parameter. If configured, adjust the value higher or remove the parameter if it is no longer required for your workload.
  7. Click OK to save changes
  8. Attempt to power on the virtual machine again.

Additional Information

  • Similar issue is observed when VCHA is configured. Passive node fails to power on due to CPU overcommitment ratio.
  • Maximum vCPUs per DRS cluster is calculated as below : Total pCPU in the cluster x (CPU over-commitment /100)