Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

1) Can I run VirtualBox on M1 (yet)? 2) What is the overhead of doing so with Rosetta2 vs native on Intel? 3) What is the situation with VT-X?



1) VirtualBox is strictly x86_64 only, everywhere.

3) Arm virtual machines only. For now, Parallels has a preview that you can enroll to at https://www.parallels.com/blogs/parallels-desktop-apple-sili... or you might use https://github.com/kendfinger/virtual which uses the high level Virtualization.framework, for Linux VMs.


Benchmarks show M1 with Rosetta2 beats previous Mac iterations in Cinebench benchmark. See page 2 here https://www.anandtech.com/show/16252/mac-mini-apple-m1-teste...

>> What’s notable is the performance of the Rosetta2 run of the benchmark when in x86 mode, which is not only able to keep up with past Mac iterations but still also beat them.


There currently isn't any kind of useful virtualization available for Apple Silicon, and my hunch is that there won't be until ARM becomes more relevant in the Windows/Linux space.

The way Apple Silicon runs x86 apps through translation makes virtualising x86 systems either impossible or at least extremely difficult.


The answer to all three of your questions is "If you are worried about this, absolutely do not buy an M1 Mac." Rosetta 2 cannot magically turn VirtualBox from a virtualization management system into a high-performance x64 emulator. The long-term solution is probably going to be running ARM Windows or Linux in a VM and leaning on Rosetta-style compatibility/translation in the client OS to run x64 programs.

Edit: Since this is attracting downvotes, maybe it needs some clarification. The things OP asked about fundamentally cannot work. Rosetta 2 is designed exclusively for user-mode programs and cannot cooperate with virtualization software to run arbitrary OSes in VMs. VirtualBox has no plans to port to ARM and will not work in Rosetta. None of this is negativity or cynicism towards M1 Macs - it's just the reality of how switching architectures affects virtualization. If your use case for Mac hardware is to run arbitrary x64 code at high speed in VMs, you should not buy an M1 Mac because that capability does not currently exist.


Yeah, I figure the only realistic solution for my work needs (running a bunch of x86/x64 Windows VMs) is to do that remotely on a Windows workstation.

I probably won't buy an M1 anyway, but I'll be extremely interested to see what everything looks like when the M2 rolls around.


You may be interested in this thread:

https://forums.virtualbox.org/viewtopic.php?f=8&t=98742

tl;dr: VirtualBox is an x86/x86 hypervisor, there's no porting to do. It would be a re-write.


Thanks all




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: