I am running VirtualBox but get the error NS_ERROR_FAILURE (0x80004005) on an MacBook Pro 2020 with an M1 chip

I have tried everything uninstalling Virtualbox, enabling SIP in recovery mode, installing the Virtualbox again. Only thing I haven't tried is allowing Oracle in Privacy --> General since I don't see it there.

The following is the exact log I get.

Result Code: 
NS_ERROR_FAILURE (0x80004005)
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
  • What version of macos and Virtualbox - but basically if an app does not work on a clean install then best to ask their support
    – mmmmmm
    Apr 27, 2021 at 20:02
  • 11.3 macos and virtualbox 6.1
    – dtomicic
    Apr 28, 2021 at 9:31
  • And you are on an Intel machine? and which version of 6.1 - 6.1.20 is the latest
    – mmmmmm
    Apr 28, 2021 at 9:51
  • Sorry for the broad answer I was distracted didn't even realize I didn't give out enough info. Mac is MacBook Pro 2020 with an M1 chip and the version is 6.1.20
    – dtomicic
    Apr 28, 2021 at 10:35
  • Try adding the kext bundles when you start your mac. sudo kextload -b org.virtualbox.kext.VBoxDrv; sudo kextload -b org.virtualbox.kext.VBoxNetFlt; sudo kextload -b org.virtualbox.kext.VBoxNetAdp; sudo kextload -b org.virtualbox.kext.VBoxUSB;
    – akr_
    Nov 19, 2021 at 19:48

2 Answers 2


Virtualization only works when running the same CPU on the server and the VM.

Currently out of the 3 main VMs only Parallels has a release for the M1 and that can only run ARM based operating system e.g. Linuxes and a pre release Windows. That Windows can run Intel Windows executables. Vmware have announced they are working on a version for ARM. I don't think Oracle have said anything for VirtualBox

There are other emulators that can run Intel executables on the M1. Crossover (and thus I suspect wine) can run Windows Intel binaries. Qemu can emulate and virtualise so can run Intel CPU bases OSs on an ARM machine.

Rosetta2 can run Intel binaries on Apple M1 but not all. Virtual machines need very low level support from the CPU and kernel that Rosetta cannot provide - so that is why you get that error.

  • So basically no other way to use virutalbox until they add the support, alright thanks for your help.
    – dtomicic
    Apr 28, 2021 at 13:43

I know it's been 2 years since this has been asked but in case someone comes here for the same solution I needed, this is what I did to fix mine:See logs

My vm was converted from vmware to ovf and imported to virtualbox. after the the import, it didn't start. In the logs, I saw it was complaining about nvme so from the settings I went to storage tab and removed nvme controller. It was fine after that. enter image description here

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .