All Posts

Fusion  Player Version 13.5.0 (22583790) Mac model: MacBook Pro M2 2022 OS: Sonoma 14.1.11 CentOS Downloaded today Nov 9, 2023: CentOS-Stream-9-latest-aarch64-dvd1.iso   .vmx config: (I used the defaults) $ cat d.vmx .encoding = "UTF-8" config.version = "8" virtualHW.version = "21" pciBridge0.present = "TRUE" pciBridge4.present = "TRUE" pciBridge4.virtualDev = "pcieRootPort" pciBridge4.functions = "8" pciBridge5.present = "TRUE" pciBridge5.virtualDev = "pcieRootPort" pciBridge5.functions = "8" pciBridge6.present = "TRUE" pciBridge6.virtualDev = "pcieRootPort" pciBridge6.functions = "8" pciBridge7.present = "TRUE" pciBridge7.virtualDev = "pcieRootPort" pciBridge7.functions = "8" vmci0.present = "TRUE" hpet0.present = "TRUE" nvram = "d.nvram" virtualHW.productCompatibility = "hosted" powerType.powerOff = "soft" powerType.powerOn = "soft" powerType.suspend = "soft" powerType.reset = "soft" displayName = "d" usb.vbluetooth.startConnected = "TRUE" firmware = "efi" guestOS = "arm-other6xlinux-64" tools.syncTime = "TRUE" tools.upgrade.policy = "upgradeAtPowerCycle" sound.autoDetect = "TRUE" sound.virtualDev = "hdaudio" sound.fileName = "-1" sound.present = "TRUE" numvcpus = "2" cpuid.coresPerSocket = "1" memsize = "768" sata0.present = "TRUE" nvme0.present = "TRUE" nvme0:0.fileName = "Virtual Disk.vmdk" nvme0:0.present = "TRUE" sata0:1.deviceType = "cdrom-image" sata0:1.fileName = "/Users/msacks/Downloads/CentOS-Stream-9-latest-aarch64-dvd1.iso" sata0:1.present = "TRUE" usb.present = "TRUE" ehci.present = "TRUE" usb_xhci.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.addressType = "generated" ethernet0.virtualDev = "e1000e" ethernet0.linkStatePropagation.enable = "TRUE" ethernet0.present = "TRUE" extendedConfigFile = "d.vmxf" floppy0.present = "FALSE" vmxstats.filename = "d.scoreboard" numa.autosize.cookie = "20012" numa.autosize.vcpu.maxPerVirtualNode = "2" uuid.bios = "56 4d ae 2d c0 1c 89 32-73 90 f6 bf 9f ba 92 c4" uuid.location = "56 4d ae 2d c0 1c 89 32-73 90 f6 bf 9f ba 92 c4" pciBridge0.pciSlotNumber = "17" pciBridge4.pciSlotNumber = "21" pciBridge5.pciSlotNumber = "22" pciBridge6.pciSlotNumber = "23" pciBridge7.pciSlotNumber = "24" usb.pciSlotNumber = "32" ethernet0.pciSlotNumber = "160" sound.pciSlotNumber = "33" ehci.pciSlotNumber = "34" usb_xhci.pciSlotNumber = "192" sata0.pciSlotNumber = "35" nvme0.pciSlotNumber = "224" nvme0:0.redo = "" svga.vramSize = "268435456" vmotion.checkpointFBSize = "134217728" vmotion.checkpointSVGAPrimarySize = "268435456" vmotion.svga.mobMaxSize = "268435456" vmotion.svga.graphicsMemoryKB = "262144" ethernet0.generatedAddress = "00:0c:29:ba:92:c4" ethernet0.generatedAddressOffset = "0" vmci0.id = "-1615162684" nvme0.subnqnUUID = "52 bf a7 5a 13 36 67 d9-5d 4b 9a e5 86 1e 91 b3" monitor.phys_bits_used = "32" cleanShutdown = "FALSE" softPowerOff = "FALSE" usb_xhci:4.present = "TRUE" usb_xhci:4.deviceType = "hid" usb_xhci:4.port = "4" usb_xhci:4.parent = "-1" usb_xhci:6.speed = "2" usb_xhci:6.present = "TRUE" usb_xhci:6.deviceType = "hub" usb_xhci:6.port = "6" usb_xhci:6.parent = "-1" usb_xhci:7.speed = "4" usb_xhci:7.present = "TRUE" usb_xhci:7.deviceType = "hub" usb_xhci:7.port = "7" usb_xhci:7.parent = "-1" usb:1.speed = "2" usb:1.present = "TRUE" usb:1.deviceType = "hub" usb:1.port = "1" usb:1.parent = "-1" svga.guestBackedPrimaryAware = "TRUE" checkpoint.vmState = "" ehci:0.present = "TRUE" ehci:0.deviceType = "video" ehci:0.port = "0" ehci:0.parent = "-1"  

