Virtual Machine Reboot In Progress For 2 hours

[ThePieMonster]

I told a virtual machine to reboot itself using the vCenter Web Client 2 hours ago and its still just sitting in limbo and I am unable to communicate with it. How can I fix this? I already tried restarting the vCenter server which didn't help accomplish anything.

Running vSphere 6.5.

[DavoudTeimouri]

You should kill the machine process on your ESXi.

Check this KB:Unable to power off the virtual machine in an ESXi host (1014165) | VMware KB

[ThePieMonster]

I got the VM's world number and then used the command below to kill the process.

esxcli vm process list

esxcli vm process kill --type=[soft,hard,force] --world-id=WorldNumber

Unfortunately the above didn't turn off the VM nor did the task that is trying to reset the virtual machine stop. So I tried the below but it dosn't seem to find the process even though its listed right above it.

[SureshKumarMuth]

Looks like the process became zombie. You need to reboot the ESXi host.

[RajeevVCP4]

It seems virtual machine locked on other host, Unlock vm then try power off.

Investigating virtual machine file locks on ESXi (10051) | VMware KB

https://www.vmadmin.co.uk/resources/35-esxserver/90-vmfslockedfilerelease

Or restart service on host,

Services.sh restart and see if process killed.

[ThePieMonster · Accepted solution]

I ended up just rebooting the ESXi host. VMware you guys need to implement some form of a failsafe or way of unlocking these processes from the web interface. Having to reboot your host in the middle of the day is not a acceptable solution.