palter's Posts

I have no idea if this is the issue or not. But, there's a setting "Displays have separate Spaces". (On Ventura, it's at the bottom of Desktop & Dock.) What is it set to on your Intel system and your M1 system?

Those reports of other people running macOS guests in these forums are running on Intel Macs where it is supported. VMware has not yet implemented support for virtualizing macOS on Apple silicon. @Mikero has mentioned a couple of times that they are looking into it. At this time, the only way to virtualize macOS on Apple silicon is through Apple's Virtualization framework which is a higher level framework than the Hypervisor framework that VMware uses. There are several prodcuts out there -- UTM, VirtualBuddy, Parallels -- which offer that support. However, as Apple's framework is fairly limited, those products face the same limitations. Off the top of my head, I remember that there's no suspend/resume, split disks, resizing disks, copy/paste, etc.

You didn't state what Mac you're using. If you're using an M1 or M2 based Mac, you cannot virtualize macOS in Fusion. Virtualizing macOS on Apple silicon (M1/M2) can only be done using Apple's high-level virtualization framework which Fusion doesn't use. (It uses the lower-level hypervisor framework.) If you want to create a macOS VM on Apple silicon, you can try VirtualBuddy, UTM, or Parallels. However, the VM will be severely limited in what it can do. (I.e., no snapshots, no split disks, etc.)

[Edited to correct pricing on UTM] Excellent work as usual! I'd like to mention another alternative for virtualization of macOS on Apple silicon -- UTM which is only $9.99 and available on the Mac App Store. The latest version also allows virtualization of Linux with support for Rosetta 2 in Linux. (Unfortunately, Linux VMs are highly unstable on base M1 systems, apparently an Apple and/or Linux problem.) When I finally upgrade my mini, I hope to use that feature to run my Alpha VMs faster than my Intel NUC can today.

Not yet ... If you watch @Mikero's presentation at the Arm Developers Forum, he was using a Release Candidate of Fusion 13. He states in the video that the initial release will not support 3D graphics, drag-and-drop or copy-and-paste.

In the Ventura GA, the Settings pane still doesn't offer any additional information if the item is signed. Again, not very helpful. (E.g., it took me quite some time to figure out that the launch items from PhotoMinds LLC are for Arq.) On the other hand, if the item is unsigned (e.g., from a MacPorts port), there's an Info button that opens a Finder window on the executable referenced from the plist. I read somewhere that there's a new API in Ventura to manager background items that avoids the notification and, I believe, also doesn't put the items in the Settings pane.

Another alternative is to run an ESXi server for your old VMs. You can then access them though Fusion on your Apple silicon machine. (When Fusion is released, you'll need a Pro license.) If any of those VMs are macOS, you'll need an Intel Mac. Otherwise, you can setup a small, inexpensive Intel box (e.g., an Intel NUC).

This mechanism is part of Apple's high-level Virtualization framework. VMware uses the low-level Hypervisor framework. It's not clear that there's any way to access Rosetta from the Hypervisor framework. Of course, if anyone can figure out how to get this functionality, it's probably the VMware team. (Yes, I'd like to see it as well.)

I  asked @Mikero on Twitter about this when I first saw the KB article for ESXi. He responded Yah, I helped write it, while throwing up in my mouth the whole while. Frankly, I don't care what the GOS team thinks. They're wrong to drop this. Our customers need this, our own employees need this, and so I'm pushing as hard as I can for a path forward. Because OS validation is centralized, it's a side-effect of no M1 support for ESXi. What the underlying things is saying is that we won't do "VMWARE" VMs for macOS, starting with ESXi. On macOS hosts tho, with Fusion, we have options that are unavailable to ESXi as the Host OS. I'm confident we will figure something out at least for Fusion.

I asked @Mikero on Twitter about this when I first saw a similar article about ESXi. He responded Yah, I helped write it, while throwing up in my mouth the whole while. Frankly, I don't care what the GOS team thinks. They're wrong to drop this. Our customers need this, our own employees need this, and so I'm pushing as hard as I can for a path forward. Because OS validation is centralized, it's a side-effect of no M1 support for ESXi. What the underlying things is saying is that we won't do "VMWARE" VMs for macOS, starting with ESXi. On macOS hosts tho, with Fusion, we have options that are unavailable to ESXi as the Host OS. I'm confident we will figure something out at least for Fusion.

As noted in the Tech Preview Testing Guide, shared folders are not yet supported by the VMware Tools for Windows on Apple silicon. I'm sure VMware is working to add support for that and the other missing features before final release.