Thanks for the info, Rick. I ran through all that and I was not able to resolve my issue. It seems the machine is stuck in a "powered on" status, but it is not actually on and I can't get it to turn on or off. When I try to access the console, it says "Unable to connect to the MKS: Error connecting to <path to .vmx> because the vmx is not started.
Have you tried from the service console doing a "service mgmt-vmware restart" then trying with the client again?
I have not tried doing that and I'm still new enough at this that I didn't try it on my own.
Thanks! That did the trick! I will keep that one in the back of my mind for the future.
glad it worked, might want to check this kb out also in case you find yourself on a 3.5U1 host. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003696
RE: 2. vm-support -X
<VMID> - this doesn't work because if I run this without the VMID
it doesn't even list the server I'm trying to kill in there.
Ans: first you need to run
This will list the running VMs and the WID, use the WID to run the command below. Substitute the <WID> with the WID of the specific VM.
vm-support -X <WID>