vm(s) continuously crash on VMware Fusion Pro 10.1.1 (7520154) on macOS 10.13.3

[AkronX]

I'm not more able to use vm(s) on VMware Fusion Pro 10.1.1 (7520154) on my new macOS 10.13.3 iMac 27" 5K 2017. Also I'm not able to create a new macOS vm with High Sierra 10.13.2 App Store installer.

Someone experience same issues?

[ColoradoMarmot]

Have you tried removing and reinstalling Fusion?  Make sure you do it from an administrator (not regular user) account.

[bluefirestorm]

In case you allocated the macOS VM with more than 2 processors, try reducing it to 2. You might be facing the same problem as other people in this other thread Kernel panic in OSX guest on Fusion 10.0.1 when configured for 3 or more CPU's

[AkronX]

Yes, completely uninstalled (also cleaning all the Library folders) and reinstalled. Same issue..

[AkronX]

The VM is configured with 2 core.. I think Fusion 10 has still some issue

[zhus]

Hi AkronX,

Could you attach any logs which would be helpful? Or the support bundle, if it's convenient. 

To get the support bundle, select Help -> Collect Support Information on Fusion menu.

​Thanks.

[AkronX]

Hi zhus,

I've fonund what is causing all this troubles to the VMs: it is a USB device attached to my machine that, even if I uninstall both USB and Audio controller on the VM, it still crash. The only way to let all my VM works is unplug the device or power it off. That happens both with my iMac 5K 2017 and my MacBook Pro 2017

The device is a Naim DAC V-1 (audio Dac) that mount an OEM Audiophilleo USB chip on board. The VMware support team is investigating in this issue.

[mjazz]

I actually have the same since 10.13. I have a Naim DAC V1, the support told me that VM-Ware does not support USB 3.1 from my 2018 Mac Mini. Although the Naim is USB 2.0 and is detected as sound device, Fusion tries to connect is as keyboard.

I now have Fusion 11.5.0 installed and still have the same problem.

> The external sound card 'Naim DAC-V1' is getting detected as a keyboard, which is causing a Kernel panic leading to the Fusion crash.

2018-12-17T22:02:56.363+01:00| keyboard| I125: MKS MacOSKeyboard: Adding device: VID:279A PID:0001 Naim Audiophilleo (Naim DAC-V1. Audiophilleo.com)

2018-12-17T22:02:57.566+01:00| vmx| I125: HDAudio: HDAudioDefaultBackingDeviceChangedCb: Received request to change default sound backing device.

2018-12-17T22:02:57.566+01:00| vmx| I125: SoundUtilMacos_ExtractAudioDeviceStr: Sound input device: BuiltInSpeakerDevice.

2018-12-17T22:02:57.566+01:00| vmx| I125: SoundUtilMacos_ExtractAudioDeviceStr: Sound output device: AppleUSBAudioEngine:Naim Audiophilleo:Naim DAC-V1. Audiophilleo.com: 00000:2.

2018-12-17T22:02:57.566+01:00| vmx| I125: SoundUtilMacos_ExtractAudioDeviceStr: Sound input device: BuiltInSpeakerDevice.

2018-12-17T22:02:57.566+01:00| vmx| I125: SoundUtilMacos_ExtractAudioDeviceStr: Sound output device: AppleUSBAudioEngine:Naim Audiophilleo:Naim DAC-V1. Audiophilleo.com: 00000:2.

2018-12-17T22:03:08.391+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

2018-12-17T22:03:08.391+01:00| vmx| I125: Tools: [AppStatus] Last heartbeat value 351 (last received 5s ago)

2018-12-17T22:03:11.921+01:00| mouse| I125: MKS MacOSMouse: Detected window server coalescing input, disabling constraining

2018-12-17T22:03:17.557+01:00| mouse| W115: Poll timeout: Something may be hung... ungrabbing

2018-12-17T22:03:17.824+01:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2018-12-17T22:03:22.635+01:00| mks| E105: PANIC: MKS MacOSKeyboard: Keyboard thread failed to respond to ungrab request

Is there any news on this? This is already one year ago and they promised to fix it. The device is connected to a USB 3.0 hub.

[AkronX]

I actually have the same since 10.13. I have a Naim DAC V1, the support told me that VM-Ware does not support USB 3.1 from my 2018 Mac Mini. Although the Naim is USB 2.0 and is detected as sound device, Fusion tries to connect is as keyboard.

I now have Fusion 11.5.0 installed and still have the same problem.

Hi,

A workaround for this annoying issue is following the instruction of this KB article:

https://kb.vmware.com/s/article/52589

That is:

1. Quit Fusion;

2. Create a file and name it as "config", make sure the file has no extension name;

3. Add this line to the config file:

   mks.keyboard.setHostLEDs="FALSE"

4. Copy the config file to ~/Library/Preferences/VMware Fusion/ folder

I've tested and it is working also on VMware Fusion 11.5.0 (14634996): no more VM crash with Naim DAC V1 connected and powered-on.

[mjazz]

Hi AkronX

Perfect! This really helps me Thank you very much!

Menno