Fusion 11.5.7 Could not open /dev/vmmon: Broken pipe

[batti_74]

Hello All, Im new to Fusion. I downloaded a trial to test but having trouble installing. Fusion v11.5.7 on Mac os 10.14.6

Error: Could not open /dev/vmmon: Broken pipe: 

Please make sure that the kernel module `vmmon' is loaded.

Any help support, i need to make it run before purchase.

Thanks

I Tried to load vmmon kext manually but i got 

failed to load - (libkern/kext) not loadable (reason unspecified); check the system/kernel logs for errors or try kextutil(8).

[scott28tt]

@batti_74 

Did you try searching this area of VMTN for "vmmon" or "broken pipe"? You should find similar threads with workarounds or solutions.

[batti_74 · Accepted solution]

Thanks, nothing seemed to work for me but finally issue solved by:

• Rebooted and run csrutil disable under Command+R terminal

[DVCa]

I have the same problem on a Mac with OS Catalina @ Fusion 11. It has worked for several years but has just developed this problem. Non of the suggested fixes have worked. VMware support will not help, even if I pay, unless I upgrade to Fusion 13, which I cannot do as my Mac has a 2012 chipset. I have tried Catalina @ Fusion 11 on a separate HD, which makes no difference. Has anyone found a solution to this issue?

[Technogeezer]

This error has several causes, but we can quickly see if you’re experiencing what appears to be a frequently occurring cause for this.

Can you post the vmware.log file found in the VM’s bundle, and also the output of the following command executed in the Terminal app:

ls -ald /tmp /private/tmp

[DVCa]

Can you advise where I would find the VMware bundle please?

The following is the result of the terminal command

drwxrwxrwt  7 root  wheel  224 10 Jan 16:16 /private/tmp

lrwxr-xr-x@ 1 root  admin   11 18 Dec  2019 /tmp -> private/tmp

[Technogeezer]

Thanks for posting the output of the commands. They appear correct and rules out the "common" issue that generates that error message.

The vmware.log file can be found as follows:

• In Fusion's Virtual Machine Library, right click on the VM in the left hand panel, and select "Show in Finder". A Finder window will open for the folder containing the virtual machine.
• Locate the virtual machine, and right click on that. Select "Show package contents".
• The Finder window will then show all of the files that make up the virtual machine.

Attach a copy of both vmware.log and mksSandbox.log files.

Close the Finder window when finished.

. 

[DVCa]

Can you please tell me where I will find the library? I can't find any sign of it in either the Fusion 11 programme or the Mac finder

[Technogeezer]

The window that normally appears with all of your virtual machines showing on it when you first start Fusion is the Virtual Machine Library. If it doesn't appear, then from the Fusion menu bar, select Window -> Virtual Machine Library. Or type shift-command-L as a keyboard shortcut.

[DVCa]

This is the log file. There is no sandbox file shown. Hope this helps.

Powering off.
2023-01-08T13:30:43.358Z| vmx| I005: Policy_SavePolicyFile: invalid arguments to function.
2023-01-08T13:30:43.358Z| vmx| I005: PolicyVMX_Exit: Could not write out policies: 15.
2023-01-08T13:30:43.359Z| vmx| I005: WORKER: asyncOps=2364431 maxActiveOps=9 maxPending=7 maxCompleted=8
2023-01-08T13:30:43.644Z| vmx| I005: Vix: [mainDispatch.c:4200]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2023-01-08T13:30:43.644Z| vmx| I005: Vix: [mainDispatch.c:4218]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
2023-01-08T13:30:43.646Z| vmx| A000: ConfigDB: Setting cleanShutdown = "TRUE"
2023-01-08T13:30:43.647Z| vmx| I005: Vix: [mainDispatch.c:4200]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2023-01-08T13:30:43.647Z| vmx| I005: Vix: [mainDispatch.c:4218]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.
2023-01-08T13:30:43.648Z| vmx| I005: Transitioned vmx/execState/val to poweredOff
2023-01-08T13:30:43.648Z| vmx| I005: VMX idle exit
2023-01-08T13:30:43.648Z| vmx| I005: WQPoolFreePoll : pollIx = 3, signalHandle = 27
2023-01-08T13:30:43.649Z| vmx| I005: Services_Exit: Closed the services.
2023-01-08T13:30:43.652Z| vmx| I005: Vix: [mainDispatch.c:815]: VMAutomation_LateShutdown()
2023-01-08T13:30:43.652Z| vmx| I005: Vix: [mainDispatch.c:770]: VMAutomationCloseListenerSocket. Closing listener socket.
2023-01-08T13:30:43.654Z| vmx| I005: Flushing VMX VMDB connections
2023-01-08T13:30:43.654Z| vmx| I005: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2023-01-08T13:30:43.654Z| vmx| I005: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
2023-01-08T13:30:43.655Z| vmx| I005: VigorTransport_ServerDestroy: server destroyed.
2023-01-08T13:30:43.655Z| vmx| I005: WQPoolFreePoll : pollIx = 2, signalHandle = 14
2023-01-08T13:30:43.655Z| vmx| I005: WQPoolFreePoll : pollIx = 1, signalHandle = 17
2023-01-08T13:30:43.685Z| vmx| I005: VMX exit (0).
2023-01-08T13:30:43.686Z| vmx| I005: OBJLIB-LIB: ObjLib cleanup done.
2023-01-08T13:30:43.686Z| vmx| I005: AIOMGR-S : stat o=2 r=18 w=1 i=0 br=57840 bw=128

[Technogeezer]

What you've cut and pasted into your reply is incomplete - its the very end of the file and we need to see the entire file. Please attach the entire file by dragging and dropping it in the area noted below where you're typing a reply. . 

[DVCa]

It seems that I cannot attach a file larger than 10,000 characters

[DVCa]

Hopefully I have managed to send this to you as an attachment.

[DVCa]

As well as the vmware.log file that I have attached previously, there are also vmware-0.log, vmware-1.log and vmware-2.log files. Are these relevant to the problem?

Thanks for your help with this.

[Technogeezer]

The attachments came over fine. I’m looking over them but I’m not seeing anything that’s giving me a clue yet. I’ll keep looking. 

The -0.log, -1.log and -.2.logs are from prior attempts to run the VM. Unless the VM was successfully run on one of those 3 prior attempts (using the last modified time on the files and your memory of when it last worked) they won’t be of interest. However if there’s one where it did work, it might be interesting to compare the log where it did work to what you’re seeing now. 

[DVCa]

No, unfortunately none of the previous attempts worked.

VMware does fire up on its own, it's only when it tries to load the virtual machine that it fails.

I have tried installing the OS onto a separate hard drive, then transferring everything across to that - effectively treating that as a new machine but operating from that is exactly the same.

[ColoradoMarmot]

Couple of other questions:

1) Installing and running Fusion as an administrator account?

2) Case-insensitive file system?

3) Using any corporate MDM tools like JAMF, crowdstrike, etc?

4) Ever set a root password?

5) Used any third party 'optimization tools' like Onyx, CCleaner, etc?

[Technogeezer]

I just remembered something that you might want to check.

There was a similar problem reported and the root cause of that was improper permissions on the /private/var/db/KernelExtensionManagement folder

See the reply in this thread from jameslodberg:

https://communities.vmware.com/t5/VMware-Fusion-Discussions/VM-s-not-working-in-Fusion/m-p/2816692/h...

[DVCa]

On your first post, the only one that applies is that i did run CCleaner prior to this problem arising.

Unfortunately I'll be away for a few days, but I will respond as soon as I get back.

Thanks for persevering with this.