Virtual Machine power on fails with "Module 'MonitorLoop' power on failed; CPU min outside valid range"

Products

• VMware vSphere ESXi

Issue/Introduction

• The Virtual Machine deployed from an OVA fails to power on and displays the following error:
  Failed to power on virtual machine . Module 'MonitorLoop' power on failed. Click here for more details. dismiss
  
  
• /var/run/log/hostd.log have the below entries:
  YYYY-MM-DDTHH:MM:SSZ verbose hostd[1050935] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/######-#####-####-#######/examplevm/examplevm.vmx opID=esxui-####] Disconnected from VM; signaling migration waiter
YYYY-MM-DDTHH:MM:SSZ info hostd[1050935] [Originator@6876 sub=Libs opID=esxui-####] VigorOnlineDisconnectCb: connection closed (is final).
YYYY-MM-DDTHH:MM:SSZ verbose hostd[1050935] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/######-#####-####-#######/examplevm/examplevm.vmx opID=esxui-####] Power On message: Module 'MonitorLoop' power on failed.
--> Group host/user: Invalid CPU allocation requested for virtual machine vmm0:examplevm. (min: 5000 mhz, max: 4294967295, minLimit: 4294967295, shares: 4294967293)
--> Could not power on virtual machine: CPU min outside valid range.
--> Failed to power on VM.
--> Failed to start the virtual machine.
-->
YYYY-MM-DDTHH:MM:SSZ info hostd[1050711] [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/######-#####-####-#######/examplevm/examplevm.vmx opID=esxui-####] Bootstrap online state is not available (expected if VM just started or exited): Fault cause: vim.fault.GenericVmConfigFault


• There is CPU reservation configured on the Virtual Machine.

Environment

ESX 8.x

Cause

This issue arises when the CPU reservation configured on the virtual machine exceeds the physical CPU core capacity of the available ESX hosts.

Resolution

To resolve the issue, please follow one of the below :

1. Configure the CPU reservation after calculating the maximum available on the ESX host. 
For example, if an ESXi host with two CPUs runs at 2500 MHz, the maximum reservation would be calculated as: 2500 x 2 = 5,000 MHz. A VM with a reservation of 5,384 MHz would not be able to power on this ESX host.

2. If feasible, remove the CPU reservation from the Virtual Machine.