A VM that has CPU limitation set on it will cause the vm to stop if the limitation is set to 0.
These log types can contain similar messages to the following:
hostd.log:YYYY-MM-DDTHH-MM-SS info hostd[#######] [Originator@#### sub=Vimsvc.ha-eventmgr] Event ####### : Issue detected on fqdn.hostname in ha-datacenter: CpuSched: ####: Container group(########): host/user/vm.######## is configured with 0 CPU max
YYYY-MM-DDTHH-MM-SS info hostd[#######] [Originator@#### sub=Vimsvc.ha-eventmgr] Event ####### : Issue detected on fqdn.hostname in ha-datacenter: CpuSched: ####: Container group(########): host/user/vm.######## is configured with 0 CPU max
YYYY-MM-DDTHH-MM-SS info hostd[#######] [Originator@#### sub=Vimsvc.ha-eventmgr] Event ####### : Issue detected on fqdn.hostname in ha-datacenter: CpuSched: ####: Container group(####): host/user/vm.####### is configured with 0 CPU max
vmkernel.log:YYYY-MM-DDTHH-MM-SS cpu23:####### opID=########)ALERT: CpuSched: ####: Container group(########): host/user/vm.######## is configured with 0 CPU max
YYYY-MM-DDTHH-MM-SS cpu12:#######)ALERT: CpuSched: ####: Container group(########): host/user/vm.######## is configured with 0 CPU max
YYYY-MM-DDTHH-MM-SS cpu36:####### opID=#######)ALERT: CpuSched: ####: Container group(#######): host/user/vm.####### is configured with 0 CPU max
vmkwarning.log:YYYY-MM-DDTHH-MM-SS cpu23:####### opID=#########)ALERT: CpuSched: ####: Container group(########): host/user/vm.######## is configured with 0 CPU max
YYYY-MM-DDTHH-MM-SS cpu12:#######)ALERT: CpuSched: ####: Container group(########): host/user/vm.######## is configured with 0 CPU max
YYYY-MM-DDTHH-MM-SS cpu36:####### opID=#########)ALERT: CpuSched: ####: Container group(#####): host/user/vm.######## is configured with 0 CPU max
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
Set the CPU limitation to unlimited when trying to clear the CPU limitation instead of 0