Yep - I see that occasionally as well - sometimes I just wait half an hour until the system is responsive again.
Most of times I see this when I overcommit RAM or run very large VMs.
As I run WS 8 to know WS 8 I dont care.
If I would use WS 8 just to run a few VMs like 99.99% of the other users - I would revert back to WS 7
well, it's good to know I'm not alone. My VM has not come back after 20+ hours (and it looks as if my only way to kill VMware Workstation 8 in that case is to use the Task Manager). I can run any other VM, so I'm not dead in the water even without killing it.
I have submitted a formal support request.
kill vmware.exe first - then restart Workstation and check if that VM is still hanging.
If yes - kill vmware-vmx.exe
I've collected a few clues in replicating this hang.
One is that it occurs after our software application is intensively accessing (read only) a particular file on a VMware shared folder. If I access the same file and folder using a Windows network file share, this hang does not occur!
The other clue is that frequently (not always) when the hang occurs, simultaneously I get a message on the message log "the default sound device cannot be opened".
I've repeated this dozens of times. The hang isn't always a hang. Sometimes (perhaps 3-2 times) I get an actual VMware error message (see some attachments). Other times it just appears that Windows has crashed (with no particular error message). Occasionally I just get a file open error; but if I then proceed to do anything with Windows, it will quickly hang.
I did file a problem report with VMware support, and I am told that they are working on it.
I was able to reproduce this VMware Workstation 8 hang using a Windows Vista 32-bit guest system (otherwise the identical setup).
cant you use regular Windows filesharing ? - vmware shared folders are famous for such obscure effects
if you want something reliable just dont use them
yes I can -- and it works! I just figure that shared folders are a feature of VMware Workstation that worked with no such problems in prior versions (pre-8) and we should get what we paid for!