VM crashing or failing to display are one thing, but not being able to create a new VM is quite another. That's not something that we're seeing very often.
Please take the time to post the logs and any other evidence you can provide so that those of us in the community as well as perhaps anyone from Broadcom that may be looking here can take a look and see what's going on. That's going to get things fixed faster if this is indeed a bug.
For what it's worth, I'm running VMware Workstation under Fedora. Workstation 25H2 and 25H2u1 have worked well for me. But then again, I'm not running hardware that has a Nvidia GPU card - in Fedora-land there are no end to issues with Nvidia graphics drivers, Wayland, Vulkan, and Mesa graphics. I've yet to have the Workstation kernel modules fail to compile with Workstation 25H2 and later whenever I've updated Linux kernels on Fedora 43 and 44. ( Linux kernels 6.19 and 7.0. )
I'd personally also eliminate any interaction with Homebrew packages by removing the PATH entries for the Homebrew directories from any .bashrc or .zprofile. Or, create a new user profile (without access to Homebrew) and see if that user can create a virtual machine in Fusion.
------------------------------
Paul Rockwell (technogeezer)
vExpert 2026 (3x)
------------------------------
Original Message:
Sent: May 14, 2026 05:18 PM
From: MMartin-Adm
Subject: macOS Tahoe 26.5 and Fusion
Paul,
Thank you for the offer to examine the Fusion logs. I installed the new 26x build and after a reboot, all VMs are still down and still cannot create any new VMs. I am not complaining. I have the VoiceOver feature completely disabled still. I will just wait until Broadcom fixes the issue. Regarding my M5 MacBook, the only third party software running is VMWare Fusion, and packages from the Brew Package Manager. I have another very well equipped engineering level Linux workstation (RHEL10) and have moved my workload to this computer for now. I do understand that OS upgrades and module libraries need to be in sync at a foundation level. This is the reason I do not run Fedora Linux due to how often the kernel is patched/updated. I like the Fedora Linux product very much, I just do not run VMWare Workstation on it due to the same issue I am having here with MacOS. I have great respect to ALL the IT engineers who write all of this amazing software. I appreciate the Jedi Level expertise they all have. This will resolve itself in time. :)
Original Message:
Sent: May 13, 2026 05:11 PM
From: Technogeezer
Subject: macOS Tahoe 26.5 and Fusion
Can you post the log files for one of the VMs experiencing this issue? Zip up all of the files with a .log extension found in one of those hanging virtual machine's bundle folder, upload the zip file, and let's have a look to see if there's anything that gives a clue to what's happening.
------------------------------
Paul Rockwell (technogeezer)
vExpert 2026 (3x)