VM shuts down seconds after powering on: "Pipe connection has been broken" (-14)

[lmerrill]

Hi all,

This is my first time posting in the VMware Communities but not my first time using Fusion - in fact I've been a loyal Fusion user for almost a decade and in that time have barely had any problems.

I was eager to upgrade to the latest tech preview on my 2021 Apple Silicon 16-inch M1 MacBook Pro running macOS Sonoma Beta so as to get support for copy and paste, among other VMware tools inside my Windows 11 ARM virtual machine.

I upgraded to the beta a few days ago and, despite getting the ""Unable to reencrypt the virtual machine: Disk problem" message discussed elsewhere, things have been fine after I decided to create a new virtual machine and restored from a Windows system image backup. Fine until last night, that is.

I tried to start up my virtual machine, and it powered on for about 5 seconds before immediately powering off again. Trying again yielded the same result. I changed some system settings, like amount of processors and memory given to the VM, removing USB devices, etc. but to no avail. Heck I even re-installed VMware Fusion 13 and tried to create a new virtual machine there, which worked fine, but when I powered it on so I could install Windows, the same issue happened again.

I've attached a support information bundle but wanted to highlight these lines from the ~/Library/Logs/VMware Fusion/vmware-vmfusion.log file which I feel are interesting. Note the support bundle is the smaller of the two options because the full bundle was over 400 MB in size and would exceed the attachment size limit, but I still have the archive if anyone wants to see it some other way.

