Request/Question: (macOS 15) Nested virtualization for Windows ARM and MacOS guests?

[oscarbg]

Hi,
In utm 4.6 beta says:
(macOS 15) Nested virtualization for Linux” but since it’s a hypervisor feature why not supported also for windows arm vm’s for wsl2 support..
It’s a qemu 9.1 limitation or apple virtualization limitation?
Expected to be supported soon via MacOS 15.x update or UTm update?
Thanks..

[osy]

We need QEMU to support it for Windows. As soon as support is added, we will pick it up.

[just4id]

We need QEMU to support it for Windows. As soon as support is added, we will pick it up.

Great! I'm also waiting support for WSA on Windows ARM and wish this would be added too. I'd like to appreciate you guys for my newly buying M4 Mac Mini!

Thanks.

[oscarbg]

thanks @osy! is there an issue/feature request open on Qemu gitlab for tracking the status?

[osy]

I don't know

[oscarbg]

thanks! expanding the issue to request/ask also about MacOS guest nested support..
seems not available using M4 and UTM 4.6.1 on Macos guest 15.1 image..

Virtualization is not available on this hardware

more context:

tested installing lima and get:

INFO[0089] [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/obgutm/.lima/default/serial*.log") 
FATA[0090] exiting, status={Running:false Degraded:false Exiting:true Errors:[] SSHLocalPort:0} (hint: see "/Users/obgutm/.lima/default/ha.stderr.log") 

cat .lima/default/ha.stderr.log

{"level":"fatal","msg":"Error Domain=VZErrorDomain Code=2 Description=\"Invalid virtual machine configuration. Virtualization is not available on this hardware.\" UserInfo={\n    NSLocalizedFailure = \"Invalid virtual machine configuration.\";\n    NSLocalizedFailureReason = \"Virtualization is not available on this hardware.\";\n}","time":"2024-11-24T00:18:49-08:00"}

[osy]

I don't think Apple enabled it for macOS guests

Is there anything new on this request? @osy?

[osy]

Don't ask me ask Apple

[AndreasKunar]

IMHO its not an Apple hypervisor issue, just a virtual machine monitor thing, which means, that in theory, you could replace it and still remain app-store compliant. Parallels did replace both for their Intel-Mac nested hypervisor support, but for Apple Silicon, you have to use Apple's hypervisor. The virtual-GPU feature of Vulkan in Podman containers for Apple silicon also IMHO uses a custom VMM.

[osy]

We are talking about macOS guests. Hypervisor.framework does NOT work to boot macOS. Virtualization.framework is what is used and it does not support nested virt for macOS.