This happened 3 times so far within 1 1/2 weeks and it is highly annoying having bounce a server because of this:
XP guest locks up - black screen, curser/keyboard unresponsive and if the curser is left active in the XP guest, it's stuck there as well and can't be moved to another window.
After stopping vmplayer (either Ctl-C in start window) or killing, it is no longer possible to run vmplayer or restart vmware services for that matter:
~# /etc/init.d/vmware stop
Stopping VMware services:
At least one instance of VMware Player is still running.
Please stop all running instances of VMware Player first.
because vmware leaves a zombie process:
~# ps -ef | grep vm
root 6398 26773 0 20:25 pts/24 00:00:00 grep vm
sam 26878 1 18 16:43 ? 00:41:57 Windows XP guest hangs, vmplayer creates zombie and Linux host needs reboot
so, what's the 26878 process up to?
~# l /proc/26878/task
total 0
dr-xr-xr-x 5 sam users 0 2008-10-03 19:21 26878
dr-xr-xr-x 5 root users 0 2008-10-03 19:21 26932
~# ps -p 26932
PID TTY TIME CMD
- can't be seen with ps and it's waiting for disk i/o
~# cat /proc/26878/task/26932/status
Name: vmware-vmx
State: D (disk sleep)
Tgid: 26878
Pid: 26932
PPid: 1
TracerPid: 0
Uid: 201 0 0 0
Gid: 100 100 100 100
FDSize: 256
Groups: 20 24 25 29 44 46 100
- shared memory segments relating to the vmplayer software complex are still present as well in that situation:
-
Shared Memory Segments -
key shmid owner perms bytes nattch status
0x00000000 188153858 sam 700 16777216 1 dest
0x00000000 188186627 sam 700 48600 2 dest
0x00000000 131530757 sam 600 196608 2 dest
0x00000000 188252166 sam 700 2956800 2 dest
For what it's worth......