Eric,

Is there a chance you are running FileVault on your Mac? If so, see the following note from the VMware Fusion release notes that will likely solve this problem:

Virtual machines that are stored in a FileVault home folder or encrypted disk image might become unresponsive or quit unexpectedly during suspend and snapshot operations. To avoid this problem, move your virtual machines out of the FileVault protected home folder or encrypted disk image. As an alternative, you can manually edit your virtual machine configuration (.vmx) file:

• Power off the virtual machine.
• In the Finder, locate the virtual machine configuration (.vmx) file and open the file in a text editor such as TextEdit. Note: If the virtual machine files are stored in a package (with the extension .vmwarevm), Control-click or right-click the package in the Finder and select Show Package Contents to find the configuration file.
• Add the following line to the configuration file: mainmem.useNamedFile = “FALSE”
• Save the configuration file.
• Power on your virtual machine.

Suspend and snapshot operations will take longer now, but the virtual machine should no longer quit unexpectedly or become unresponsive during those operations.

Hi, Pat. Thanks for writing! I am not running FileVault.

The virtual machine doesn’t seem to be the problem because it runs on my other machine. The VM isn’t quitting — the entire VMWare Fusion application is crashing.