VM does not power on post scheduled reboot with advanced parameter "vmx.reboot.powerCycle=True"
book
Article ID: 401261
calendar_today
Updated On:
Products
VMware vSphere ESX 7.xVMware vSphere ESX 8.x
Issue/Introduction
VM is enabled with advanced parameter "vmx.reboot.powerCycle=True". However, post scheduled reboot the VM did not power on back automatically.
From /vmfs/volumes/<Datastore-Name>/<VM-Name>/vmware.log, similar log entries will be seen
YYYY-MM-DDTHH:MM:SS.###Z In(05) vcpu-0 - Chipset: The guest has requested that the virtual machine be hard reset. YYYY-MM-DDTHH:MM:SS.###Z In(05) vcpu-0 - Chipset: hard reset being turned into a power cycle. YYYY-MM-DDTHH:MM:SS.###Z No(00) vcpu-0 - ConfigDB: Setting softPowerOff = <not printed> YYYY-MM-DDTHH:MM:SS.###Z No(00) vcpu-0 - ConfigDB: Setting virtualHW.scheduledUpgrade.poweredOffNeedsPowerOn = <not printed> YYYY-MM-DDTHH:MM:SS.###Z No(00) vcpu-0 - ConfigDB: Setting vmx.reboot.powerOffTriggered = <not printed> YYYY-MM-DDTHH:MM:SS.###Z In(05) vcpu-0 - VM reset: Power cycle on reboot requested.
From /var/run/log/hostd.log, similar log entries will be seen
The virtual machine shutdown process overlapped with another management operation specifically, a resource reconfiguration triggered by host synchronization. This conflict can also occur during other operations such as snapshot creation or modification. Due to the simultaneous tasks, the VM may not restart automatically after shutdown.
Resolution
Engineering Team is aware of this issue and will be fixed in future release.