M4 Macs Unable to Run macOS VMs Earlier Than Ventura 13.4

Monday November 18, 2024 1:34 am PST by Tim Hardwick

New M4-based Macs are reportedly unable to run virtual machines of older macOS versions prior to macOS Ventura 13.4, according to user reports and developer findings.

According to an in-depth write-up by the Eclectic Light Company's Howard Oakley, security researcher Csaba Fitzl highlighted the issue, which has been documented in Apple Feedback and affects popular virtualization software including UTM. When attempting to run a virtual machine with an earlier version of macOS on M4 Macs, users encounter a black screen, and the VM fails to boot entirely.

The limitation appears to occur during early kernel boot processes, as indicated by Activity Monitor showing only one active virtual core despite multiple cores being allocated. This suggests the failure happens before the VM kernel can initialize additional cores.

The limitation is not an issue on M1, M2, and M3 Macs, all of which can successfully run VMs of macOS Monterey (12.0.1) and later versions (with some limitations), though Big Sur virtualization was never supported on Apple silicon Macs.

For users who rely on older macOS versions in virtual machines for testing or compatibility purposes, this limitation may be an important consideration before upgrading to M4-based Macs. Currently supported macOS versions for virtualization on M4 Macs include:

macOS Ventura 13.4 and later
macOS Sonoma 14
macOS Sequoia 15

Given the nature of the issue occurring early in the boot process, Oakley reports that a fix would likely require Apple to release updated IPSW files for older macOS versions, which would be unprecedented for the company, perhaps making it unlikely.

The restriction adds to existing virtualization limitations on Apple silicon Macs, such as the inability to run App Store applications in VMs. Apple did however introduce a notable enhancement to its virtualization framework in macOS Sequoia by enabling Mac users to sign into iCloud within macOS VMs.

Apple in October unveiled new M4 powered versions of its iMac, Mac mini, and MacBook Pro models. For more information on the virtualization issue, be sure to read Oakley's informative write-up.

Tag: M4

Top Rated Comments

anshuvorty

25 months ago

Just add yet another wrinkle to the addage or user experience where macOS isn't really a legacy OS or an OS that supports legacy usage; it isn't like Windows where the UI might be modern and pretty but still allows for decades and decades of older software to run quite nicely; on macOS, you are lucky if you can run anything older than 2-3 years...this is yet another example of that.

So, I am not really surprised at this development; Apple wants its users and its developers to constantly be on the cutting edge in terms of hardware and software. If you want Unix/Linux legacy compability, macOS isn't where you will find it, you will be better off using an Open Source Unix/Linux OS instead...

Score: 31 Votes (Like | Disagree)

Trusteft

25 months ago

Seeing the fantastic Apple operating system (and computers) turn into a mobile phone OS, few years at a time. Meh.

Score: 28 Votes (Like | Disagree)

Populus

25 months ago

Just add yet another wrinkle to the addage or user experience where macOS isn't really a legacy OS or an OS that supports legacy usage; it isn't like Windows where the UI might be modern and pretty but still allows for decades and decades of older software to run quite nicely; on macOS, you are lucky if you can run anything older than 2-3 years...this is yet another example of that.

So, I am not really surprised at this development; Apple wants its users and its developers to constantly be on the cutting edge in terms of hardware and software. If you want Unix/Linux legacy compability, macOS isn't where you will find it, you will be better off using an Open Source Unix/Linux OS instead...

Apple has a completely different policy regarding legacy software and code than Windows, I’d even say they’re opposites.

This has it’s negative side, but also (in my humble opinion), it also has some benefits.

We were all surprised by how quick and graceful was the adoption of the new ARM64 architecture by developers, while on Windows the transition to ARM is way slower.

Also the big quantities of old code on Windows, and I’m not talking 6-7 years old but even older, might make it less efficient. And there’s the problem of the inconsistency of the UI across the system, something that macOS isn’t free of, but offers a much more cohesive and consistent experience.

As I said, I don’t think Apple cutting support of devices or apps so quickly is absolutely a good thing, and I think they should provide more legacy support from now to all Apple Silicon machines, including the M1. But cutting the cord to old (7+ years), useless code, is beneficial for the platform efficiency.

Score: 15 Votes (Like | Disagree)

cjsuk

25 months ago

Just add yet another wrinkle to the addage or user experience where macOS isn't really a legacy OS or an OS that supports legacy usage; it isn't like Windows where the UI might be modern and pretty but still allows for decades and decades of older software to run quite nicely; on macOS, you are lucky if you can run anything older than 2-3 years...this is yet another example of that.

So, I am not really surprised at this development; Apple wants its users and its developers to constantly be on the cutting edge in terms of hardware and software. If you want Unix/Linux legacy compability, macOS isn't where you will find it, you will be better off using an Open Source Unix/Linux OS instead...

You’re no better on windows. There are tonnes of broken APIs. And definitely not on Linux. Try dealing with .so hell.

The only reason they appear to work better is because most windows apps that rely on broken APIs are full of if statements and crap. I’ve written enough in my time. And on Linux the tested configuration is at distribution level so someone has done that legwork. There are plenty of problems in the periphery. And let’s not forget the old ELF switch over of course.

I would be surprised if you can get any Linux stuff that is not just talking to kernel API/ABI to actually work after 4-5 years. Especially GTK/Qt stuff. Unless you static link the entire thing.

Score: 14 Votes (Like | Disagree)

jlc1978

25 months ago

On ios after upgrading Apple teases you with a little cloud icon of abandoned apps. You can‘t copy the app over from the old to new device so you eventually lose them.

IMHO, that's as much a developer issue as an Apple issue. OS's evolve and things get deprecated over time, and if developers want to continue to stay in business they need to adapt their apps; especially if they use undocumented features. If an OS is designed to maintain 100% backward compatibility it would rapidly become a mess; although I think OS developers should work to ensure established API functionality remains available for a reasonable amount of time.

I personally I’m not interested in running older OS, and if I need to, I have an old 2014 Mac mini sleeping and connected to the local network ready to be awaken from my new M4 Mac mini. But I can understand there might be cases where an older version might be needed.

I would think, if running on older hardware is mission critical, you have it around to be used as test mules. I do that with an Intel MBA, for example.

Score: 11 Votes (Like | Disagree)