top | item 40642328

macOS 15.0 supports Nested Virtualization on M3 chips

138 points| zshrc | 1 year ago |developer.apple.com

135 comments

order

walterbell|1 year ago

Asahi Linux supports nested virtualization on Apple Silicon M2, where the feature is present in the chip, but not exposed by macOS.

MaxikCZ|1 year ago

I was shopping for a phone some time ago. iP14 Pro had always-on display while non-Pro version didnt. Apple justified it by non-Pro having lcd, while Pro having Oled.

Next year iP15, both non-Pro and Pro have Oled, but again only Pro has always-on display.

Honestly that is the reason I am still on my Note9, and looking for another Android.

I understand what product segmentation is, and probably I am minority, but damn, it feels like subscription-based heated seats.

jbverschoor|1 year ago

Yeah, it’s just another artificial limitation to get people to buy a newer laptop. They hit the devs where it hurts

whatever1|1 year ago

And ipadOS not even one layer of Mac virtualization

albertopv|1 year ago

And never will (probably), Apple has been clear for years about market segmentation.

justinclift|1 year ago

It'd be super useful if Asahi Linux worked on iPads. :)

dehrmann|1 year ago

Servers aren't really Apple's thing, so it hasn't been much of an issue, but isn't this something Intel CPUs have supported for almost two decades?

thesquib|1 year ago

Came here to say the same thing

nailer|1 year ago

Anyone have a practical case for this? Not complaining just wondering.

saurik|1 year ago

CI systems often run their workloads in virtualization (for both security and ease of uniform deployment), but sometimes the jobs themselves use a VM to either run part of the build process (such as depending on a tool distributed using Docker, which relies on such due to the host kernel not being Linux) or run some of the unit/integration tests (whether to create a clean environment or to take advantage of the hypervisor to get fast emulation of a target device, such as an Android phone or whatever). Without nested virtualization, services such as GitHub Actions (or locally hosted options; FWIW, GitHub also lets you bring your own "runners") have thereby been somewhat crippled on Apple Silicon.

jborean93|1 year ago

Nested virtualization would be needed if you want to test out a Windows VM with the various Hyper-V integrations like WSL2, credential guard, etc.

justinclift|1 year ago

Docker containers (ie Docker Desktop) running inside macOS VMs.

That would fix a current blocking problem, as the lack of nested virtualisation means Docker Desktop (which runs its containers inside a Linux VM) has to run on the host and can't run inside a VM.

gilgoomesh|1 year ago

Running an older version of macOS, which supports older versions of Xcode and then using that to run older iOS simulators.

tonymet|1 year ago

Inception

JayDustheadz|1 year ago

I'm not a super-advanced user, so could somebody please let me know if this will allow running Windows on an ARM based Macs? Or perhaps running a VM with macOS Big Sur on macOS 15 ( I'm looking to install a specific version of an app via App Store - a version that is limited to macOS Big Sur )? Thanks in advance!

wobfan|1 year ago

You can already run Windows on Macs, just look at UTM or Parallels. You can also already run Big Sur on macOS 14.

Edit: Should've added that you can only run Windows ARM. Emulating x86 on ARM (= running "normal" Windows on macOS M-processors) may be possible (I'm not sure), but practically not usable as it will be painfully slow. That will probably not change in the near future. However Windows ARM contains a Rosetta-like x86 emulation layer so with some luck you won't even notice that you're running Windows ARM and not "normal" Windows.

taran_narat|1 year ago

I’m even less, what’s nested virtualisation?

vbezhenar|1 year ago

Still no USB Passthrough it seems. It's a pity.

littlecranky67|1 year ago

That is something that Parallels traditionally had for x86, isn't it also the case for Parallels with Windows on ARM?

saagarjha|1 year ago

That's up to the virtualization solution you're using.