I have Fusion 3.0.2 on Snow Leopard 10.6.3. When I run one VM everything works fine. As soon as I try to create a second VM and run it, Fusion locks my entire system. The cursor freezes and the entire system hangs. I cannot even ssh into the host. I have to hard reboot the machine (hold down the power button until the machine powers down). Obviously this is seriously not good as it has corrupted other applications in the past (e.g. Mail.app). This seems like a very serious bug in Fusion - it should never be able to freeze the host OS.
I had Fusion2 working great, with superb performance on a 15" MacBookPro from 2007. As soon as I upgraded to Fusion 3 (WHY did I do that? And I PAID!) it became unusable. My Windows XP guest takes forever to boot up and the rest of the machine slows to a crawl. Upgrading to 3.1.0 hasn't helped.
Is there a checklist anywhere of things to try for this condition?
Simon
Actually, just today I froze OS X 10.6.6 by running one Linux guest with one CPU. The corrupted both OS X and the Linux guest. Is there really nothing you can do about it? In any case, I've turned on AutoProtect now just to be a little safer.
I now have a reproducible test case. Note that I am now on Fusion 3.1.3 (416484) on OS X 10.6.7. This happens every time for me.
On an Ubuntu guest, check out the current Python 2.7 Mercurial repository:
$ hg clone http://hg.python.org/cpython/
$ cd cpython
$ hg up 2.7
Build it.
$ ./configure && make
Run the full test suite
$ make test
When the test suite hits test_io, the entire Mac will completely freeze, requiring a hard reboot.
If this system is still around can be see the verbose output from that test? Something like:
./python -Wd -3 -E -tt ./Lib/test/regrtest.py -v test_io
Simon