| 1 |
On Tue, 2010-02-02 at 16:12 -0800, Mark Knecht wrote: |
| 2 |
> Hi, |
| 3 |
> I was running VMWare and the program inside of Windows has crashed. |
| 4 |
> (Or maybe Windows crashed or maybe VMWare crashed - I cannot tell.) |
| 5 |
> |
| 6 |
> Gentoo is still alive and I can log in and look around but the |
| 7 |
> mouse on that computer but its mouse is frozen so I cannot do anything |
| 8 |
> at its screen. It seems the keyboard is dead also. |
| 9 |
|
| 10 |
So can you do things once logged in? Which screen are you talking |
| 11 |
about? Sounds like you're host is locked up, not just the guest? |
| 12 |
|
| 13 |
> top says there's nothing going on. No CPU cycles at all. |
| 14 |
> |
| 15 |
> Is there a way for me to ask Linux to talk to VMWare and see if it |
| 16 |
> can shut itself down before I hit the reset button? |
| 17 |
|
| 18 |
as in "tell VMWare to do a windows shutdown"? Not that I'm aware of. |
| 19 |
|
| 20 |
killall -15 vmware |
| 21 |
|
| 22 |
will send the SIGTERM to all vmware named processes. (You may need to |
| 23 |
use vmware-workstation, or just use ps to get the PID). If that doesn't |
| 24 |
work, follow up with a |
| 25 |
killall -9 vmware |
| 26 |
|
| 27 |
Then if you're still stuck, gnome-session-save with either --logout or |
| 28 |
--force-logout should log you out nicely. If that gets stuck, try |
| 29 |
|
| 30 |
kill -15 -1 |
| 31 |
from your user login (not root) to kill all your processess. Again, |
| 32 |
maybe a |
| 33 |
kill -9 -1 |
| 34 |
is required. It will log you out of the ssh session. |
| 35 |
|
| 36 |
If that fails (as you can tell I've done this before) try an acpi |
| 37 |
shutdown. If that fails, use the magic SysRq, but I don't think you'll |
| 38 |
need to go that far since you can ssh in. |
| 39 |
-- |
| 40 |
Iain Buchanan <iaindb at netspace dot net dot au> |
| 41 |
|
| 42 |
Simon: "My God - you're like a trained ape. Without the training." |
| 43 |
--Episode #7, "Jaynestown" |
Archives