Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Ventura / VMware Fusion: "Error (VMDB) -14: Pipe connection has been broken"
- Thread starter bobesch
- Start date
- Sort by reaction score
Today I gave OCLP0.6.8(AMFIpass_b4)/Ventura13.4.1 another try. No success either to run a VM in Fusion.
OCLP0.6.7 also bricked Fusion in Monterey.
So I downgraded to OCLP0.6.1 to make Fusion fully working again (as long as the use of the discrete GPU is forced #1 )
Last edited:
iMac 14.2 with Ventura 13.4.1(c) and Fusion 13.0.2. Experenced the Broken Pipe error after the Ventura update. Intalled OCLP 0.6.7 AMFIPass b4 and Windows 10 and 11 virtual machines start without error again. I did not need to re-install Fusion. Not yet sure about the stability as I experienced an unexpected crash of the Windows 11 VM during a Windows update but it has been OK since then.
Yep. My fault. Didn't follow the OCLP-instructions properly.
I've started with OCLP 0.6.8_AMFIpass-b4 / Ventura13.4.1 and that bricked VMware Fusion 13.
To sort out the problem I downloaded OCLP 0.6.7, reverted/reinstalled the RootPatches and rebuilt OpenCore.
After reboot I replaced OCLP 0.6.7 by OCLP 0.6.8_AMFIpass-b4 and proceeded as described:
- ...
- ...
- Build and install OpenCore in order to add AMFIPass to your EFI.
- Reboot
- Install the new root patches
- Reboot
- Build and install OpenCore again to enable AMFI
- Reboot
- You should now be booting with AMFI enabled!
I hope this solution is resilient to further OCLP/Ventura-updates.
(Did I mention, I don't like the version number of macOS-Ventura ...)
Last edited:
Which version of VMware Fusion?
With OCLP1.2.1/Ventura13.6.1 now Fusion 13.0.1 is working fine both on my 2013 11"MBA6,1 and my 2012 15"MBP9,1.
But the MBP9,1 needs to have the "discrete" GPU switched on (workaround either https://gfx.io/ or adding the line mks.forceDiscreteGPU="TRUE" to the .vmx file)
After upgrading to the latest Fusion13.5 my VMs were broken again. So I went back to Fusion 13.0.1, which is fully functioning on both OCLP/Ventura and OCLP/Sonoma.
Anyone here successfully running a version of Fusion13.x higher than Fusion13.0.1?
I just have found this thread.
I had mention that with all OCLP 1.2, 1.2.1 , 1.3 on my MBP 13" macbook 9,2 mid2012 (that has only intel hd graphics)
Im unable to run VMWare Fusion 13.x and and 13.5.x as i had tested on Monterrey and also Sonoma.
I had 3 clean installs with no luck.
Neither that seems that also Premiere, and other adobe products failing to installing due to 107 error, that meaning (inside adobe's forum) an incompatible HW .
So im assuming something has to do with iGPU and its patches, even with AMFI pass .
I had mention that with all OCLP 1.2, 1.2.1 , 1.3 on my MBP 13" macbook 9,2 mid2012 (that has only intel hd graphics)
Im unable to run VMWare Fusion 13.x and and 13.5.x as i had tested on Monterrey and also Sonoma.
I had 3 clean installs with no luck.
Neither that seems that also Premiere, and other adobe products failing to installing due to 107 error, that meaning (inside adobe's forum) an incompatible HW .
So im assuming something has to do with iGPU and its patches, even with AMFI pass .
Adobe's latest video apps require AVX2 support, which the CPU in your 2012 MBP doesn't have. VMware Fusion has some similar hardware requirements that prevent Fusion from working on old Macs with OCLP.
Well, in order to make Fusion13 work, I had to go back to Fusion 13.0.1,
change permissions of the VMBundle,
open the VMBundle/Package and
also change the permissions of the .vmx file and the .vmdk files within the bundle/package,
and finally
on an 15"MBP activate the discrete GPU permanently with gfxCardStatus.
Last edited:
I've run into the same problem. I'm using OCLP_Sonoma on my "mid2012 15" MBP9,1. I'm running Vmware Fusion 13.5. I tried your solution (thank you for "gfxCardStatus app"). It makes no difference switching between "Integrated Only" or "Discrete Only". I have also researched and found an article requiring OCLP v1.3 to install "AMFIPass.kext v1.4" extension, which I have done. Nothing has removed the "Transport error (VMDB) -14: Pipe connection has been broken" error. Any other suggestions are welcome.
Where can I obtain Vmware Fusion v13.0.1? I can only see v13.5 on Vmware.com which is where I downloaded it.
Thank you. I had the same problem on OCLP-Sonoma. Reverting back to Vmware Fusion 13.0.1, updating OCLP to v1.3 and adding AMFIPass.kext + setting gfxCardStats to discrete solved the problem.
There is no need to revert VMWARE FUSION to past versions.
This problem has been resolved in today's latest version, 13.5.2.
Remove AMFI=0x80 option.
And replace it with AMFIPass.kext instead to safely keep AMFI disabled.
github.com
I Think, The Ventura version is v1.3.1 and the Sonoma version is v1.4.0.
I used v1.3.1 on Ventura 13.4.1.
Now the VMs in VMARE FUSION will start booting without problems.
Detailed explanations are provided below.
Since the explanation is in Korean, I recommend translating it into your native language.
This problem has been resolved in today's latest version, 13.5.2.
Remove AMFI=0x80 option.
And replace it with AMFIPass.kext instead to safely keep AMFI disabled.
OpenCore-Legacy-Patcher/payloads/Kexts/Acidanthera at main · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
github.com
I Think, The Ventura version is v1.3.1 and the Sonoma version is v1.4.0.
I used v1.3.1 on Ventura 13.4.1.
Now the VMs in VMARE FUSION will start booting without problems.
Detailed explanations are provided below.
Since the explanation is in Korean, I recommend translating it into your native language.
The differences between the versions seem a little different than I expected.
I looked up the version history of 1.3.1 and 1.4.0,
The following was described in 1.4.0.
"Remove NVMeFix.kext MaxKernel"
OpenCore-Legacy-Patcher/payloads/Kexts/Acidanthera at main · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
github.com
It seems that Sonoma has improved a conflict with this kext.
I tried using Sonoma with 1.3.1 and NVMeFix.kext without any adjustments, but a kernel panic occurred.
Also, as a result of examining the EFI of Monterey 12.7.3, which is being used with my MacBook Pro Mid 2014 and OCLP 1.3.0, the 1.4.0 version of AMFIPass.kext was already in use.
Hello i am stuck in the same error i have downgraded 13.0.1 then upgraded, checked amfipass kext is in efi partition 1.4.0 boot in efi parition in sonoma but no luck with vmware. I am in OCLP 1.4.3 with root patches applied and disabled SIP.I cant make a new machine or either turn on existent one. Can someone help me please?
How to apply AMFIPass.kext
1. If you are using the amfi=0x80 flag, first remove it from config.plist.
2. Add AMFIPass.kext to the kernel section of config.plist.
3. If you were using the amfi=0x80 flag, remove amfi=0x80 stored in nvram through nvram reset.
* If you use AMFIPass.kext and amfi=0x80 together, AMFI will be disabled as is, so you must remove amfi=0x80.
Have you followed the precautions above?
Thanks for the reply where can i see if the flag has this value? other thing is the kext is in EFI partition in OC/kexts inside and its version 1.4. How can i remove the flag amfi=ox80. Thanks
If you checked the version of Kext, it means that you have mounted the EFI partition. Under this assumption, you need to find the presence or absence of the amfi=0x80 setting in the config.plist file.
Please tell us more about Your Mac!
Did You try all steps, I've mentioned in #34?
- delete current Fusion (with AppCleaner), reinstall Fusion 13.0.1 and stay with 13.0.1
- change permissions of the VMBundle and files within the Package (You'll have to open the VMBundle/Package and
also change the permissions of the .vmx file and the .vmdk files, that are within the bundle/package)
- on an 15"MBP activate the discrete GPU permanently with gfxCardStatus.
Hell ohanks for reply, i deleted with Appcleaner. The permission to which user needs to be changed? I have a Macpro no MBP but also i can change the discretecpu. The other thing is that i am connecting a Cinema Display to my Macpro in the 6 ports of display port but no success. OCLP is not able to make this? Thanks.
Now its running i removed the ox80 flag in config.plist and selected gfxstatus discrete graphics!!!. Thanks
hello ,
i have installed bigsur in a virtualmachine on a PC.
however, the graphics card is unsupported (showing as "Monitor 128 MB")
if i would install a supported GPU for BigSur instead , could i get proper graphics in VirtualMachine?
thanks.
i have installed bigsur in a virtualmachine on a PC.
however, the graphics card is unsupported (showing as "Monitor 128 MB")
if i would install a supported GPU for BigSur instead , could i get proper graphics in VirtualMachine?
thanks.