Fusion 10 on 10.12 won't start any virtual machine

[ckater]

I just upgraded to Fusion 10 (from Fusion 8.5.8) and I'm still on Sierra, preparing my upgrade to High Sierra.

But: After migration the virtual machines to the corresponding internal Version (14) I'm still not able to launch them. They are all stuck with an "internal error in the virtual machine" (sorry, no exact translation as I'm using the German version). Basically, after a normal start of a machine, I run into an error saying the machine can't be launched.

I even tried to install a new machine, but the error is happening too - right before the very first start (not Windows setup at this point). It seems as if Fusion 10 isn't able to launch any virtual machine, even complete new ones.

Anyone having this problems too?

[turnbull]

I was told by VMWare support to do this:

Thank you for contacting VMware Desktop Services.

Please follow the below mentioned steps which should fix the issue:

- Go to Apple System Preferences > Security & Privacy > General

- Select 'Allow'

- Start VMware Fusion

I had already done it, but it didn;t work. Your Mileage may vary.

VMWare closed the ticket anyway (I've re-opened). This product is clearly not production ready.

[RickShu]

Hi turnbull,

Would you please try with the following steps and see if it helps:

1) Manually removed Fusion completely and then executed the below commands in Terminal window on Mac Host:

     xattr -l ~/Downloads/VMware-Fusion-10.0.0-6665085.dmg

     xattr -dr com.apple.quarantine ~/Downloads/VMware-Fusion-10.0.0-6665085.dmg

2) Reinstalled VMware Fusion from the dmg

Sorry for any inconveniences,

Regards,

-Rick

[turnbull]

This worked. Thanks very much!

[Mikero]

Hi everyone,

We recognize the issue here and have a patch planned for release tomorrow.

I apologize to everyone who's been affected by this issue, we both expect better from us, so I'm glad our team could rally so quickly to issue a fix.

[dietrich_on_vmw]

Hi Michael,

thanks for the quick solution. Will this patch show up as a new release if I run "check for updates..."?

Or do we have to get it somewhere else?

regards

Dietrich

[RefriedNoodle]

I seem to have the same issue, with Fusion 10.0 on MacOS 10.12.6 (Dutch locale) on 15" rMBP 2016.

Fusion asked to upgrade the VM hardware to version 14, and after that, refused to boot it. I reverted to an earlier snapshot which I luckily had (which apparently reverts the VM hardware version as well), and it boots. Upgrading to 14 gave the error again.

I haven't tried the solutions mentioned above yet. I'll keep it running on VM hardware version 12 for now. Can't afford to lose my VMs right now.

[Neurolept]

Hi everyone,

I have same problem.

MacOS 10.13 (17A365) French

Fusion 10.0.0-6665085

Hardware : MBP Retina 2015, MBP 2016, IMAC 2017

Waiting for new version or patch

[iFrodo75]

The issue is now fixed with Fusion 10.0.1 which not yet offered as software update but can be downloaded from VMWare web site directly.

[Zongmin]

Hi ckater,

Thank you for using Fusion10 and report this issue. I'm really sorry for the inconvenience this issue have brought to your!

We just released a Fusion10.0.1 which this issue should have been fixed. Refer to https://rna.vmware.com/document/preview/html?documentId=725#Resolved Issues. Pls try and see whether your issue got fixed.

Thank you!

[RefriedNoodle]

Team,

Thank you, 10.0.1 seems to fix it for me. I upgraded my VMs to 14, and they boot. Going to upgrade macOS to HS tonight. Thank you for your efforts!

[mkummer]

Good morning: thanks - patch works for me too.

[gabhau]

Hi,

Fusion Version 10.0.1 Solved the issue of non starting VMs for me too. Thanks!

/ Gabriel

[SvenGus]

Problem solved with Fusion 10.0.1 also for my MacBook Pro (Retina, 15-inch, Late 2013): shut down my Windows and Linux VMs (the problem is not present for macOS VMs, as they are not graphically accelerated), removed the mks.enableMTLRenderer = "0" line from the respective ​.vmx​ configuration files, and all now works as expected...

