Rosetta 2 is key feature for the transition to Apple silicon, and is also available to run Intel x86_64 binaries in virtual macOS and Linux (in Ventura).
virtualisation
Now feature-complete with support for shared folders with the host Mac, and everything is in place for Rosetta 2 translation of x86_64 binaries within the VM.
Now fully supports shared folders, on Ventura hosts running Ventura in a VM. This gives access to faster storage, and to iCloud Drive as well.
Just 4 cores and 16 GB of memory were used for the virtual machine to run Xcode and build apps successfully, but only for local testing.
Writing to the Data volume in a VM is dismally slow. Is using shared storage any quicker? What happens when you copy a VM to an external SSD, or to another Mac?
Some threads are set to run in the background, and get allocated to the E cores. Could you run them in a VM, and effectively promote them to run on P cores instead?
How lightweight virtualisation of macOS and Linux has improved in Ventura, and what hasn’t changed.
Virtual CPU cores are of one type, and QoS has no effect in virtualised macOS. This has consequences for both the host and guest macOS.
A popular insurance when upgrading to a new version of macOS: how to keep your Mac running both Monterey and Ventura. Covers all models including M-series.
Running Linux on an Apple silicon Mac may now be straightforward, but it presents challenges for installation and management.
The Eclectic Light Company 