Not seen it before.
From the service console, I would try :-
vmware-cmd <path to vmx file> getstate
Which should tell you the state vmware thinks the vm is in.
You might then try a vmware-cmd <path to vmx file> stop or vmware-cmd <path to vmx file> reset
Alternatively do a ps -ef | grep "<some part of vm name>" to see if an associated vmware-vmx process is running, and maybe kill it off.
If you found this helpful please consider the use of the Helpful /Correct buttons to award points. Thanks!!
If you found this helpful please consider the use of the Helpful /Correct buttons to award points. Thanks !!