As I upgraded to VMWare Fusion RC1 recently based on the comments from Ben G from VMWare as RC1 supports Global keys, experimental Suspend and Revoke, Snapshots and Unity features. The upgraded one is really doing good especially the performance and overall appearance. In case if you have the older build of Fusion, I recommend going ahead with the newer one.
As I wrote earlier, by default the suspend feature is not enabled. So, you have to manually enable it by changing suspend.disabled= “TRUE” to “FALSE” from the file ~/Library/Application\ Support/VMware\ Fusion/Virtual\ Machines/Boot\ Camp*/Boot\ Camp\ partition.vmwarevm/Boot\ Camp\ partition.vmx; which makes it easy to suspend and revoke the OS within the virtual environment. That seemed to work for few days and lately I noticed a strange problem.
Since a day or so, whenever I needed to suspend my guest Vista OS within fusion, it pops up a login dialog to enter the sudo access and then it hangs and nothing that it takes..nor I can type anything in dialog and the fan starts spinning like anything. I can’t get the control back to either of the OS; so only option is to recycle the power and start both the OS back.
As an alternative I tried to disable the suspend feature ( suspend.disabled= "TRUE"); then the Vista doesn’t even boot to the OS and it just hangs as blank screen after the initial bios process. Looks like there is some suspend state which fusion uses is causing this; and boots back fine without any problem once I enable the suspend feature.
Have you found any solution to this? I’m having the same issue with Win2K and Ubuntu guest OSes on the final production release of Fusion. Even worse, power cycling the host appears to sometimes corrupt the .vdk file associated with the image. So then I can’t boot the guest OSes until I provide them with a repaired/backed-up .vdk file.
Not really, thats why I have to make a switch back to PC laptop.