Virtualising macOS, Linux and Windows on Intel Macs has been relatively straightforward, and device support left to the developer. That won’t work for Apple silicon Macs. This explains what happens, its strengths and limitations as a result.
virtualisation
In Ventura, VM disk performance was poor, with write speeds of 0.7 GB/s. How fast is it now in macOS 26.4, and how does using FileVault affect it? Plus a note on problems with BSIs in VMs.
Do you still need Rosetta to translate Intel code so it runs on Apple silicon? With macOS 26.4, Rosetta warnings will start, telling that it won’t be available for much longer.
Apps supplied through the App Store aren’t signed by their developer, but by Apple. Many now have certificates that have expired. When will they stop running?
What can you do to protect your Mac when a stranger asks you to take a look at a document or app? Two alternatives for doing this is safety, rather than risk being victim to a phishing attack.
Normally, the x.1 update fixes many of the bugs from the first release. But in Tahoe, a crop of fresh bugs have been included. Here are some of them, and how they have arisen.
VMs running 26.1 can’t access iCloud and related services, with no workaround. Finder Services below an item’s thumbnail don’t work.
If your virtualiser allows you to run 2 macOS VMs at the same time, and to give them different MAC addresses, it’s easy to migrate from one to the other as explained here.
macOS VMs can have iCloud, iCloud Drive, Messages, FaceTime, FileVault and many shared folders, but still can’t sign into Apple service like the App Store. But you can resize their VMs.
This new disk image format is claimed to be “efficient and general-purpose”. But is it? Is it as fast as sparse bundles or read-write (UDRW) disk images are?