[Neurolept]

Thanks - patch works for me too with 3D Accelrator

[Miek1967]

Windows 10 Virtual machine now boots with 3D acceleration, but after the installation of VMWare tools the mouse-integration doesn't seem to work. At the loggin screen it works as it always have but as soon as I activate the password field the mouse integration stops and it won't work in Windows 10... It did work before the update of Fusion to 10..0.1. and the VMWare tools service is running, and the version is 10.1.15 build 6627299.

UPDATE: I went back 10.0.0 (did the workaround with adding a line to the .vmx file) and re-installed VMWare Tools and now everything works as expected and the mouse integration between macOS and Windows is working again

UPDATE 2: The problem only appears to be when I'm using an External display connected via Thunderbolt 3 port on my Macbook 15" 2016 and the internal display is not used as soon as I opened the Macbook and used both the internal and externa display the mouse integration works as it should.

[NecrolyteDT]

Very good 10.0.1 fixed this issue for me

[DougBirdwell]

I upgraded this evening (10/8/17) to Fusion 10.0.1 Pro (VMware-Fusion-10.0.1-6754183) and am seeing the same problem: "internal error" when I attempt to boot a VM image.  So no, I'm guessing that at least for some users 10.0.1 didn't fix the problem.  System info:

Macbook Pro 13" (Retina, early 2015)

Mac OS X 10.12.6

3.1GHz i7

16GB RAM

Intel Iris Graphics 6100 1536 MB graphics

[DougBirdwell]

For others who have encountered this issue, I submitted a support request and received the following information.  This procedure fixed the problem.

Thanks again for the VMware support team's rapid response!

From VMware support:

Please follow these steps in given sequence :

