RolandZi's Posts

This issue has been discussed before and according to: https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Tech-preview-crashes-when-starting-Windows-VM-for-the-first-time/m-p/2978169 there is an internal ticket for this (on VMWare server): #3254837 https://bugzilla.eng.vmware.com/show_bug.cgi?id=3254837 A work-arround can be found in the 5th answer of this thread: https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/VM-shuts-down-seconds-after-powering-on-quot-Pipe-connection-has/m-p/2980139/highlight/false#M307 Basically: When starting Fusion from the terminal with "su" privileges the error does not show. I can confirm that this works for me, Mac Mini 2018. Since this problem is only present when using Voiceover and since "su" privileges solve it I would assume the root cause is related to access privileges. Let's keep in mind that VM Ware does use the accessibility API and requests permission to it during installation. May be they are dropped again when running as normal user in Sonoma? Best, Roland

Hi, The root cause is found. In Mac OS Sonoma VM fusion does not work at all with the builtin VoiceOver screenreader which I need to use. This worked until updating to Sonoma with all previous versions of VM Fusion. Second source link: https://www.applevis.com/forum/macos-mac-apps/if-your-using-vmware-fusion-mac-do-not-upgrade-sonoma-extremely-serious-bug   Steps to reproduce: 1. Start Voiceover by pressing CMD+F5. 2. Start a virtual machine - guest does not matter.   Expected behavior: Guest OS starts. Observed behavior: Guest runs for some seconds and then terminates.   What would be the best place to send such bug report to? Thanks for your effort so far. Best, Roland

Thanks for the suggestion but unfortunately removing thin print and also the serial0 entries does not make any differences. I tried on three different guests, Linux, Windows 10 and Windows 11 (encrypted) so I don't think it is guest OS related. I also tried to disable the network adapter to narrow down the problem. The strange thing is that it starts, stays running for about 3 seconds and powers off. Looking at the logs I do not see any relation between the power states and this behavior. Looking at the corresponding logs in backed up files I see that they end with something like  2023-09-20T16:24:50.656Z In(05) vmx WQPoolFreePoll : pollIx = 2, signalHandle = 15 2023-09-20T16:24:50.656Z In(05) vmx WQPoolFreePoll : pollIx = 1, signalHandle = 16 2023-09-20T16:24:50.663Z In(05) vmx VMX exit (0). 2023-09-20T16:24:50.670Z In(05) vmx OBJLIB-LIB: ObjLib cleanup done. 2023-09-20T16:24:50.670Z In(05) vmx AIOMGR-S : stat o=8 r=27 w=2112 i=0 br=431263 bw=8591633533   so memory is freed, the subprocess is exited. In my case it looks like the whole process ends prematurely from the VMWARE side. Is there any other source for debugging / tracking this down? Thanks!