Nested Virtualization on Apple Silicon

Discussion in 'Parallels Desktop for Mac Feature Suggestions' started by, Oct 17, 2022.

  1. Member

    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 ???
    computeronix, MarkB30 and MatthewR20 like this.
  2. MarkB30

    MarkB30 Bit poster

    Please work on nested virtualization on Apple Silicon devices for Parallels Desktop 19. Windows 11 ARM64 runs great but WSL2 support is missing because of nested virtualization missing.
    ibefindia and MatthewR20 like this.
  3. computeronix


    +1 need nested virtualization for M2 and Windows 11 so Sandbox // WSL2 // Hyper-V // VirtualBox // etc
    MatthewR20 likes this.
  4. Юрий_Трухин

    Юрий_Трухин Bit poster

    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!
    ScottE7 likes this.
  5. Mikhail Ushakov

    Mikhail Ushakov Parallels Team

    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 ;)
  6. mixodett

    mixodett Bit poster

    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.

Share This Page