Contributor
Contributor

Fusion 1.1 acting badly after upgrade, please help

Jump to solution

Hello, I was using Fusion 1.1rc and it has started acting badly after I upgraded to 1.1. I also upgrade to Mac OS 10.5.1, then upgraded Fusion to 1.1.

I can only run Fusion for a short time then it just stops running and most of the Virtual Machine menu items are grayed out. Fusion will not quit and I am not given an option to force quit. I can only shut down my machine (MacBook Pro) by holding the power button. Then I can run Fusion for a short time. At this point I am only running Quicken in my VM (Windows XP). It will run for a few minutes and then then window closes and I can't run Quicken or do anything with Fusion. I can't stop, suspend, etc. my VM and again can't quit Fusion unless I hold power button. I have tried different views and have scanned this forum for a similar issue.

Please help me troubleshoot this issue.

Thanks.

0 Kudos
1 Solution

Accepted Solutions
Immortal
Immortal

When I have problems involving upgrades, my first instinct is to do an uninstall and then a clean reinstall. In Fusion's case, it's pretty easy, because uninstalling Fusion does not affect your virtual machines. They will be left unmodified, ready to use again when you reinstall.

Fusion's uninstaller is in the .dmg file that contains its installer.

When uninstalling or reinstalling, make sure that you have only one Fusion .dmg mounted at a time. Some people (me included!) have encountered problems related to having both a beta .dmg and a released .dmg mounted at the same time during an install or an uninstall.

View solution in original post

0 Kudos
2 Replies
Contributor
Contributor

Here is my log file if this helps:

Nov 17 15:29:27.713: vmfusion| Log for VMware Fusion pid=166 version=1.1 build=build-62573 option=Release

Nov 17 15:29:27.714: vmfusion| Hostname=Macintosh-2.local

Nov 17 15:29:27.714: vmfusion| Using log file /Users/bryandoyle/Library/Logs/VMware Fusion/vmware-vmfusion.log

Nov 17 15:29:27.739: vmfusion| Msg_Reset:

Nov 17 15:29:27.739: vmfusion| http://msg.dictionary.load.statFailed Unable to get information about file "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg": No such file or directory.

Nov 17 15:29:27.739: vmfusion| -


Nov 17 15:29:27.739: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg".

Nov 17 15:29:28.265: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Nov 17 15:29:28.479: vmfusion| Msg_Reset:

Nov 17 15:29:28.479: vmfusion| http://msg.dictionary.load.statFailed Unable to get information about file "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg": No such file or directory.

Nov 17 15:29:28.479: vmfusion| -


Nov 17 15:29:28.479: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg".

Nov 17 15:29:28.509: vmfusion| XXXMACOS: Implement HostDeviceInfo_FindHostSoundDevices

Nov 17 15:29:28.515: vmfusion| Could not open /proc/net/dev

Nov 17 15:29:28.515: vmfusion| SGMAC: XXX: SGHostEnumerate not yet implemented

Nov 17 15:29:28.541: vmfusion| SMBIOS: can't open /dev/mem: Could not find the file

Nov 17 15:29:28.541: vmfusion| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.

Nov 17 15:29:28.542: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Nov 17 15:29:28.542: vmfusion| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

Nov 17 15:29:28.542: vmfusion| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Nov 17 15:29:28.998: vmfusion| Foundry Init: setting up global state (0 threads)

Nov 17 15:29:29.001: vmfusion| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x203

Nov 17 15:29:29.621: | UUID: Unable to open /dev/mem: No such file or directory

Nov 17 15:29:29.623: | Reloading config state: /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Nov 17 15:29:30.293: vmfusion| readlink /var/run/vmware/0b2b7f6addd260c9ae73251be15b6f24: No such file or directory

Nov 17 15:29:30.299: vmfusion| readlink /var/run/vmware/%2fUsers%2fbryandoyle%2fDocuments%2fVirtual%20Machines%2elocalized%2fWindows%20XP%20Professional%2evmwarevm%2fWindows%20XP%20Professional%2evmx: No such file or directory

Nov 17 15:29:31.149: vmfusion| DUMPER: restoring checkpoint version 8

Nov 17 15:29:31.911: vmfusion| VMHSVMCbPower: Setting state of VM /vm/#53d41d2ec60feee0/ to resume with option soft

Nov 17 15:29:31.911: vmfusion| Cmd /vm/#53d41d2ec60feee0/cmd/##8c/op/resume/ failed: A power operation is already in progress

Nov 17 15:29:31.957: vmfusion| VMHS: Exec()'ing /Library/Application Support/VMware Fusion/vmx/Contents/MacOS/vmware-vmx, /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Nov 17 15:29:33.101: vmfusion| Mounting virtual machine paths on connection: /db/connection/#8f/, /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Nov 17 15:29:33.719: vmfusion| Mount VM completion for vm: /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Nov 17 15:29:33.720: vmfusion| Mount VM Complete: /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx, Return code: OK

Nov 17 15:29:39.682: vmfusion| VMX status has been set for vm: /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Nov 17 15:30:31.749: vmfusion| Disconnect check in progress: /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Nov 17 15:30:31.750: vmfusion| Disconnect check in progress: /Users/bryandoyle/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

0 Kudos
Immortal
Immortal

When I have problems involving upgrades, my first instinct is to do an uninstall and then a clean reinstall. In Fusion's case, it's pretty easy, because uninstalling Fusion does not affect your virtual machines. They will be left unmodified, ready to use again when you reinstall.

Fusion's uninstaller is in the .dmg file that contains its installer.

When uninstalling or reinstalling, make sure that you have only one Fusion .dmg mounted at a time. Some people (me included!) have encountered problems related to having both a beta .dmg and a released .dmg mounted at the same time during an install or an uninstall.

View solution in original post

0 Kudos