To sum up:
1. Obviously using less resources, (OSX flies). Parallels can bring OSX to a crawl for seconds at a time.
2. It can suspend (from inside the VM) a Bootcamp VM, using 2% CPU. Parallels Pause function still uses 9-10%.
3. It can hibernate a Bootcamp VM, where as in Parallels every time you want to quit the program you need to shutdown Windows completely. ( I am talking about Bootcamp VMs)
4. Faster CPU, memory and IO, (at least in Bootcamp).
5. Does not corrupt Windows VM. (The last version of Parallels has a lot of problems with crashing Bootcamp for no apparent reason)
6. As a cocoa app, it keeps WindowServer memory to a minimum. (Parallels ups WindowServer memory to 170-300 MBs, cause they say it's a QT app and needs to present 60 open windows to windowserver, even with no VM loaded). I would really like an explanation from the VMware engineers that so kindly help us here, if that is true, that a QT app needs 300 MBs of WindowServer memory and what is the downside for the host system (OSX).
7. It starts and stops much faster than Parallels.
8. Much better USB2 support, with more special devices like WM phones and stuff.
9. Impressed with this forum, where I see Vmware engineers and programmers actively participating and helping, when in Parallels forums plain users try to help or fight each other, with Parallels people absent.
10. Extreme stability, didn't crash once. Parallels crashes at least once a day.
1. In my case (Bootcamp-Core2Duo Macbook Pro, 2GB RAM, 10.4.9), 2 CPUs in the VM makes guest XP slower.
2. Slower 2D graphics. (40-50% of Parallels, depending on the action)
3. When in full screen, Command+H is not working. After hiding it through menu and bringing it back, it does not come completely in front unless you click on something on the Mac tray (clock let's say), or right click on it's dock icon. Very annoying. Also annoying is the warning that comes up every time I reopen Fusion and go full screen.
4. At work I use bridged networking. My ethernet is connected to the internal network, and my airport to my own personal ADSL fast line. In OSX I give the gateway to the Airport, and I use Ethernet to mount my servers on the desktop. My Windows VM is configured to use Ethernet so it can join and use the Domain and active directory. With Fusion that can not be the case. The moment I activate Airport with a gateway IP, Fusion decides that that is the primary interface and ignored ethernet. In Parallels I can choose in bridged mode if I want it connected to Airport or Ethernet.
5. At work and connected to the Domain, it never opens it the first time. (??). I double click, it produces an error message, and the second time it connects.
6. Drag and drop between guest and host is not working all the time, sometimes it produces an error message.
7. It doesn't use a seperate hardware profile in Bootcamp VM. Result is that in Device Manager is still a "Multiprocessor ACPI PC".
That's all for now guys, to sum up the goods and bads. I am sticking with you, especially after the rumours of the latest version of Parallels ruining Macbook's batteries, but please do something at least with the 2D speed.
Message was edited by: