I'm not sure how I got it into this state, but I REALLY need to get to the data on this VM soon. When I start this particular VM, below the VM name, next to the spinning gear, it just says "Stopping..." How can I get it out of this state?
How to kill it without rebooting I had the same problem, Windows XP was stuck in the "stopping" state for a day and rebooting did not fix the problem. Quit Parallels and open Activity Monitor in Utilities and have it show All Processes. Sort by Process name and look for all the processes that begin with prl_ Note the PID numbers for each process. Next open up a Terminal window (also under Utilities) and type "sudo kill xxxx" for each PID. I am not sure why rebooting did not fix my problem. My assumption is the VM (or Mac OS) remembers the state and tries to reload the process which had effectively crashed. Killing the process this way eliminates the state entirely. Plus you can open Parallels right back up and have it work. It did for me. I also don't have anything crucial on my VM so if it truly kicks the bucket it is only an inconvenience for me.
Thanks, but... Thanks dfobert, I'm going to have to file this somewhere in case it happens again. I managed to get out of it by restoring my virtual machine file from my Time Machine backup. Had to go back a few months. Fortunately, even though the information on it is critical, it only changes in spurts, and I've yet to find that I've lost anything valuable. If it happens again, I'm going to try your suggestion to see if it gets me out the jam. Thanks, ASL.Roger
Thank you!!! Thanks dfobert, I know you posted this quit sometime ago but I just experienced this issue where Windows 7 got stuck in the Stop state and I follow your directions and they worked perfectly! Thanks again.
