Cloud IBR Expands Disaster Recovery for MSPs — Scalable, on-demand recovery without idle infrastructure

READ PRESS RELEASE
Try It For Free
Book A Demo

VM Fails to Power On Due to vCPU Count Exceeding Physical CPU Capacity

Summary

A virtual machine (VM) may fail to power on when the configured number of virtual CPUs (vCPUs) exceeds the number of physical CPUs available on the ESXi host.

Cause

The VM that was recovered has more vCPUs (24) assigned to it than the ESXi host you recovered to has (16 physical CPUs). As a result, the hypervisor prevents the VM from powering on due to CPU resource constraints.

Error Details

While attempting to power on the VM, the following error is encountered:

Key: haTask-10-vim.VirtualMachine.powerOn-15796

Description: Power On this virtual machine

Virtual machine: vapbnrcustomer-Recovered

State: Failed - Module 'MonitorLoop' power on failed.

Errors:

  • The number of virtual CPUs (24) is greater than the number of physical CPUs (16).
  • Could not power on virtual machine: Number of running VCPUs limit exceeded.
  • Module ‘MonitorLoop’ power on failed.
  • Failed to power on VM.
  • Failed to start the virtual machine.

Resolution

To resolve the issue, choose one of the following options:

Option 1: Use a Larger ESXi Host

Select a higher amount of RAM on the Cloud Providers tab in the Cloud IBR Portal. By selecting a higher RAM option, you will be assigned a host that also has more CPUs. This option requires you to upgrade your Cloud IBR account if you are currently limited to smaller ESXi hosts.

Option 2: Reduce the Number of vCPUs

Modify the VM configuration in your recovery environment to match the available host resources.

Steps:

  1. Log in to the ESXi host.
  2. Locate and Edit the Settings for the affected VM.
  3. Reduce the number of virtual CPUs to a value equal to or less than the host’s physical CPU count (e.g., 16 or fewer).
  4. Save the changes and power on the VM.