I understand this is non-trivial, what with the host OS adding roadblocks these days to software accessing the raw partitions, and with the increasingly complex volumes of a guest Mac OS X install, but I believe this would be useful as a standard configuration. So that is why virtualizing a Mac OS X partition ought to be considered a major use case. So for that purpose, it needs to have its own partition, not a disk image.

with network debugging).īut, you might sometimes want to boot that daily driver directly for whatever reason, e.g. browse the web), where they can be used to monitor and debug the virtualized OS (e.g. That is, use Mac OS X in a VM guest as your daily driver, and install the tools in the Mac OS X host (where on the other had you never e.g. Reactions: Patrick, AMDPUSH and AudioGod. The only significant barrier you can put is to install these tools beyond the virtualization barrier. Install macOS Big Sur on Ryzen with VMware Workstation and OpenCore - Ken5998/OpenCore-VMware-Workstation-AMD. installing in non-standard locations, etc.), but ultimately it would only result in malware applying smarter checks that you would not know how to fool. So how can I fulfill that role, while still installing the developer and other monitoring tools that would signal me to malware as someone to avoid? You could try obfuscating your installs (e.g. I firmly believe that the Mac community should rely as little as possibly on the anti-virus vendors to monitor threats: it’s part of our jobs as developers. It is designed completely from the ground up for the new style introduced in Big Sur. I am very interested in such a functionality as well (I will let you know how successful I eventually get), and if anyone’s listening, I will tell you why.įlashback (more specifically, OSX/Flashback.I) has been a wakeup call in many ways in the Mac community and among the alarms, there was the one bit about the malware attempting to detect whether any of some specific kind of software was present on the system up for infection as a sign that it belonged to someone who should not be messed with: anti-viruses beyond the mainstream, network activity reporters, and most significantly, the optional development tools. I also have no idea how macOS will react if you first boot into a VM and next up boot it physically again. Note however that current macOS will prevent you to access that disk so you will have to muck around with macOS security settings in order to be able to get access to that partition.įinally be aware of the limitations (you cannot -should never- suspend that VM or use snapshots with it) If you do want to do this then you would want to use raw disk mapping for your partitions and you should be looking at something like this: So it is not as interesting for VMware to provide an easy click and point way of being able to do this. IOW there are only a few possible configurations with 1 bootcamp VM.īesides that the bootcamp configuration is one that is very commonly used in a business settings whereas the business case for being able to run multiple macOS versions is much less common. I did test this observation with a few other colleagues who have different revisions of Apple Intel hardware and the issue was the same so I don't believe this is hardware dependent.It is probably possible, but with bootcamp the way it is configured is much more constrained. Big Sur in guest also continues to work fine. I can confirm that 12.0, 12.0.1, 12.1 in the Guest with any version of Monterey up to 12.3.1 on the Host still work fine. For example, when opening Photos, the full screen view is blank. I used these guest VMs somewhat sparingly so its possible it broke with 12.2 but I don't have a guest at that level to verify at moment. Let me rephrase: The host is Monterey OS 12.7.1, the VMWare version is 13.5.0, yet it appears that 3D acceleration for the OS10.14 Mojave virtual machine is not working. That support also worked with Big Sur Host/Monterey Guest and subsequently Monterey Host/Big Sur Guest, and Monterey Host/Monterey Guest.įor sure starting with 12.3 and remaining the same with 12.3.1 3D acceleration in the Monterey Guest (Host version doesn't seem to matter) is pretty broken to the point that simple scrolling operations will not only work without significant delays but even typing in a browser window can be a 5 second delay character to character.

I have used the experimental macOS 3D acceleration since announced via blog post starting with Big Sur Host/Big Sur Guest. Fellow members I wanted to post an observation to see if others might have noticed the same before, I report more formally to VMware.

Vmware macos big sur 3d acceleration