VMWARE Fusion 8.5.3 locks up every day

[bjenkinsvm]

Running El Capitan 10.11.6 on a 2015 Macbook Pro laptop (Retina display, mid-2015) with VMWare Fusion 8.5.3.  Prior to running the Fusion 8.5 series I could leave my laptop running constantly with the VM running 24/7 and it never misbehaved.  Now, once a day, usually after leaving it sit overnight it will freeze up and I have to Force Quit the Fusion application.  Looking in the logs, I see the following:

~/Library/logs/VMware Fusion/vmware-vmfusion.log (filtered by the string "error")

2017-01-12T09:35:23.489-05:00| VMware Fusion| I125: SOCKET connect failed, error 2: No such file or directory

2017-01-12T09:35:23.490-05:00| VMware Fusion| I125: SOCKET connect failed, error 2: No such file or directory

2017-01-12T09:35:23.502-05:00| VMware Fusion| I125: SOCKET connect failed, error 2: No such file or directory

2017-01-12T09:35:23.809-05:00| VMware Fusion| E110: CDS error: No install keys defined for fusion-mas

2017-01-12T09:35:23.809-05:00| VMware Fusion| I125: RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product fusion-mas

2017-01-12T09:35:23.810-05:00| VMware Fusion| E110: CDS error: No install keys defined for fusion-mas

2017-01-12T09:35:23.810-05:00| VMware Fusion| I125: RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product fusion-mas

2017-01-12T09:36:09.740-05:00| VMware Fusion| W115: SOCKET failed to create socket, error 47: Address family not supported by protocol family

2017-01-12T09:36:09.889-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.664-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.687-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.702-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.703-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.704-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.704-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.705-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:16.773-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:22.206-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:22.206-05:00| VMware Fusion| W115: Failed to get guest app info hash: Internal error

2017-01-12T09:36:22.218-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-01-12T09:36:33.758-05:00| VMware Fusion| E110: CDS error: No description for bulletin 125c9fb6-2ed2-47aa-b422-7692889c6cf1

2017-01-12T09:36:34.299-05:00| VMware Fusion| E110: CDS error: Bulletin file /var/folders/38/x1ff8bgj3v9d_mmjb54x7jvw0000gn/T/cdstmp_536_0 version 3.2.0 is not valid (min: 3.5.0, max: 3.5.0)

2017-01-12T09:36:34.581-05:00| VMware Fusion| E110: CDS error: Bulletin file /var/folders/38/x1ff8bgj3v9d_mmjb54x7jvw0000gn/T/cdstmp_536_0 version 3.2.0 is not valid (min: 3.5.0, max: 3.5.0)

2017-01-12T09:36:35.153-05:00| VMware Fusion| E110: CDS error: Bulletin file /var/folders/38/x1ff8bgj3v9d_mmjb54x7jvw0000gn/T/cdstmp_536_0 version 3.2.0 is not valid (min: 3.5.0, max: 3.5.0)

2017-01-12T09:36:35.451-05:00| VMware Fusion| E110: CDS error: Bulletin file /var/folders/38/x1ff8bgj3v9d_mmjb54x7jvw0000gn/T/cdstmp_536_0 version 3.2.0 is not valid (min: 3.5.0, max: 3.5.0)

2017-01-12T09:36:35.655-05:00| VMware Fusion| E110: CDS error: Bulletin file /var/folders/38/x1ff8bgj3v9d_mmjb54x7jvw0000gn/T/cdstmp_536_0 version 3.2.0 is not valid (min: 3.5.0, max: 3.5.0)

2017-01-12T09:36:35.926-05:00| VMware Fusion| E110: CDS error: Bulletin file /var/folders/38/x1ff8bgj3v9d_mmjb54x7jvw0000gn/T/cdstmp_536_0 version 3.2.0 is not valid (min: 3.5.0, max: 3.5.0)

2017-01-12T09:36:35.973-05:00| VMware Fusion| E110: CDS error: Bulletin file /var/folders/38/x1ff8bgj3v9d_mmjb54x7jvw0000gn/T/cdstmp_536_0 version 3.2.0 is not valid (min: 3.5.0, max: 3.5.0)

2017-01-12T09:36:36.237-05:00| VMware Fusion| E110: CDS error: No install keys defined for fusion-mas

2017-01-12T09:36:36.237-05:00| VMware Fusion| I125: RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product fusion-mas

[wila]

Hi,

There are a number of reports on Sleep/wake errors in the forums. There have been workarounds proposed, but never really a fix as VMware hasn't been able to reproduce the issue.

In regards to your error from the log.

CDS errors -> that has to do with VMware Fusion trying to download the latest versions of VMware Tools or finding the latest update.

Under preferences you can disable "automatically check for updates". That should at least get rid of those errors in the logs.

Not sure if it will help with the actual issue.

Somebody else today posted that he had similar issues until he did a SMC and PRAM reset.

--

Wil

[mdawson69]

I am also running Fusion 8.5.3 in Mac OS X 10.11.6 on an iMac 5K Retina (late-2014) and have been experiencing issues with VM lockup. Note I run Fusion in Unity mode due to my workflow. I started noticing issues at some point in mid-December—I do not recall when I ran the last Fusion update—but the problem seems to be specifically linked to 8.5.3, which became available at the end of November 2016. I typically update Fusion when updates become available, so I would have done the previous 8.5 updates that began in September and I know I did not have this particular issue until December; previously, there was just the near-daily “Fusion unexpectedly quit” issue each morning, but that matter was more of a nuisance and restarting Fusion put me back to where I left off in my VMs.

The new issue initially manifested as slow file I/O in Canvas X 16 in my Windows 7 Ultimate VM with CVX files opening very slowly. Other Windows software in the Win7 VM were operating normally and my Windows 8.1 VM seemed to be unaffected. During the last week of December Canvas X became intermittently non-responsive with menus opening blank or dialog windows rendering black if not the entire Canvas window whiting out. Also, Fusion would slow to a crawl resulting in me getting the spinning beachball. Initially, the beachball would only be present when the cursor was over VM windows, but eventually OS X would slowdown and become non-responsive; I could not even invoke the Force Quit dialog and would need to do a hard shutdown. This issue continued when I returned to work after the New Year weekend and after the final shutdown my iMac would no longer boot. After spending nearly two hours on the phone with Applecare, I had to wipe my hard drive and re-install OS X because the hard drive had somehow become encrypted.

After spending a week rebuilding both of my VMs, everything seemed to be OK initially, but now the same issue is occurring again, but it now afflicts both VMs. In my last attempt to use Fusion this morning, I switched my Win7 VM to full screen mode and opened Canvas and everything seemed to work fine. When I opened my Win8 VM to examine an Excel workbook I was doing VBA development on, the VBA app I built began having the screen rendering options; the app windows rendered all black and the VM became non-repsonsive. Eventually, Fusion crashed and I sent a crash report. I looked for the log file in the path you cited, but my /Library/Logs/VMware Fusion folder there are only numbered files named “vmware-usbarb-nnnnn.log”.

[mdawson69]

Update. I updated Mac OS X El Capitan (10.11.6) to macOS Sierra (10.12.2) and the VMs seem to be working as expected. I will repost if anything goes wrong.