Hello Henry,
Welcome at the VMware communities forum.
You might already have tried, but the initial troubleshooting step when this happens is a reboot of the host.
If that isn't helping then another possibility for the error might be antivirus or antimalware interfering.
It doesn't help much bar the "it can work" statement, but down here Fusion 8.5 works fine on macOS Sierra.
--
Wil
I was hopeful that I had found a solution, but apparently not:
I'm concerned about possible data loss. Which is the safest option to choose if that dialog appears?
Thanks.
It's hard to know which parts of the log file might relate to these Internal Error instances. Perhaps this bit?
2016-10-04T11:34:50.539Z| VMware Fusion| I125: OnGuestCanRunUnityChanged: Tools status is not RUNNING
2016-10-04T11:36:38.917Z| VMware Fusion| I125: VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF (remote disconnect)
2016-10-04T11:36:38.918Z| VMware Fusion| I125: Internal VMDB error: Pipe: Read failed (-32)
2016-10-04T11:36:38.922Z| VMware Fusion| I125: VmdbPipeStreamsOvlError: write failed, draining reads
2016-10-04T11:36:38.922Z| VMware Fusion| I125: VmdbPipeStreamsOvlError Couldn't initiate write: (32) Broken pipe.
2016-10-04T11:36:38.922Z| VMware Fusion| I125: VmdbCnxCommitUpdates: pipe lost, pumping recv before unmounting
2016-10-04T11:36:38.922Z| VMware Fusion| I125: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#5a4/' (-26)
2016-10-04T11:36:38.922Z| VMware Fusion| I125: Internal VMDB error: Pipe: Write failed (-31)
2016-10-04T11:36:38.923Z| VMware Fusion| I125: Internal VMDB error: Pipe connection has been broken (-14)
2016-10-04T11:36:38.924Z| VMware Fusion| I125: Internal VMDB error: Pipe connection has been broken (-14)
2016-10-04T11:36:38.925Z| VMware Fusion| I125: Internal VMDB error: Pipe connection has been broken (-14)
2016-10-04T11:36:38.925Z| VMware Fusion| I125: Internal VMDB error: Pipe connection has been broken (-14)
2016-10-04T11:36:38.946Z| VMware Fusion| I125: SOCKET 7 (11) recv detected client closed connection
2016-10-04T11:36:38.946Z| VMware Fusion| I125: Detected automation socket close for VM (/Volumes/V/VMs/Windows 10 x64.vmwarevm/Windows 10 x64.vmx)
2016-10-04T11:36:38.946Z| VMware Fusion| I125: Internal VMDB error: Pipe connection has been broken (-14)
2016-10-04T11:36:38.947Z| VMware Fusion| I125: VigorOnlineCnxDemux: VmdbCnx failed: Lost a connection to the running VMX instance.
2016-10-04T11:36:38.947Z| VMware Fusion| I125+ Transport (VMDB) error -26: Pipe: Would block.
2016-10-04T11:36:38.947Z| VMware Fusion| I125:
2016-10-04T11:36:38.947Z| VMware Fusion| I125: VigorOnlineDisconnect: disconnect /vm/#4996fa36372958a2/ via /db/connection/#5a4/
2016-10-04T11:36:38.947Z| VMware Fusion| I125: /Volumes/V/VMs/Windows 10 x64.vmwarevm/Windows 10 x64.vmx: Unmounting VM begun.
This is the OS version I am running:
| System Version: | macOS 10.12 (16A320) |
| Kernel Version: | Darwin 16.0.0 |
Again, as in the post above, this is the error message:
Thanks.
Hi Botnik,
It is so disheartening to read that removing 8.5.0 and reinstalling the previous version of Fusion doesn't fix the problem.
Be aware that this type of software depends on many factors and that bugs might look like they are the same might end up just being similar in that they show the same symptoms but have different origins on why the problem happens.
To illustrate.
In this thread there's people who have problems because of the particular hardware model having a specific camera.
There's people who report reinstalling 8.5 works and in other threads I read it did not help..
Some here report that removing the usb controller from their VM or changing it from USB3 to USB2 helped.. for others it doesn't work..
So even if the top post mentions that reinstalling 8.1 did not fix it for them, this might in fact work for you.
For the record, if you do want to go down that path then I suggest to reboot your host after uninstall Fusion 8.5 to make sure the kernel modules from Fusion 8.5 are actually unloaded before installing Fusion 8.1.
--
Wil
Hello Thomas_McKane,
Sorry to hear about your problems. VMware certainly is not ignoring you (and BTW, if not clear, I'm not from VMware)
As one of the first respondents in this thread there's Darius, who is a VMware employee.
If you want VMware to actually look at your problem you will need to supply more info as just chiming in with a "me too".
A good start usually is to supply a vmware.log file from the folder of your virtual machine.
An even better help is to supply a complete support bundle.
You can also open a support ticket if you rather handle this directly with VMware.
For your information, the Community Forum is not an official support-forum and is not officially monitored by VMware Support or Product Managers.
This is a community based forum where VMware Fusion users help other users.
As a side note there are VMware employees who keep an eye on the forums and try to help out, but they might not see every post and most - if not all of them - are doing so in their own free time.
To get official support please go to: Fusion Support and open a ticket at File a Support Request
hope this helps,
--
Wil