2023-07-28T02:31:13.820Z In(05) VMware Fusion Initialized the OpenGL renderer.
2023-07-28T02:31:13.820Z In(05) VMware Fusion cui::MKSScreenView::SetRenderTarget: hostWindow and surfaceID are none. id: 0.
2023-07-28T02:31:13.820Z In(05) VMware Fusion cui::MKSScreenView::OnHostWindowChanged, id: 0, unsetting destination and setting is rendering to false
2023-07-28T02:31:13.820Z In(05) VMware Fusion -[UIDrawnMKSController initWithWindowId:view:portName:], starting UIDrawnMKS rendering
2023-07-28T02:31:13.821Z In(05) VMware Fusion UtilMacOS: Found graphics devices
2023-07-28T02:31:13.821Z In(05) VMware Fusion Initialized the OpenGL renderer.
2023-07-28T02:31:13.824Z In(05) VMware Fusion -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1
2023-07-28T02:31:13.824Z In(05)+ VMware Fusion .
2023-07-28T02:31:13.825Z In(05) VMware Fusion -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1
2023-07-28T02:31:13.825Z In(05)+ VMware Fusion .
2023-07-28T02:31:13.825Z In(05) VMware Fusion -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1
2023-07-28T02:31:13.825Z In(05)+ VMware Fusion .
2023-07-28T02:31:13.836Z In(05) VMware Fusion MKSControl: Connect
2023-07-28T02:31:13.849Z In(05) VMware Fusion CUIMKS: cui::MKS::OnSetAttachedCompleted (12A00B000)
2023-07-28T02:31:13.854Z In(05) VMware Fusion SOCKET 6 (40) AsyncTCPSocketSetOption: Option layer/level [6], option/name [1]: could not set OS option for TCP socket; error [102: Operation not supported on socket].
2023-07-28T02:31:13.855Z In(05) VMware Fusion -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1
2023-07-28T02:31:13.855Z In(05)+ VMware Fusion .
2023-07-28T02:31:13.856Z In(05) VMware Fusion -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1
2023-07-28T02:31:13.856Z In(05)+ VMware Fusion .
2023-07-28T02:31:13.856Z In(05) VMware Fusion -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1
2023-07-28T02:31:13.856Z In(05)+ VMware Fusion .
2023-07-28T02:31:13.874Z In(05) VMware Fusion OnGuestCanRunUnityChanged: The guest is a supported version of Windows, checking Tools status. Version status: 3, running status: 1
2023-07-28T02:31:13.874Z In(05) VMware Fusion OnGuestCanRunUnityChanged: Tools status is not INSTALLED
2023-07-28T02:31:13.912Z In(05) VMware Fusion DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2023-07-28T02:31:13.989Z In(05) VMware Fusion DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2023-07-28T02:31:14.003Z In(05) VMware Fusion DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2023-07-28T02:31:14.311Z In(05) VMware Fusion DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2023-07-28T02:31:17.508Z In(05) VMware Fusion SOCKET 5 (44) recv detected remote shutdown
2023-07-28T02:31:17.508Z Wa(03) VMware Fusion MKSControlClientBase: Remote Disconnect: socket closed: (4) Remote disconnected.
2023-07-28T02:31:17.508Z In(05) VMware Fusion MKSControl: CloseMKSControl
2023-07-28T02:31:17.508Z Wa(03) VMware Fusion MKSControlClientBase: MKSControlWriteCB returns because connection is invalid: mSocket = 138F52DF0, mConState = 0.
2023-07-28T02:31:17.508Z In(05) VMware Fusion SOCKET 6 (40) recv detected remote shutdown
2023-07-28T02:31:17.508Z In(05) VMware Fusion Detected automation socket close for VM (/Users/lmerrill/Virtual Machines.localized/Windows 11.vmwarevm/Windows 11.vmx)
2023-07-28T02:31:17.508Z In(05) VMware Fusion CUIMKS: On MKSControl connection broken (12A00B000)
2023-07-28T02:31:17.508Z In(05) VMware Fusion CUIMKS: cui::MKS::SetAttached (12A00B000): detach
2023-07-28T02:31:17.508Z In(05) VMware Fusion MKSControlClientBase: Disconnect is called (1299052F0) (current state 0).
2023-07-28T02:31:17.508Z In(05) VMware Fusion MKSControl: CloseMKSControl
2023-07-28T02:31:17.508Z Wa(03) VMware Fusion MKSControlClientBase: MKSControlWriteCB returns because connection is invalid: mSocket = 0, mConState = 0.
2023-07-28T02:31:17.508Z In(05) VMware Fusion MKSControlClientBase: Disconnect is done (1299052F0) (current state 0).
2023-07-28T02:31:17.508Z In(05) VMware Fusion VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF (remote disconnect)
2023-07-28T02:31:17.508Z In(05) VMware Fusion Internal VMDB error: Pipe: Read failed (-32)
2023-07-28T02:31:17.509Z In(05) VMware Fusion CUIMKS: cui::MKS::OnSetAttachedCompleted (12A00B000)
2023-07-28T02:31:17.509Z In(05) VMware Fusion CUIMKS: On MKSControl connection broken done (12A00B000).
2023-07-28T02:31:17.509Z In(05) VMware Fusion VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#9/' (-14)
2023-07-28T02:31:17.509Z In(05) VMware Fusion VigorOnlineCnxDemux: VmdbCnx failed: Lost a connection to the running VMX instance.
2023-07-28T02:31:17.509Z In(05)+ VMware Fusion Transport (VMDB) error -14: Pipe connection has been broken.
2023-07-28T02:31:17.509Z In(05)+ VMware Fusion
2023-07-28T02:31:17.509Z In(05) VMware Fusion VigorOnlineDisconnect: disconnect /vm/#a54346d4b5771e99/ via /db/connection/#9/
2023-07-28T02:31:17.509Z In(05) VMware Fusion /Users/lmerrill/Virtual Machines.localized/Windows 11.vmwarevm/Windows 11.vmx: Unmounting VM begun.
2023-07-28T02:31:17.509Z In(05) VMware Fusion VMDB unmount initiated for /vm/#a54346d4b5771e99/.
2023-07-28T02:31:17.516Z In(05) VMware Fusion VigorOnlineUnmountCb: Mount state values have changed for /vm/#a54346d4b5771e99/.
2023-07-28T02:31:17.516Z In(05) VMware Fusion VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#9/'
2023-07-28T02:31:17.516Z In(05) VMware Fusion VigorOnlineUnmountCb: Unmount complete for /vm/#a54346d4b5771e99/.
2023-07-28T02:31:17.516Z In(05) VMware Fusion VigorOnlineUnmountCb unset Vigor path on vm unmount.
2023-07-28T02:31:17.516Z In(05) VMware Fusion /Users/lmerrill/Virtual Machines.localized/Windows 11.vmwarevm/Windows 11.vmx: Unmounting VM complete.
2023-07-28T02:31:17.516Z In(05) VMware Fusion /Users/lmerrill/Virtual Machines.localized/Windows 11.vmwarevm/Windows 11.vmx: Reloading config state.
2023-07-28T02:31:17.525Z In(05) VMware Fusion VMHS: Transitioned vmx/execState/val to poweredOff

I haven't made any changes on my Mac that might coincide with this issue and don't know where the problem could lie. Any assistance or insight would be very helpful, especially as like I said even the stable VMware Fusion 13 exhibits the same exact issue so I know this isn't strictly related to the new tech preview (but is where I first encountered the problem).

Thanks in advance for any replies!

[Technogeezer]

Don't rule out an issue with the Sonoma betas.

[lmerrill]

You might be right about that - though I'm not sure if it's an issue or a new requirement by Apple. After doing some further research on my issue and collecting a system log bundle of the 60 seconds before and during virtual machine startup, I came across this:

