vim-cmd vmsvc/getallvmsesxcli vm process listStorage outage caused a split brain scenario and hostd could not locate the .vmx file while the vmx process was still running on the hosts memory
1. Try to restart the ESXi management agents
/etc/init.d/hostd restart/etc/init.d/vpxa restart
2. If the VM is not back in inventory, re-register via esxcli and restart management agents again
vim-cmd solo/registervm /vmfs/volumes/DatastoreName/VMFolder/VMName.vmx/etc/init.d/hostd restart/etc/init.d/vpxa restart