Virtualisation on Apple Silicon Macs is different

PlunderBunny an hour ago | parent | next [-]

So if I wanted to run Windows ARM on an Apple Silicon Mac, what's the best option(s) that make full use of the hypervisor? I'm aware of UTM [0] but the second paragraph of the article makes it seem like UTM is a software emulator (that doesn't take advantage of the hypervisor?)

0. https://mac.getutm.app

	▲	chromadon 42 minutes ago \| parent \| next [-]
		Running Windows under UTM on macOS was (and might still be) the fastest way to run Windows on ARM.
	▲	argsnd an hour ago \| parent \| prev \| next [-]
		Parallels and VMware still do implement their own graphics virtualisation (among other things) for Windows and Linux guests on Apple silicon, and in my experience Parallels still works better than the alternatives for Windows.
	▲	dmitrygr an hour ago \| parent \| prev [-]
		UTM does both. hypervisor for ARM, qemu for other archs

▲

epistasis an hour ago | parent | prev | next [-]

What a lovely technical article for those of us that haven't followed it, thanks! I was thinking this might be about how Parallels does not have copy-and-paste for M1-on-M1 macOS-on-macOS virtualization, which is definitely "thinking different" compared to all other desktop virtualization that I have encountered.

▲

w10-1 an hour ago | parent | prev | next [-]

TLDR: macOS virtualization is as fast as native due to hypervisor support, with free but limited driver support thanks to virtio. MacOS guests are limited to 2 at a time, and cannot use iCloud services or log in to the App Store.

Also FYI:

- launch times are fast enough for serverless

- you can restore snapshots for macOS guests but not for Linux

- Apple's open-source container support is built on Virtualization, making it a much more secure option than Docker

What's needs investigating is access to the secure enclave. You can login with an apple ID and use enclave API's; it's not clear if this is emulated or handled using the host enclave with a different scope - i.e., if this presents any security issues. To be conservative, one might avoid logging in using an Apple ID with sensitive information in an automated/CI context.

▲

lostmsu an hour ago | parent | prev [-]

AI slop from the looks of it. The title is a clickbait also.

	▲	sys_64738 7 minutes ago \| parent [-]
		You don't know much about Mac bloggers then.