What version of Fusion, what Mac model, and what macOS version? What’s the date on the CentOS 9 Stream installer? How did you configure your virtual machine? (A copy of the .vmx file would be helpful). 

I agree with you that VMware should not be constantly adding and removing these. It’s lazy coding - otherwise they’d have to write a proper uninstaller to remove these as opposed to just dragging the app to the trash. VMware should have installed those items once and left them there, updating them only when needed by upgrades. It’s also not like those services are started  by the system automatically  they are started on demand by Fusion   I believe Apple is on the path of stopping the system wide Library folders from being modified by applications. Whats annoying is that VMware knew about this long before Fusion 13.5 was released. I personally had an exchange with their staff during the Tech Preview stage. They decided not to do anything about this despite knowing about it for months. 

One thing triggers the other...  Is there any reason for VMWare to keep adding/removing these?  That is what triggers the Background notification from Apple... Solution:  developer, don't remove them.. there is no need to remove files added to these folders.. Its seems Apple is alerting people in the right way, but the implementation of is it allowing developers to annoy users. BTW: VPN apps do the same thing. ExpressVPN is annoying me equally as bad. But it  the way Apple allowed this add/remove to happen when there is no resewn to remove files. They introduced the issue. If users want to remove files they can  manually browse these two folders  and remove manually..

@ColoradoMarmot wrote: Correct, this is MacOS and there's no easy to way to suppress it.  It's a design defect and an annoyance that Fusion needs to fix. --- before Apple decides to lock down the ability of applications to add things to /Library/LaunchDaemons and /Library/LaunchAgents, which looks like the direction that they're heading. 

Ok, here's what might get that Windows 7 VM working for you: First, make sure you have made a copy of that VM folder and its contents. Just in case so if something goes wrong, you don't have to go back to the original system to copy it over again. Next, delete the following files from the VM's folder: That needs to be done because it looks like the VM was in a suspended state.  Windows 7 x64-06e43f69.vmem.lck Windows 7 x64-06e43f69.vmem Windows 7 x64-06e43f69.vmss Then, download the attached zipfile. It contains a VMX file that was recreated from the log file you provided. Unzip the file and it will extract the file "Windows 7 x64.vmx". Move that file to fhe virtual machine's bundle. Now try opening the VM from Fusion GUI using FIle > Open... and see if you can power on the VM. If things don't work, then you always have the copy you took to restore things back to where we were before, I have another idea if this doesn't work....    

I've been running 13 for some time and now 13.5. It's not a complete fix. I have definitely seen it since upgrading. However, I would say that the number of occurrences is now vanishingly small. Not zero, but maybe once or twice since 13 has been released. Still frustrating when it happens, but I can live with it.  

@wb9tpg1 wrote: I'm interested if v13 solves this issue.  If it still persists I'm switching to Parallels.   Can anyone who's upgraded comment?  If you're on Apple Silicon (don't know about Intel), Parallels now looks to be a GUI wrapper around macOS's lightweight virtualisation framework.  If you don't mind a little extra effort, this free app (also a wrapper around the built-in virtualisation) might be just as good: https://eclecticlight.co/virtualisation-on-apple-silicon/.  It can even run two macOS VMs concurrently, unlike Parallels.

Been a problem for me for a while.  Currently using Fusion 12.2.5 on macOS Ventura 13.6.1.  Sometimes just launching Fusion results in this.  Sometimes I wake up a sleeping VM (Windows or Linux) and find it has no network access.  In these cases, I disconnect the network adapter and run: sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start  It's an annoyance that at best wastes time.  It drains my battery and impacts the performance of macOS.

Is your macOS system language set to something other than English? If not, try it again (could be a problem on Microsoft's side). If all else fails,, try the using the command line version of the utility. Detailed instructions can be found in the Unofficial Fusion Companion Guide https://communities.vmware.com/t5/VMware-Fusion-Documents/The-Unofficial-Fusion-13-for-Apple-Silicon-Companion-Guide/ta-p/2939907. Look for the topic in chapter 15: Windows 11 download tool in Fusion GUI fails to create ISO