2023-07-28 15:57:25.512195-0400 0x68ab Default 0x0 3433 0 vmware-vmx-debug: (AppKit) The application with bundle ID com.vmware.vmware-vmx-debug is running setugid(), which is not allowed. Exiting.

[ColoradoMarmot]

@Mikero Two reports of this this morning on the latest Sonoma beta

[Technogeezer]

There are other reports like this one https://appleinsider.com/articles/23/07/30/boot-loops-and-failed-installs-plague-fourth-macos-sonoma... about problems with Sonoma developer beta 4. I'd skip this one if at all possible.

[lmerrill]

For what it's worth, I was able to work around the problem somewhat by using Terminal.app to start the tech preview with the sudo command. This allowed the virtual machine to start, though I had to re-grant all of the required permissions. Starting TP normally via the icon in the Applications folder still yields the error though, and I suspect starting with sudo is not the most secure approach.

To get the permissions to work I had to enable the root account by way of the Director Utility, log into it and start the tech preview there so as to allow the program to prompt me for the required permissions, then I logged out and back into my normal (administrator) account.

[Mikero]

I think there was an update to Sonoma Beta 4 today, I'm installing that and will see how it goes.

[Technogeezer]

Good luck. We’re all counting on you.  

[Mikero]

---

@Technogeezer wrote:

Good luck. We’re all counting on you.  

---

Surely you can't be serious!

Anyway, I have several Win11 VMs that are running simultaneously, no issues thus far on my Mac Studio... Continuing to test there and on my M1 Air.

[lmerrill]

Unfortunately I haven't been that lucky. I just updated to the latest beta release of macOS Sonoma and the issue is still present for me after the update - in fact nothing has changed. The VM still crashes within seconds of starting, and the same error about setugid not being allowed is displayed in the terminal after a log capture.

For context, I am now running beta build 23A5301h (as opposed to 23A5301g, which would suggest this wasn't a big update).

[ColoradoMarmot]

---

@lmerrill wrote:

For what it's worth, I was able to work around the problem somewhat by using Terminal.app to start the tech preview with the sudo command. This allowed the virtual machine to start, though I had to re-grant all of the required permissions. Starting TP normally via the icon in the Applications folder still yields the error though, and I suspect starting with sudo is not the most secure approach.

To get the permissions to work I had to enable the root account by way of the Director Utility, log into it and start the tech preview there so as to allow the program to prompt me for the required permissions, then I logged out and back into my normal (administrator) account.

---

Question - did you install and run as an administrator account (ideally the same one)?  That's required.

FWIW, enabling the root account/setting a password has a long and sordid history of causing random issues (including with Fusion), so if that had happened before the issue, it could be the root cause.  MacOS really doesn't want it turned on.  It's not really UNIX as much as it pretends to be.

Can you replicate on a machine without one set if that was done?

[lmerrill]

Unfortunately Apple doesn't work that way - when it releases a new beta build, the same build applies to all machines running a particular operating system. Today's macOS beta update release, according to the release notes, to news sources like 9to5Mac, etc. was build 23A5301h, up from 23A5301g. I'm running it on a 2021 Apple Silicon M1 MacBook pro with 64 GB RAM, 8 TB disk space, and the highest CPU and GPU core count available.

[lmerrill]

All good questions

First let me clear up a typo from the message you replied to - I meant to say Directory Utility instead of Director Utility. Anyways, I only have one account on my Mac, which is my administrator account, and I've always installed and ran VMware Fusion (12, 13, and now the tech preview) from this same account. When Fusion prompts me for my password while opening, I enter my account's password and this seems to satisfy it.

I didn't enable the root account until like a day or two after trying to start a VM and getting the error. I first discovered the sudo trick but then had a problem with things like keyboard inputs because required permissions were missing, and this was when I went down the rabbit hole of using the root account.

Finally, I was able to replicate this issue three times in different configurations, the first being a separate volume on my current Mac that had a fresh copy of Sonoma Beta installed, the second being another distinct volume on my main Mac that had Ventura installed (where everything worked fine) and then got upgraded to Sonoma Beta (where this issue occurred), and then another distinct volume, this time on my work Mac (a 2021 14-inch Apple Silicon M1 MacBook Pro), with a fresh copy of Sonoma Beta installed where things once again broke with the same issue occurring there as well. I didn't enable the root account on any of these three separate configurations.

[Technogeezer]

I assume this is Sonoma dev beta 4? 

[lmerrill]

Yes.

[ColoradoMarmot]

Hmmm, sounds and feels like a beta issue.