Module MonitorLoop power on failed.
This virtual machine failed to switch to 64 bit mode. This failure might be due to a lack of available memory on the host.
[YYYY-MM-DDTHH:MM:SS] vmkernel: cpu64:2417769)World: vm 2417772: 7244: Starting world vmm0:<Name_of_the_vm> of type 8
[YYYY-MM-DDTHH:MM:SS] vmkwarning: cpu64:2417769)WARNING: World64: 1112: Failed to instantiate VMM bootstrap blob: Failure
[YYYY-MM-DDTHH:MM:SS]vmkernel: cpu10:4322487)Vmxnet3: 459: Memory region is completely overlapped 4004dc2
[YYYY-MM-DDTHH:MM:SS]vmkernel: cpu51:4322965)Vmxnet3: 459: Memory region is completely overlapped 4004dcd
VMware vSphere ESXi 8.0.x
This is caused by XMap fragmentation/exhaustion for the VMXNet3 device
There are multiple ways to solve this issue:
# esxcli system settings kernel set -s "xmapGB" -v 64
# esxcfg-advcfg -s 0 /Net/Vmxnet3MemoryRegions
# esxcfg-advcfg -s 64 /Net/NetMaxMemRegPerDevice
Note: Options 1 and/or 3 will not completely remove the risk of xmap exhaustion. If the number of virtual machines running on the host that use memory regions gets too large, the issue might still occur. If this happens, you can either select option 2 instead or reduce the number of VMs by spreading them out across other hosts.
The VMNet3 memory regions feature was implemented to allow performance-centric VMs/VNICs such as DPDK VMs to pre-map some memory for better performance.