Transport (VMDB) error-14: Pipe connection has been broken

[chrilarc]

Hello,

After migrating my MacBook from Catalina to Monterey, I can not open my VMs anymore: Transport (VMDB) error-14: Pipe connection has been broken

- MacBook Pro 16 Intel - Monterey 12.2.1

- VMWare Fusion 12.2.1

I tried the following methods stated in the other posts regarding this error and nothing worked.

- sudo kextutil /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext

- go into system preferences, battery, and disable “Automatic Graphics Switching”

- manually edit the .vmx file, modifying the option mks.forceDiscreteGPU="TRUE" to mks.forceDiscreteGPU="FALSE"

- disable 3D accelerator

Thank you for your help.

[Technogeezer]

Manually creating the folder should not be necessary. The default permissions on /private/tmp should have allowed Fusion to create that folder. 

Please run the commands and post the output - I'd like to make sure this doesn't happen to you again.

[GK17]

I have attached the Terminal window after running the commands.  Thank you

[Technogeezer]

@GK17 thanks for the post of the permissions.. 

The permissions on your /private/tmp (linked to from /tmp) are still incorrect. Assuming you are logged in as an administrator account, issue the following command to reset the permissions to the correct value:

sudo chmod 1777 /private/tmp

Then re-issue the following to see that the change "took";

ls -ald /tmp /private/tmp

[GK17]

Spoiler

 You are correct as this morning I got the error again.  I ran those commands - output attached - and I am back in. Thank you.

[rakeshummat10]

I am having the same issue on my Mac pipe line connection is broken with error 14 can you pls hep and tell me how you fix you issue

[brell]

How do I grant VMware access to the microphone?

[brell]

What is SIP?

[brell]

Ok I am also having the dreadful -14 issue.

I have VMware 12.2.5 and I am trying to make it work on my new MacBook pro Apple M2 with MacOS Ventura 13.1

It worked great on my old MB pro.

Someone wrote that this version of VMware does not run on Apple M2 based computers.  Can anyone verify that?

Is there any newer version of VMware that would work?

Thanks

[RDPetruska]

---

@brell wrote:

Ok I am also having the dreadful -14 issue.

I have VMware 12.2.5 and I am trying to make it work on my new MacBook pro Apple M2 with MacOS Ventura 13.1

It worked great on my old MB pro.

Someone wrote that this version of VMware does not run on Apple M2 based computers.  Can anyone verify that?

Is there any newer version of VMware that would work?

Thanks

---

Correct - you need version 13.x to work on Apple Silicon processors.

And, more importantly, NONE of your existing virtual machines will work on your new computer... you can only run ARM-based OS's.

[brell]

Wow!  Do you know whether VM is going to fix this?

What other options do I have?  Will Parallels work with old Mac OSes?

[RDPetruska]

---

@brell wrote:

Wow!  Do you know whether VM is going to fix this?

What other options do I have?  Will Parallels work with old Mac OSes?

---

There's nothing to "fix".  VMware and Parallels are *virtualization* companies - they create a software-based computer framework which exposes the real CPU to the virtual machine.  They are not *emulation* companies - which present a fake CPU to the virtual machine.

[ColoradoMarmot]

To answer your last question, no.  The only thing that remotely does is QEMU (and it doesn't work with MacOS), and performance is so bad that it's unusable.

If you need to run intel guests, keep an intel machine around.  That's doubly true for MacOS - we don't even have a good option for virtualizing Monterey and Ventura yet (the support is rudimentary at best).

You can't modify a diesel engine to run on gasoline!

[Sam__fr]

I had issues running my VMs once upgraded to Monterey from Big Sur on MBPro 13 mid 2012 using OCLP,  all failed starting with the error message "broken pipe -14".

As a few people said around, the issue is the HD4000 GPU embedded with the Intel Ivy Bridge processor, OCLP installs a root patch to support the macOS METAL framework and speeds up UI. 

I was about to downgrade my Monterey 12.6.3 to Big Sur 11.7.4 but I decided as a last try to remove the OCLP post patch for Intel Ivy Bridge and reboot my MBPro.

Once rebooted, OCLP warns you macOS needs to install a root patch to better run your GUI. This is not false as the GUI becomes less smooth than with the patch. BUT it enables to run your VMs again !!!  And once using Windows10  in full screen mode, you don't feel that much the latency. 

I don't use a lot my Windows / VMs, mainly for an accounting software not running under macOS or to do some testing with Windows only software. Once done, I can very easily re-install the root Intel patch from OCLP and reboot the Mac to have a faster GUI under macOS 12.6.3

[bobfesch]

I'm running a test-machine (mid2012 15" MBP9,1) with OCLP_Ventura and also ran into the "Transport (VMDB) error-14: Pipe connection has been broken."

So I upgraded from Fusion12 to Fusion13 without having any success.

After reading Your initial question and description I followed the step, you described and just went into "system preferences/battery, and disabled “Automatic Graphics Switching”
After this, my VMs did launch without any problem.
Installing the app "gfxCardStatus" allows to switch graphics card manually through an icon in the menubar.

Today I read Your posting again. About editing the .vmx file.
The line mks.forceDiscreteGPU="TRUE" was missing in my .vmx files.
After adding that line, the VM did start, even with "Automatic Graphics Switching" was enabled.
(modifying the line to mks.forceDiscreteGPU="FALSE" broke the VM launch)

Thanks for Your inspiration!

[jojo888]

I have same macbook as you. Just upgrade to Ventura and Vmware Fusion 13. Tried all the suggested by you but still has broken pipe error. I need to solve this urgently seems i am conducting training tomorrow...

[Technogeezer]

There are known issues with trying to run Fusion with OCLP. OCLP in its current "production" (and I use the term "production" very loosely) incarnation hacks macOS in a way that breaks Fusion..

The hack that seems to break Fusion and the Apple Hypervisor is the disabling of security checks in the OS (specifically AMFI). @SvenGus indicates in a prior post that you could try OCLP with AMFIPass, which eliminates the previous requirement to disable Library Validation and AMFI, and is currently in beta (will soon be merged into the main OCLP):

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/tag/amfipass-beta-test

[ColoradoMarmot]

The only guaranteed fix for this issue is to downgrade to a support OS/Hardware stack.  Fusion provides no support for unsupported platforms.

[jojo888]

Dear Sir,

Thank you for your feedback. I hope you don't mind if I ask a quick question. Have you had the chance to test this workaround? I'm curious to know if implementing AMFIPass would allow me to run/open my VMware Fusion instance successfully.

I truly appreciate your time and assistance.

Best regards,

[Technogeezer]

---

@jojo888 wrote:

Have you had the chance to test this workaround? I'm curious to know if implementing AMFIPass would allow me to run/open my VMware Fusion instance successfully.

Unfortunately I can’t answer that question as I don’t run Fusion on unsupported configurations. There are some that have reported that AMFIPass has worked for them. You’ll have to try it yourself to see if it works for you. And be prepared to back out if it in the event that it doesn’t.

There is no way that VMware will test this, so you’ll have to rely on your own testing and that of others. 

[SvenGus]

FYI, AMFIPass - with which Fusion works perfectly - is now integrated in the latest OCLP main release:

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/tag/0.6.8