1. Uninstall VMware Fusion 10   [My note: Look on the web for VMware's instructions on how to do this; it involves more than deleting the application file.]

2. Download a fresh copy of VMware Fusion 10 make sure the dmg is not mounted. If this dmg is automounted then these won’t work.

3. Open Terminal on the Mac host

4. Run the below command

               xattr -l ~/Downloads/VMware-Fusion-10.0.dmg

5. You will see this output

com.apple.lastuseddate#PS:

00000000  42 16 CC 59 00 00 00 00 A2 DC 9B 27 00 00 00 00  |B..Y.......'....|

00000010

com.apple.metadata:kMDItemDownloadedDate:

00000000  62 70 6C 69 73 74 30 30 A1 01 33 41 BF 7C 4D C2  |bplist00..3A.|M.|

00000010  AD B9 52 08 0A 00 00 00 00 00 00 01 01 00 00 00  |..R.............|

00000020  00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00  |................|

00000030  00 00 00 00 13                                   |.....|

00000035

com.apple.metadata:kMDItemWhereFroms:

00000000  62 70 6C 69 73 74 30 30 A2 01 02 5F 11 02 89 68  |bplist00..._...h|

00000310  00 00 00 00 00 00 00 00 00 02 F5                 |...........|

0000031b

com.apple.quarantine: 0083;59cc1642;Safari;47AAAF78-0967-4C60-B35F-DB1A7B2100CC

6. Run the below command to remove the quarantine

               xattr -dr com.apple.quarantine ~/Downloads/VMware-Fusion-10.0.dmg

7. Run the same command in step 4, now you should not see the last line com.apple.quarantine

8. Install Fusion using the same dmg

[arkaina]

For others running Sierra 10.12 and VMWare Fusion 10.0.1 that have tried all of the prior suggestions and still getting the "internal error" when trying to resume any VM, the following worked for me.   

I tried everything and spent countless hours trying to sort this out. The simple solution was to download OnyX and click "verify/repair permissions" under the "maintenance" section, reboot and you're good to go.   Apple's disk utility "first aid" option could not sort this out - I wonder what other useful functionality apple will remove next.  The vmware logs had no mention of anything permission related.

My error logs looked like this:

2017-10-25T17:05:13.060-05:00| VMware Fusion| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-10-25T17:05:13.068-05:00| VMware Fusion| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-10-25T17:05:13.091-05:00| VMware Fusion| I125: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

2017-10-25T17:05:13.092-05:00| VMware Fusion| I125: DISKLIB-DSCPTR: Unrecognized ddb entry. ID='isNativeSnapshot' Val='no'

2017-10-25T17:05:13.869-05:00| VMware Fusion| I125: VMServiceUser successfully opened service: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services

2017-10-25T17:05:13.869-05:00| VMware Fusion| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-10-25T17:05:13.872-05:00| VMware Fusion| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-10-25T17:05:13.921-05:00| VMware Fusion| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-10-25T17:05:14.815-05:00| VMware Fusion| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-10-25T17:05:14.967-05:00| VMware Fusion| I125: DISKLIB-DSCPTR: Unrecognized ddb entry. ID='isNativeSnapshot' Val='no'

2017-10-25T17:05:14.968-05:00| VMware Fusion| I125: DISKLIB-DSCPTR: Unrecognized ddb entry. ID='isNativeSnapshot' Val='no'

2017-10-25T17:05:14.969-05:00| VMware Fusion| I125: VMHSVMCbPower: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx, Setting state of VM to resume with option soft

2017-10-25T17:05:14.969-05:00| VMware Fusion| I125: Found vmx as /Applications/VMware Fusion.app/Contents/Library/vmware-vmx

2017-10-25T17:05:14.970-05:00| VMware Fusion| I125: Starting vmx as /Applications/VMware Fusion.app/Contents/Library/vmware-vmx

2017-10-25T17:05:14.970-05:00| VMware Fusion| I125: VigorExecVMXExCommon: VM /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx in directory /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm

2017-10-25T17:05:14.970-05:00| VMware Fusion| I125: VigorExecVMXExCommon: Exec()'ing /Applications/VMware Fusion.app/Contents/Library/vmware-vmx /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx.

2017-10-25T17:05:15.065-05:00| VMware Fusion| I125: VmdbAddConnection: cnxPath=/db/connection/#17/, cnxIx=1

2017-10-25T17:05:15.066-05:00| VMware Fusion| I125: Vmdb_AddConnectionAsync_Secure: registered VERSION completion callback, cnx = /db/connection/#17/

2017-10-25T17:05:15.068-05:00| VMware Fusion| I125: OnGuestCanRunUnityChanged: The guest is a supported version of Windows, checking Tools status. Version status: 5, running status: 3

2017-10-25T17:05:15.068-05:00| VMware Fusion| I125: OnGuestCanRunUnityChanged: Tools status is not INSTALLED

2017-10-25T17:05:15.069-05:00| VMware Fusion| I125: OnVMStateChanged: alive = 1

2017-10-25T17:05:15.156-05:00| VMware Fusion| I125: VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF (remote disconnect)

2017-10-25T17:05:15.156-05:00| VMware Fusion| I125: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#17/' (-32)

2017-10-25T17:05:15.156-05:00| VMware Fusion| I125: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx: VMX did not report err via stderr

2017-10-25T17:05:15.156-05:00| VMware Fusion| I125: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#17/'

2017-10-25T17:05:15.157-05:00| VMware Fusion| I125: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx: Pending power op found, completing.

2017-10-25T17:05:15.158-05:00| VMware Fusion| I125: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx: Clearing execReqPath

2017-10-25T17:05:15.158-05:00| VMware Fusion| I125: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx: Reloading config state.

2017-10-25T17:05:15.175-05:00| VMware Fusion| I125: VMHS: Transitioned vmx/execState/val to suspended

2017-10-25T17:05:15.176-05:00| vigorCnx| I125: DISKLIB-DSCPTR: Unrecognized ddb entry. ID='isNativeSnapshot' Val='no'

2017-10-25T17:05:15.177-05:00| vigorCnx| I125: VigorOfflineGetToolsVersion: updated tools version to 282f

2017-10-25T17:05:15.187-05:00| vigorCnx| I125: DUMPER: Restoring checkpoint version 8.

2017-10-25T17:05:15.189-05:00| VMware Fusion| I125: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx: VMHSStartVmxVigorCb: vmPath=/vm/#6f7653904eb3f736/ status=error

2017-10-25T17:05:15.189-05:00| VMware Fusion| I125: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx: VMHSStartVmxVigorCb: error vmdb=-45 msg=Failed to power on '/Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx'.

2017-10-25T17:05:15.189-05:00| VMware Fusion| I125:

2017-10-25T17:05:15.189-05:00| VMware Fusion| I125: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx: Reloading config state.

2017-10-25T17:05:15.204-05:00| VMware Fusion| I125: VMHS: Transitioned vmx/execState/val to suspended

2017-10-25T17:05:15.205-05:00| vigorCnx| I125: DISKLIB-DSCPTR: Unrecognized ddb entry. ID='isNativeSnapshot' Val='no'

2017-10-25T17:05:15.206-05:00| vigorCnx| I125: VigorOfflineGetToolsVersion: updated tools version to 282f

2017-10-25T17:05:15.207-05:00| VMware Fusion| I125: Internal VMDB error: VMDB failure (-1)

2017-10-25T17:05:15.216-05:00| vigorCnx| I125: DUMPER: Restoring checkpoint version 8.

2017-10-25T17:05:15.460-05:00| VMware Fusion| I125: OnGuestCanRunUnityChanged: The guest is a supported version of Windows, checking Tools status. Version status: 5, running status: 3

2017-10-25T17:05:15.460-05:00| VMware Fusion| I125: OnGuestCanRunUnityChanged: Tools status is not INSTALLED

2017-10-25T17:05:15.460-05:00| VMware Fusion| I125: OnVMStateChanged: alive = 0

2017-10-25T17:05:15.461-05:00| VMware Fusion| I125: Setting power state suspended

2017-10-25T17:05:15.463-05:00| VMware Fusion| I125: Vix: [775 foundryVMPowerOps.c:988]: FoundryVMPowerStateChangeCallback: /Volumes/data-mac/Virtual Machines/Windows Server 2016.vmwarevm/Windows Server 2016.vmx, vmx/execState/val = suspended.

2017-10-25T17:05:15.958-05:00| VMware Fusion| I125: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

2017-10-25T17:05:15.959-05:00| VMware Fusion| I125: DISKLIB-DSCPTR: Unrecognized ddb entry. ID='isNativeSnapshot' Val='no'

2017-10-25T17:05:15.977-05:00| VMware Fusion| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

2017-10-25T17:05:16.476-05:00| VMware Fusion| I125: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

2017-10-25T17:05:16.477-05:00| VMware Fusion| I125: DISKLIB-DSCPTR: Unrecognized ddb entry. ID='isNativeSnapshot' Val='no'

2017-10-25T17:05:17.177-05:00| VMware Fusion| I125: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.

and this:

Process:	vmware-vmx [5835]
Path:	/Applications/VMware Fusion.app/Contents/Library/vmware-vmx
Identifier:	vmware-vmx
Version:	10.0.1 (0675.41.83)
Code Type:	X86-64 (Native)
Parent Process:	??? [1]
Responsible:	vmware-vmx [5835]
User ID:	0

Date/Time:	2017-10-25 17:49:01.426 -0400
OS Version:	Mac OS X 10.12.6 (16G29)
Report Version:	12
Anonymous UUID:	30DDC438-1492-8022-5BD6-7E611E2F05C6

Time Awake Since Boot: 10000 seconds

System Integrity Protection: enabled

Crashed Thread:

2  Dispatch queue: com.apple.root.default-qos

Exception Type:	EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:	KERN_INVALID_ADDRESS at 0x00000000000000d8
Exception Note:	EXC_CORPSE_NOTIFY

Termination Signal:	Segmentation fault: 11
Termination Reason:	Namespace SIGNAL, Code 0xb

Terminating Process:   exc handler [0]