Nested Virtualization on Apple Silicon

I simply do not understand why nested hypervisors are not supported in the ARM M1 version yet.

Also please add AlmaLinux and/or RockyLinux to the installation list.

Finally when can we expect Parallels Tools to work on Alma and/or Rocky ???
 
Finally, macOS 15 introduces support for Nested Virtualization!
THANK YOU, Apple!!!

Now, for developing WSL2 support and building cloud sandboxes with virtualization within virtual machines, a separate computer will no longer be needed!

I've been waiting for this since the introduction of Apple Silicon processors, checking for this feature every release, and now the API is finally here!

I'm looking forward to the Parallels Desktop update more than ever!
https://developer.apple.com/documen...tedvirtualizationenabled?changes=latest_minor
 
hi everyone!
Would you help us, and answer the following question: what use case would be unlocked for you if WSL2 was supported? Why is creating a Linux virtual machine not an option for you?
Thank you in advance ;)
 
I hope for better file system I/O performance as claimed in this video (4 years old and probably Intel-related while I'm running Parallels on recent ARM Mac, but probably still applicable in general):

There's some unrelated stuff, but:

1:09 WSL2 has faster I/O performance, 3-6 x
2:39 unzipping a tar ball under WSL2 can be 20 x faster
10:13 architectures
WSL1: translation-based (translate Linux system call to Windows system calls)
WLS2: virtualization-based, lightweight utility VM, Windows hypervisor layer

Given that, I actually don't understand your question "Why is creating a Linux virtual machine not an option for you?". WLS2 is exactly that.

My problem: I can create a 3 GB tar ball (not compressed, I'm focussing on I/O here) under macOS in < 8 seconds. Tarring the same directory tree copied to a Windows file system takes about 10 minutes(!), regardless of using Cygwin tar (x86-64, no ARM port available, probably suffering from the same system call mapping as WSL1) or Linux tar under WSL1. This is a nightmare (75 times - not percent - slower), of course, and that's why I'm looking forward to WSL2 support.
 
Юрий_Трухин said:
Finally, macOS 15 introduces support for Nested Virtualization!
THANK YOU, Apple!!!

Now, for developing WSL2 support and building cloud sandboxes with virtualization within virtual machines, a separate computer will no longer be needed!

I've been waiting for this since the introduction of Apple Silicon processors, checking for this feature every release, and now the API is finally here!

I'm looking forward to the Parallels Desktop update more than ever!
https://developer.apple.com/documen...tedvirtualizationenabled?changes=latest_minor
Click to expand...

This property appearance doesn't necessarily mean support for nested virtualization on ARM64. Nested virtualization has been supported on Mac OS in Parallels for quite a while. So this property can just mean that MacOS's built-in hypervisor supports enabling nested virtualization (e.g. on Intel processors). But it still may be unsupported on Apple Silicon.
 
Mikhail Ushakov said:
hi everyone!
Would you help us, and answer the following question: what use case would be unlocked for you if WSL2 was supported? Why is creating a Linux virtual machine not an option for you?
Thank you in advance ;)
Click to expand...
Using WSL2 is simply way more straightforward and flexible. It's obviously easier to setup Docker only on Windows machine, when most things are installed and configured automatically, and resources usage is minimized. Installing a Linux vm with docker service, configuring network, and especially files mappings is so much additional work! Take for instance .Net development under Visual Studio - VS maps folders with source code and debugger into a WSL2 docker container easily and automatically, because WSL2 is well integrated with Windows. But when using separate VM, will this mapping work that easily (if at all)?
Also, nested virtualization is not only about Docker. It's also emulators and Windows Sandbox.
 
Andriy S. said:
This property appearance doesn't necessarily mean support for nested virtualization on ARM64. Nested virtualization has been supported on Mac OS in Parallels for quite a while. So this property can just mean that MacOS's built-in hypervisor supports enabling nested virtualization (e.g. on Intel processors). But it still may be unsupported on Apple Silicon.
Click to expand...
My bad, they actually state in the property docs: "Nested virtualization is available for Mac with the M3 chip, and later.". So at least in MacOS hypervisor it's supported on newest Macs. Still unclear when to expect this with Parallels...
 
Mikhail Ushakov said:
hi everyone!
Would you help us, and answer the following question: what use case would be unlocked for you if WSL2 was supported? Why is creating a Linux virtual machine not an option for you?
Thank you in advance ;)
Click to expand...

I use Visual Studio Code for DevOps work on Windows and rely on the Windows Subsystem for Linux (WSL). I hope this answers your question!

Additionally, why is such a basic support option missing? Users shouldn't have to request it themselves, especially when Microsoft only officially supports Parallels as a platform.
 
Andriy S. said:
My bad, they actually state in the property docs: "Nested virtualization is available for Mac with the M3 chip, and later.". So at least in MacOS hypervisor it's supported on newest Macs. Still unclear when to expect this with Parallels...
Click to expand...
There may be hope then with M3 and parallels App Store edition if the APIs are allowed in the App Store side of things with Apple + Parallels? :) - great find!
 
I don't understand these forums. We are in the "feature suggestions" forum, but this item can't be voted on? Well here's my +1 -- been long enough for Apple to finally support this, now Parallels needs to catch up asap! UTM seems to be getting there already...
 
On my Intel Mac (using Windows via boot camp), I use remote testing in Visual Studio to check my code works correctly on Linux via WSL2. I am wanting to use this workflow on an Apple Silicon Mac via a virtual Windows machine.
 
Mikhail Ushakov said:
hi everyone!
Would you help us, and answer the following question: what use case would be unlocked for you if WSL2 was supported? Why is creating a Linux virtual machine not an option for you?
Thank you in advance ;)
Click to expand...
I use parallels for software compatibility in one virtual machine for school. There's one piece of software that runs best on windows, so I use a Parallels Windows VM. The other runs on Windows x86 or Linux ARM. I set it up via WSL1 (would have been a lot easier with WSL2 thanks to WSLg) but I couldn't get USB passthrough working since that was only a WSL2 feature.
 
i had exactly the same problem about six months ago. i didn't solve the problem then. Now i am happy that i have come along to your page and seen all these awesome comments. thank you all ;)
 
Almost a year has passed and Parallels still doesn't support nested virtualization in Apple's Hypervisor Framework (in particular for WSL 2) -- that's extremely disappointing. Have Parallels simply switched to QEMU like UTM and are just waiting for the framework to add the feature? Either way, I'm ready to drop the product if support doesn't arrive very soon. Without it I can't run Docker on Windows properly in a VM without hacks and WSL 2, which hurts the quality of my own product. Right now I have to carry several computers in my backpack every day because Parallels still hasn't implemented this single option. Very sad...

P.S. If you have a beta where the option works, please release it -- I need it badly.
 
You must log in or register to reply here.
Back
Top