The flop: I was running a linux VM under VMware Fusion 3 on my Mac OS X Snow Leopard laptop. The VM was located on an external hard drive. The laptop battery died and the system went down.
The turn: After plugging in the AC adapter and starting up the laptop (WITHOUT the external hard drive plugged in). Fusion complained about the missing VM file(s), so I closed the VM and Fusion. I then reinserted the external hard drive and tried to start the VM. Fusion froze for a couple minutes, then I got an 'internal error' from Fusion. So I closed Fusion and tried again – same thing. Then I restarted the laptop – same thing. Then I tried starting a different VM (located on my laptop's HD) and Fusion froze for a bit and then said "The connection timed out." I rebooted and tried starting a local VM again – same thing. So now I can't start ANY VMs…
The river: After hopelessly searching the Internet for solutions, I decided to upgrade to Fusion 4, to see if that would solve my problem. Turns out I can't even do that. When I try using the 'Upgrade from v3 to v4' option in the DMG, I get an error message: "A virtual machine is running with an older version of VMware Fusion." Despite the fact that VMware Fusion is NOT running, nor are any VMs (verified by running 'vmrun list' from CLI).
So…what to do, what to do. Any suggestions?
Best Answer
Fusion uses lock files to prevent multiple processes from modifying the same files at the same time, as could happen if you tried to run to copies of Fusion (say version 3 and version 4) at once. When Fusion quit abnormally, as it did when your laptop battery died, it left behind the lock files and you need to clean them up manually.
See this support article for how to clean up Fusion lock files. If that doesn't solve it, do a Spotlight search including system files for files whose names end in
.lckand if they look like they belong to Fusion, delete them.