Gangmax Blog


[RE]ARM Mac: Why I'm Worried About Virtualization

The orginal post is here. For me, VirtualBox is a must-have. So I don’t think I will buy a ARM Mac if I cannot use VirtualBox on it.

It’s late 2020 and you just got a brand-new Mac with Apple’s own ARM processors. Exciting! But what will development be like?


I would expect about a 5x slowdown running Docker images.

Docker on a Mac utilizes a hypervisor. Hypervisors rely on running the same architecture on the host as the guest, and are about about 1x - 2x as slow as running natively.

Since you’re running ARM Mac, these hypervisors can only run ARM Linux. They can’t run x86_64 Linux.

What will happen instead? These tools will fall back on emulators. Emulators can run a different architecture between the host and the guest, but simulate the guest operating system at about 5x-10x slowdown.

A basic performance test comparing gzip performance on amd64 (hypervisor) and arm64v8 (emulator). Note that the emulator is over 6x slower. On an ARM Mac, the amd64 image will instead be 6x slower.

Why can’t you update the Docker image to also support ARM? You theoretically could switch your backend to run ARM Linux. However, this would take months - renting out ARM instances, re-building all repositories, and a tense switch over. What if your hosting provider doesn’t offer ARM instances with the same system requirements as x86_64? What if you complete this migration and find it runs at half the speed?

Worse, it might be impossible if your images include files downloaded off the internet, as those are often only compiled for x86_64.

An example of a Docker command that will only work on x86_64. PhantomJS does not release an arm build.
While moving your backend to ARM is far from impossible, it’s a serious migration that you shouldn’t take lightly. Getting a new laptop isn’t enough justification to switch your backend architecture.

Another option is to run Docker remotely. You set up an x86_64 Linux server, then allow Docker to connect to it remotely. From then on, all Docker commands instead run on the server. This is also supported in Docker, here is a tutorial on setting it up. This is what heavy Docker users will want to do.


VirtualBox won’t work.

VirtualBox is a hypervisor. Therefore, it won’t be able to run x86 Windows or x86 Linux.

You could use VirtualBox to run ARM Windows. Windows already supports ARM, and has a similar binary translation system to Apple’s, so it can run x86 binaries. However, VirtualBox only supports x86 hosts and guests and is unlikely to be ported by ARM.

VMWare Fusion similarly is a hypervisor that only support x86, but they’re thinking about supporting ARM.

Instead of VirtualBox you might use QEMU, an emulator. However, QEMU is pretty low level and not often used to emulate Windows.

Boot Camp

Boot Camp won’t work.

Boot Camp is an Apple-approved way to dual-boot Mac OS and Windows. Boot Camp will definitely not be available on ARM Macs. It might be added later with the ability to run ARM Windows, though Microsoft would have to approve.

Should I get an ARM Mac?

The point of this post isn’t to say that ARM Mac is a bad idea, but to give a realistic idea of what developing on one would look like assuming nothing changes. It’s possible Apple could release more virtualization tools before the ARM Mac launches.

Should you get an ARM Mac if you’re a developer? If you work largely on frontend, mobile, or native apps, you’ll probably be fine. But if you use virtualization often, I wouldn’t recommend it. There will be a lot of problems early on, and not all of them will have solutions. My biggest concern is getting an ARM Mac and realizing I simply can’t run an essential application on it.

However if you like troubleshooting these issues and are excited about ARM Mac, go for it! My plan is for those kinds of people to fix these issues.

Know something I don’t? Have questions? Email me at