12 Replies Latest reply on Jun 3, 2020 3:00 AM by joserfonseca Branched from an earlier discussion.

    Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?

    ocracoke Lurker

      Same error, but I'm running Fusion 11.5 on 10.15.5 OSx Catalina.

      vmware.log attached.

       

      Probably too much info but...

      I had 10.1.5 installed but was getting black screen.

      Tried to upgrade to 10.1.6 but the upgrade failed in the middle.

      So paid for 11.5 and upgraded to that.

      Got this error, so...

      Restored vmware fusion app directory from time machine backup (back to 10.1.5)

      Reinstalled 11.5.

      Everything appeared to work fine. Updated Windows 10 VM to latest.

      Shut down Windows.

      Today I get this error and it won't start up again.

        • 1. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
          scott28tt Champion
          User ModeratorsCommunity WarriorsVMware Employees

          Moderator: Comment branched from old Workstation Pro thread to the Fusion area.

          • 2. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
            joserfonseca Novice
            VMware Employees

            The segmentation fault seems to happen when powering on Metal graphics.  Unfortunately the stack back trace seems to be somewhat inaccurate, and doesn't allow to pin point exactly where.

             

            You can probably workaround by temporarily disabling 3D acceleration.

             

            It's odd it was working well, then stopped working.  I doubt updating Windows 10 would trigger this particular problem.

             

            macOS 10.15.5 GA was recently launched, and you have it installed.  Maybe the last time it worked it was before the macOS 10.15.5 upgrade. We have been testing with macOS 10.15.5 builds, but we don't have all Macs, and particular, not this exact one.  Could you please provide the newest vmware-*.log that did not show this problem?  That would allow us to hopefully narrow down the problem.

             

            Another thing worth trying is to, enable 3D acceleration, but instead of "Always Use High Performance Graphics" please try choosing the "Don't Use High Performance Graphics".  I believe your iMac doesn't have an Integrated GPU, so it won't make a difference in performance, but will avoid some complexity in choosing/forcing the high performance graphics which might be playing a role here.

            • 3. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
              joserfonseca Novice
              VMware Employees

              After spending more time analyzing the vmware.log provided, I can almost bet that if you: leave 3D enabled, but choose "Don't Use High Performance Graphics" you should be able to avoid this.

               

              If you could confirm this does indeed avoids the issue, we'd appreciate it.

              • 4. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                awkimpton Lurker

                I'm seeing a similar crash from MKS, having just upgraded to both Catalina 10.15.5 and Fusion 11.5.5 this weekend :

                 

                2020-06-01T08:09:16.685-05:00| vmx| I005: MKS PowerOn

                2020-06-01T08:09:16.733-05:00| mks| I005: VTHREAD 123145507250176 "mks" tid 8564

                2020-06-01T08:09:16.733-05:00| mks| I005: MKS thread is alive

                2020-06-01T08:09:16.759-05:00| mks| I005: MKS MacOSMouse: Using event tap path.

                2020-06-01T08:09:16.759-05:00| mouse| I005: VTHREAD 123145508323328 "mouse" tid 8566

                2020-06-01T08:09:16.759-05:00| keyboard| I005: VTHREAD 123145508859904 "keyboard" tid 8567

                2020-06-01T08:09:16.769-05:00| keyboard| I005: MKS MacOSKeyboard: Adding device: VID:05AC PID:024F Apple Inc. (Apple Keyboard)

                2020-06-01T08:09:16.769-05:00| mks| I005: MKS-RenderMain: PowerOn allowed MKSBasicOps MTLRenderer

                2020-06-01T08:09:16.769-05:00| mks| I005: MKS-RenderMain: Collecting RenderOps caps from MTLRenderer

                2020-06-01T08:09:16-05:00[+0.000]| mks| W003: Caught signal 11 -- tid 8564 (addr 20)

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: rip 0x7fff6d653678 rsp 0x70000c371aa8 rbp 0x70000c371e30

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: rax 0x0 rbx 0x7fff6d651800 rcx 0x7fff8c188428 rdx 0x7fff8c18baa0 rsi 0x8907 rdi 0x7fb899552210

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005:         r8 0x4e5f r9 0xcc r10 0x0 r11 0x202 r12 0x7fff78a9e939 r13 0x10bd11748 r14 0x7fb860020000 r15 0x7fb89988a040

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371AA8 : 0x000000010b0545e0 0x000000000000000a

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371AB8 : 0x000000000000000f 0x0000000000000000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371AC8 : 0x000000010b1c4880 0x6fb4fdb87fe400e1

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371AD8 : 0x0000000000000000 0x000070000c371b80

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371AE8 : 0x000000010b1c4926 0x000000005ed4efec

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371AF8 : 0x00007000000bbd93 0x000000005ed4efec

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371B08 : 0x000000000000013f 0x0000000900000010

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SIGNAL: stack 70000C371B18 : 0x0000000100000008 0x0000007800000005

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace:

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[0] rip=000000010b2c69b1

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[1] rip=000000010b43f3ca

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[2] rip=00007fff6e9fe5fd

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[3] rip=000000010c4df080

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[4] rip=000000010afcb3de

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[5] rip=000000010afcab97

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[6] rip=000000010af8643e

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[7] rip=000000010af9ee3d

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[8] rip=000000010b2518cb

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[9] rip=00007fff6ea0a109

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[10] rip=00007fff6ea05b8b

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[0] rip=000000010b2c69b1 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[1] rip=000000010b43f3ca in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[2] rip=00007fff6e9fe5fd in function _sigtramp in object /usr/lib/system/libsystem_platform.dylib loaded at 00007fff6e9fb000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[3] rip=000000010c4df080n

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[4] rip=000000010afcb3de in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[5] rip=000000010afcab97 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[6] rip=000000010af8643e in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[7] rip=000000010af9ee3d in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[8] rip=000000010b2518cb in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[9] rip=00007fff6ea0a109 in function _pthread_start in object /usr/lib/system/libsystem_pthread.dylib loaded at 00007fff6ea04000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[10] rip=00007fff6ea05b8b in function thread_start in object /usr/lib/system/libsystem_pthread.dylib loaded at 00007fff6ea04000

                2020-06-01T08:09:16-05:00[+0.000]| mks| E001: PANIC: Unexpected signal: 11.

                2020-06-01T08:09:16-05:00[+0.000]| mks| W003:

                2020-06-01T08:09:16-05:00[+0.000]| mks| W003+ The core dump limit is set to ZERO; no core dump should be expected

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace:

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[0] rip=000000010b2c69b1

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[1] rip=000000010ad336fb

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[2] rip=000000010b43f483

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[3] rip=00007fff6e9fe5fd

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[4] rip=000000010c4df080

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[5] rip=000000010afcb3de

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[6] rip=000000010afcab97

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[7] rip=000000010af8643e

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[8] rip=000000010af9ee3d

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[9] rip=000000010b2518cb

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[10] rip=00007fff6ea0a109

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Backtrace[11] rip=00007fff6ea05b8b

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[0] rip=000000010b2c69b1 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[1] rip=000000010ad336fb in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[2] rip=000000010b43f483 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[3] rip=00007fff6e9fe5fd in function _sigtramp in object /usr/lib/system/libsystem_platform.dylib loaded at 00007fff6e9fb000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[4] rip=000000010c4df080n

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[5] rip=000000010afcb3de in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[6] rip=000000010afcab97 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[7] rip=000000010af8643e in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[8] rip=000000010af9ee3d in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[9] rip=000000010b2518cb in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 000000010acf4000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[10] rip=00007fff6ea0a109 in function _pthread_start in object /usr/lib/system/libsystem_pthread.dylib loaded at 00007fff6ea04000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: SymBacktrace[11] rip=00007fff6ea05b8b in function thread_start in object /usr/lib/system/libsystem_pthread.dylib loaded at 00007fff6ea04000

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: Printing loaded objects

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: [10ACF4000-10B871000): /Applications/VMware Fusion.app/Contents/Library/vmware-vmx

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: [7FFF34787000-7FFF34C07000): /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: [7FFF355E6000-7FFF35650000): /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation

                2020-06-01T08:09:16-05:00[+0.000]| mks| I005: [7FFF36E41000-7FFF37207000): /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation

                 

                 

                This on a Retina 5K iMac (2019), with Accelerate 3D Graphics enabled. Disabling 3D Acceleration looks to fix the problem though obviously that's not an ideal/longterm solution!

                • 5. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                  Mikero Master
                  VMware Employees

                  Thanks Andrew, I'll let the MKS team know...  Also hi!

                   

                  *edit*well I see Jose is already here... thanks again for the stack trace!

                  • 6. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                    ocracoke Lurker

                    There is no pulldown for battery options. I assume because there's no battery since it's an iMac. Works fine if I disable 3D graphics.

                     

                    Attaching a recent log when it succeeded (after deleting fusion app and related files and reinstalling).

                    • 7. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                      awkimpton Lurker

                      Reinstalling Fusion 11.5.5 made no difference, the VM will not start (reports the Transport VMDB error, and the MKS crash previously mentioned) unless I disable 3D Acceleration.

                       

                      Is there an 11.5.4 download? I'm assuming that I could in theory go back to that version? That there were no changes made to VMX files, or .vmdk files in the course of the move from 11.5.4 to 11.5.5?

                      • 8. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                        awkimpton Lurker

                        I was able to download 11.5.3 through the downloads link for Fusion, reinstalling that version fixed my problem and I was able to run a VM with 3D Acceleration enabled. So it rather looks like a bug with Fusion 11.5.5?

                         

                        For now I'll stay on 11.5.3, but I'll have to forgo the exciting new container stuff :-(

                        • 9. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                          joserfonseca Novice
                          VMware Employees

                          If there's no "Battery Life" drop down menu on the Display settings, then instead please power off the VM, manually edit the .vmx file, modifying the option mks.forceDiscreteGPU="TRUE" to mks.forceDiscreteGPU="FALSE"

                           

                          That should enable you to enable 3D acceleration without hitting the issue.

                          • 11. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                            awkimpton Lurker

                            Is this not still a drop in performance? Since you're now forcing the VM away from the discrete (and likely higher performance) GPU, and instead using the integrated GPU? Or does the VM still pick the higher performance graphics card? It's just not forced into it (triggering the bug)?

                            • 12. Re: "Transport (VMDB) error -14: Pipe connection has been broken." How to resolve this?
                              joserfonseca Novice
                              VMware Employees

                              So far this issue has only been reported on iMacs without any integrated GPU: at least both the original and your report are.  So no matter what GPU selection mode is chosen, one will invariably get the discrete GPU, as it's the only one available.  So rest assured that you should not experience any performance degradation, at least not until you move/copy the VM onto a dual-GPU mac.

                               

                              We don't fully understand the problem as we haven't been able to reproduce it ourselves in-house so far, but I don't think it's a coincidence that only systems without dual GPUs seems affected.  I have several dual GPU systems, and neither reproduces the issue.  Mac Pro doesn't seem affected neither.  Somehow only iMacs seem affected.

                               

                              If anybody experiences this issue with a dual GPU system please do let us know.  At any rate, we are hopeful that the next release of Fusion will avoid this particular issue without requiring any further action from the end user.

                              1 person found this helpful