My Linux workstation is old, and has taken up the habit of powering off suddenly. (It'll be diagnosed and fixed.)
I copied a VM that was running when the host powered off, so it has WRITELOCK and READLOCK files.
I tried opening the VM from Fusion to see what happens. The Fusion GUI immediately quits without generating any logfile or other diagnostic information from what I can see. Any previously-running VMs continue to run in the background.
What can I do to provide useful information in this case?
When I remove the READLOCK and WRITELOCK files, the GUI still crashes hard.
Fusion is leaving a .vmx.WRITELOCK file behind.
Try looking for the Fusion GUI log here:
~/Library/Logs/VMware Fusion/vmware-vmfusion.log
Ahh... thank you.
Looks like some assert is failing, but I'm not sure what it means.
Dec 31 14:14:31.531: vmfusion| Log for VMware Fusion pid=547 version=e.x.p build=build-36932 option=BETA
Dec 31 14:14:31.531: vmfusion| Hostname=balthasar.local
Dec 31 14:14:31.531: vmfusion| Using log file /Users/jamesk/Library/Logs/VMware Fusion/vmware-vmfusion.log
Dec 31 14:14:31.674: vmfusion| Failed to acquire super user privileges.
Dec 31 14:14:31.684: vmfusion| Msg_Reset:
Dec 31 14:14:31.684: vmfusion| \[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.
Dec 31 14:14:31.684: vmfusion| \----
Dec 31 14:14:31.684: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg".
Dec 31 14:14:31.691: vmfusion| XXXMACOS: Implement HostDeviceInfo_FindHostSoundDevices
Dec 31 14:14:31.691: vmfusion| XXXMACOS: Implement HostDeviceInfo_FindHostDisks
Dec 31 14:14:31.691: vmfusion| Could not open /proc/net/dev
Dec 31 14:14:31.691: vmfusion| SGMAC: XXX: SGHostEnumerate not yet implemented
Dec 31 14:14:31.692: vmfusion| Failed to acquire super user privileges.
Dec 31 14:14:31.692: vmfusion| SMBIOS: can't open /dev/mem
Dec 31 14:14:31.692: vmfusion| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.
Dec 31 14:14:31.693: vmfusion| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.
Dec 31 14:14:31.693: vmfusion| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.
Dec 31 14:14:31.821: vmfusion| Foundry Init: setting up global state (0 threads)
Dec 31 14:14:31.822: vmfusion| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x3
Dec 31 14:14:31.921: | Reloading config state: /Volumes/150GB External Firewire 400/vmware/dhcp/DHCP Server.vmx
Dec 31 14:14:31.977: vmfusion| readlink /var/run/vmware/0650c72f8c28c6eca60b279f0901e08a: No such file or directory
Dec 31 14:14:31.977: vmfusion| readlink /var/run/vmware/%2fVolumes%2f150GB%20External%20Firewire%20400%2fvmware%2fdhcp%2fDHCP%20Server%2evmx: No such file or directory
Dec 31 14:14:32.258: vmfusion| ASSERT bora/apps/lib/cui/cui.cc:250
Dec 31 14:14:32.258: vmfusion| Backtrace:
Dec 31 14:14:32.259: vmfusion| Backtrace[0] 0xbfffdda8 eip 0x0ad917
Dec 31 14:14:32.259: vmfusion| Backtrace[1] 0xbfffe1c8 eip 0x0aede9
Dec 31 14:14:32.259: vmfusion| Backtrace[2] 0xbfffe1f8 eip 0x031960
Dec 31 14:14:32.259: vmfusion| Backtrace[3] 0xbfffe218 eip 0x19687e
Dec 31 14:14:32.259: vmfusion| Backtrace[4] 0xbfffe438 eip 0x1cd162
Dec 31 14:14:32.259: vmfusion| Backtrace[5] 0xbfffe498 eip 0x4da643
Dec 31 14:14:32.259: vmfusion| Backtrace[6] 0xbfffe618 eip 0x1ab12b
Dec 31 14:14:32.259: vmfusion| Backtrace[7] 0xbfffe688 eip 0x4d9f9f
Dec 31 14:14:32.259: vmfusion| Backtrace[8] 0xbfffe798 eip 0x18ea7d
Dec 31 14:14:32.259: vmfusion| Backtrace[9] 0xbfffe898 eip 0x186e51
Dec 31 14:14:32.259: vmfusion| Backtrace\[10] 0xbfffea78 eip 0x08c4bf
Dec 31 14:14:32.259: vmfusion| Backtrace\[11] 0xbfffea98 eip 0x08c5fc
Dec 31 14:14:32.259: vmfusion| Backtrace\[12] 0xbfffeb18 eip 0x0a1660
Dec 31 14:14:32.259: vmfusion| Backtrace\[13] 0xbfffeb58 eip 0x2f8354
Dec 31 14:14:32.259: vmfusion| Backtrace\[14] 0xbfffebb8 eip 0x9083f3a5
Dec 31 14:14:32.259: vmfusion| Backtrace\[15] 0xbfffebf8 eip 0x9083f11a
Dec 31 14:14:32.259: vmfusion| Backtrace\[16] 0xbffff148 eip 0x90829379
Dec 31 14:14:32.259: vmfusion| Backtrace\[17] 0xbffff188 eip 0x90828eb5
Dec 31 14:14:32.259: vmfusion| Backtrace\[18] 0xbffff1c8 eip 0x92dcdb90
Dec 31 14:14:32.259: vmfusion| Backtrace\[19] 0xbffff238 eip 0x92dcd297
Dec 31 14:14:32.259: vmfusion| Backtrace\[20] 0xbffff258 eip 0x92dcd0ee
Dec 31 14:14:32.259: vmfusion| Backtrace\[21] 0xbffff578 eip 0x9326f465
Dec 31 14:14:32.259: vmfusion| Backtrace\[22] 0xbffff7d8 eip 0x9326f056
Dec 31 14:14:32.259: vmfusion| Backtrace\[23] 0xbffff898 eip 0x93268ddb
Dec 31 14:14:32.259: vmfusion| Backtrace\[24] 0xbffff8d8 eip 0x9325cd2f
Dec 31 14:14:32.259: vmfusion| Backtrace\[25] 0xbffff918 eip 0x002622
Dec 31 14:14:32.259: vmfusion| Backtrace\[26] 0xbffff930 eip 0x00253d
Dec 31 14:14:32.259: vmfusion| Backtrace\[27] 00000000 eip 0x000002
Dec 31 14:14:32.259: vmfusion| Msg_Post: Error
Dec 31 14:14:32.259: vmfusion| \[msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (vmfusion)
Dec 31 14:14:32.259: vmfusion| ASSERT bora/apps/lib/cui/cui.cc:250
Dec 31 14:14:32.259: vmfusion| \[msg.panic.haveLog] A log file is available in "/Users/jamesk/Library/Logs/VMware Fusion/vmware-vmfusion.log". \[msg.panic.requestSupport.withLog] Please request support and include the contents of the log file. \[msg.panic.requestSupport.linux]
Dec 31 14:14:32.259: vmfusion| To collect files to submit to VMware support, run vm-support.
Dec 31 14:14:32.259: vmfusion| \[msg.panic.response] We will respond on the basis of your support entitlement.
Please open a beta support request and include your vmware-vmfusion.log. Thanks!
Happy New Year!
Please open a beta support request and
include your vmware-vmfusion.log.
Done.
>>Thank you for filing support request 348292.