Technogeezer's Posts

I'd first uninstall Workstation 17.5 and see if the behavior continues. If it doesn't then reinstall Workstation but opt not to install the enhanced keyboard driver. There have been reports of that driver causing problems. 

@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....    

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   

The last version of Fusion 12 (12.2.5) would accept a Fusion 13 license key. Unfortunately that version won't run on Catalina. To run on Catalina you need 12.1.x which does not accept the Fusion 13 license. If you have a paid Fusion Pro 13 or Player 13 license, you can log into your VMware account and downgrade it at the Customer Connect licensing portal.  However, a personal use license can't be downgraded. You'll need to use the following site to register for a Fusion 12 personal use license (it's not the same as the site you used to register for the Fusion 13 personal use license): https://customerconnect.vmware.com/en/evalcenter?p=fusion-player-personal  

@drcomrade wrote: The solution that actually worked for me was to down the following: 1. Quit VMWare.  2. System Preferences --> Notifications ---.> right click on VMWare, 'reset notifications'.  3. Double click on VMWare Fusion.app.  4. 'Don't allow' push notifications for VMWare.  This forces VMWare to ask for permission to send push notifications, including 'added items that can run in te background'. Granted, it does mean othe notifications for VMWare won't come through - but this seems like a reasonabel tradeoff.  I just tried it. It doesn't work. You'll get fooled into thinking it works if you quit then immediately re-launch Fusion.  Even without turning off Notifications for Fusion, if you shut it down and then immediately re-launch Fusion you will not see the message. If you shut down Fusion, wait a few minutes, and then re-launch it, the message does reappear.  Im almost 100% certain that it's macOS is throwing the notification, and not Fusion. macOS is doing what it's supposed to - warn you about anything putting background tasks/services in the systemwide folders. The warning is for security notification purposes, and that's not something you want suppressed.  And I believe there is some kind of timed check that macOS is doing on the LaunchDaemons and LaunchAgents folders in order to generate the notification.  VMware aggravates the notification proliferation by constantly adding and removing its background items to the system locations every time you start and stop Fusion. No other application I know of does that - they install them once. It is a design decision by VMware (a poor one IMO) that needs to be revisited in the light of macOS's new behaviors. It's up to VMware to change Fusion to fix the issue - probably best to use Apple's recommendations on how to manage background tasks. 

Believe the error message and reference https://kb.vmware.com/s/article/90364 Whatever you are doing with Packer to create the VM is specifying a lsiogic virtual SCSI adapter type that is not implemented by Fusion on Apple Silicon. It appears that only VMware’s pvscsi is implemented for virtual SCSI hard disk controllers. Change what you are doing to specify a NVMe hard disk type. That is the recommended disk type for virtual machines on Apple Silicon Macs and is supported by Debian. Debian does not look like they include the pvscsi driver submitted by VMware to the upstream Linux kernel and Fusion doesn’t support anything other than pvscsi.

I got the file. I'll post the rebuilt vmx file as well as instructions in the morning -- it's approaching midnight here in the EST time zone. The one thing I suggest is to take a backup of the folder of this Windows 7 x64 VM so we can preserve it in the event that something goes horribly wrong (not likely but always better to be safe than sorry)....

I've tried VSCode and I think I'm seeing the same things as you do. The console is definitely wonky and laggy. I've tried it with X11, Wayland, 3D on and 3D off. Nothing hits me over the top of the head to help me figure out if this is VSCode, Fedora, or Fusion related.  I'm going to try this on.a physical Intel PC running Fedora 39 (good chance for me to upgrade) to see if things are any different.

VMware Workstation runs on a PC that contains an Intel or AMD CPU chip. The M1 chip is neither of those.  If what you need to run is a pre-built virtual machine that runs on Workstation, then you're out of luck. Virtual machines built on Intel or AMD systems will not run on Fusion on M1 Macs.  If on the other hand it's a Windows application you might be able to install Windows 11 ARM on a Fusion VM, and then run your application (which I'm assuming is written for x64 Intel PCs) on that VM using the Rosetta-like Intel translation that Microsoft built into Windows 11 ARM.  A little more explanation on what you're trying to run for your class will help us figure out what your alternatives are.

Glad you're making progress. A VM won't power up unless a .vmx file is in the bundle. One additional thought. Are there any files in that directory that's missing the .vmx file named vmware.log (or vmware-0.log, vmware-1.log, vmware-2.log). If so, it may be possible to re-create the .vmx file using the information in those files.  If one of those files are available, zip it up and post it here and I'll see if I can re-create the .vmx file for you.

@TakeTime wrote: This is an interesting message...   That message is normal if the virtual machine has not been configured in its Settings > Advanced to disable side channel mitigations. It only means that the virtual machine will run more slowly (but more securely) than if the VM has the mitigations turned off. 

@TakeTime wrote: Interesting, one folder has a .vmx file, and the other does not. Does this mean that you have two VMs that you want to look at? Does the one that does have a .vmx file in the .vmwarevm folder open on Fusion?

@TakeTime wrote: First, is there a .vmx file in that virtual machine .vmwarevm bundle folder, along with the other files? I see vmem, vmem.lck. vmss, vmdk, nvram, and Apple's .plist extensions on files, no vmx... If there's no .vmx file, the virtual machine will not open. Either you missed it or it doesn't exist where it should on your source disks. Please post a file listing of the files in that folder Also, what operating system is running on this VM? It may be possible to recover given what you have by creating a new virtual machine, but making the new VM use a copy of your existing vmdk files. A file listing will help us as well determine if you really have everything that you need to do this.

@TakeTime wrote: It says 'Select the install method', and one selection is 'Import an existing virtual machine'. I would assume that would be where I click that and Continue, and then  Choose file', and select the VM. Except it's grayed out. I can't select it. I assume 'Select installation method' is about the VM that Fusion is supposed to be running. It must not like the 'smell' of these bundles? From what you've said, you've clicked the wrong menu item. The "Select an installation method" appears when you click File > New to create a brand new VM. You don't want to be at that menu or choose "import a virtual machine" if you have an existing VMware virtual machine. That import function is only for importing a virtual machine from an OVA or OVF formatted file, What you want to do is to open an existing virtual machine. Go to the Fusion menu bar and click File > Open... (NOT FILE > NEW).  In the dialog that appears, locate the virtual machine (that's now tagged as a VMBundle file), select it, and click the Open button.  

Does Fusion have full disk access? I've seen reports of other applications throwing the same error in Sonoma as Apple seems to have tightened access and security with Sonoma. I have it set for that in my system and never have seen that message. I'll try turning full disk access for Fusion off and see if I get anything similar.