Error: "Total CPU required for all VMs in the VRP including current VM(s) being deployed [<value>MB] is greater than VRP maxResourceValue 0MHz" occurs when powering on VMs
search cancel

Error: "Total CPU required for all VMs in the VRP including current VM(s) being deployed [<value>MB] is greater than VRP maxResourceValue 0MHz" occurs when powering on VMs

book

Article ID: 414657

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

VMs fail to power on and the error "Total CPU required for all VMs in the VRP including current VM(s) being deployed [<value>MB] is greater than VRP maxResourceValue 0MHz"..

Environment

VMware Cloud Director 10.6.x

Cause

Mismatch between the reservation at VM and VDC level.

Resolution

Setting the compute (both cpu and memory) Allocation to 0 at org vDC level.

  • Login to the VCD Provider portal->Organization VDC->Allocation->Edit and update the CPU resources guaranteed and Memory resources guaranteed to 0 and save.

Try power-on the VM, if issue still persists we need to manually clear the reservation at the VM level.
Once the vdc compute reservation was made 0. These vm(s) were still holding the reservations and were not cleared.

To verify such vm(s) for the specified effected org Vdcs follow below steps:

   1.SSH into the primary node.
   2.Connect to the database using the below query.
          sudo -u postgres psql vcloud;
   3.Run the below to get the list of the VM's.

select ovdc.name, vi.mem_reservation, vi.cpu_reservation, vi.name as vc_vm_name, vi.moref from vm_container vapp join vapp_vm on vapp.sg_id = vapp_vm.vapp_id join vm on vapp_vm.svm_id = vm.id join vm_inv vi on vi.moref = vm.moref join org_prov_vdc ovdc on vapp.org_vdc_id = ovdc.id and vi.vc_id = vapp.vmfolder_vc_id and vi.state = 1 and (vi.mem_reservation > 0 or vi.cpu_reservation > 0) and ovdc.name in ('OVDC_Name');

   4.Steps to clear reservation from vCenter side:

  • Locate and open the VM in vCenter → Actions > Edit Settings.
  • In the pop-up window, expand the CPU and Memory sections.
  • Set both CPU Reservation and Memory Reservation to 0, then save the changes.
  • Repeat the steps for all affected VMs identified from the above query results.

   5.Once the reservation on all VMs are set to 0, try powering-on the VM. It will power-on without any issues.

Additional Information