NS_ERROR_FAILURE (0x80004005) on Mac VirtualBox

[Ashj89]

Hello,

I've just updated my Mac with MacOS Big Sur 11.0.1. When I try to use any of my VMs through virtualbox I'm presented with the following error:

Result Code: NS_ERROR_FAILURE (0x80004005)
Compontent: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

I have tried reinstalling Virtualbox, reinstalling extensions and discarding saved states for the VMs to no prevail.

Thanks in advance

[mhwill55]

I am experiencing the exact same failure (same error code). In addition, if I create a new VM, it fails as well. So clearly it is not a problem with the VMs themselves.

[cybermario]

Same error here on Big Sur final, on a MBP mid 2012... tried reinstall, restart mbp, create a new virtual machine, nothing works...

Code: Select all

Fallo al abrir una sesión para la máquina virtual kali.

The virtual machine 'kali' has terminated unexpectedly during startup with exit code 1 (0x1).

Código resultado: NS_ERROR_FAILURE (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Hope anyone helps us...

[Steffen M.]

I am experiencing the exact same failure (same error code). In addition, if I create a new VM, it fails as well. So clearly it is not a problem with the VMs themselves.

Do you have SIP disabled (by doing "csrutil disable" in Apple's recovery mode)?

[cybermario]

yes, in my case, SIP is disabled

[mhwill55]

I am experiencing the exact same failure (same error code). In addition, if I create a new VM, it fails as well. So clearly it is not a problem with the VMs themselves.

Do you have SIP disabled (by doing "csrutil disable" in Apple's recovery mode)?

Yes, SIP is disabled so that I can run TotalSpaces2.

I will re-enable SIP and see if that fixes the problem. If it does, then I need to decide with is more important - VirtualBox or TotalSpaces2. Given that it appears that Oracle will not be able to support VirtualBox on the new Apple Silicon chips, this may be the early warning that I should not depend upon VirtualBox for the future.

[cybermario]

I am experiencing the exact same failure (same error code). In addition, if I create a new VM, it fails as well. So clearly it is not a problem with the VMs themselves.

Do you have SIP disabled (by doing "csrutil disable" in Apple's recovery mode)?

Yes, SIP is disabled so that I can run TotalSpaces2.

I will re-enable SIP and see if that fixes the problem. If it does, then I need to decide with is more important - VirtualBox or TotalSpaces2. Given that it appears that Oracle will not be able to support VirtualBox on the new Apple Silicon chips, this may be the early warning that I should not depend upon VirtualBox for the future.

please keep informed if enabling SIP correct the problem.

[Steffen M.]

I will re-enable SIP and see if that fixes the problem. If it does, then I need to decide with is more important - VirtualBox or TotalSpaces2. Given that it appears that Oracle will not be able to support VirtualBox on the new Apple Silicon chips, this may be the early warning that I should not depend upon VirtualBox for the future.

please keep informed if enabling SIP correct the problem.

In my case, VirtualBox 6.1.16 started to work again after re-enabling SIP.

Unfortunately, in this case, I don't have LAN access because ASIX (the manufacturer of the AX88179 chipset of my Thunderbolt-to-GigabitEthernet adapter) does not provide the new form of drivers needed for Big Sur. So I can choose between VirtualBox or LAN - and to switch between them, I have to boot into recovery mode. This is very user-unfriendly and needs to be fixed.

Regards,
Steffen

[granada29]

Unfortunately, in this case, I don't have LAN access because ASIX (the manufacturer of the AX88179 chipset of my Thunderbolt-to-GigabitEthernet adapter) does not provide the new form of drivers needed for Big Sur. So I can choose between VirtualBox or LAN - and to switch between them, I have to boot into recovery mode. This is very user-unfriendly and needs to be fixed.

Yes - I agree it would be good to get fixed. Please contact the maufacturer of your adaptor and ask them to provide a Big Sur compatible driver.

[mhwill55]

please keep informed if enabling SIP correct the problem.

Yes, I can confirm that enabling SIP corrects the problem and all my VirtualBox VMs run just fine. As a double check, I went back and disabled SIP and, as expected, my VirtualBox VMs failed to launch but successfully launched once I re-enabled SIP.

Interestingly, Parallels and VMware Fusion is able to successfully launch their VMs regardless of whether SIP is enabled or Disabled.

[cybermario]

please keep informed if enabling SIP correct the problem.

Yes, I can confirm that enabling SIP corrects the problem and all my VirtualBox VMs run just fine. As a double check, I went back and disabled SIP and, as expected, my VirtualBox VMs failed to launch but successfully launched once I re-enabled SIP.

Interestingly, Parallels and VMware Fusion is able to successfully launch their VMs regardless of whether SIP is enabled or Disabled.

I also confirm that enabling SIP the problem has been solved.

[SchroedersKater]

please keep informed if enabling SIP correct the problem.

Yes, I can confirm that enabling SIP corrects the problem and all my VirtualBox VMs run just fine. As a double check, I went back and disabled SIP and, as expected, my VirtualBox VMs failed to launch but successfully launched once I re-enabled SIP.

Interestingly, Parallels and VMware Fusion is able to successfully launch their VMs regardless of whether SIP is enabled or Disabled.

So someone at Oracle should have a look at this problem. I.e. I need SIP disabled to run TotalFinder.

BTW, it's been working with SIP disabled with macOS 10 Catalina.

[multiOS]

It's been reported on another thread that the latest 'Test Build' available here: https://www.virtualbox.org/wiki/Testbuilds allows VirtualBox to run with SIP disabled. In fact test Builds can only be installed with SIP disabled because they aren't notarised by Apple.

If you don't want to try running a Test Build, then the alternative is to wait for the next official release.

[cybermario]

please keep informed if enabling SIP correct the problem.

Yes, I can confirm that enabling SIP corrects the problem and all my VirtualBox VMs run just fine. As a double check, I went back and disabled SIP and, as expected, my VirtualBox VMs failed to launch but successfully launched once I re-enabled SIP.

Interestingly, Parallels and VMware Fusion is able to successfully launch their VMs regardless of whether SIP is enabled or Disabled.

So someone at Oracle should have a look at this problem. I.e. I need SIP disabled to run TotalFinder.

BTW, it's been working with SIP disabled with macOS 10 Catalina.

yes, in catalina works perfectly, big sur need some improvements or virtualbox adjust to big sur

[SchroedersKater]

It's been reported on another thread that the latest 'Test Build' available here: https://www.virtualbox.org/wiki/Testbuilds allows VirtualBox to run with SIP disabled. In fact test Builds can only be installed with SIP disabled because they aren't notarised by Apple.

If you don't want to try running a Test Build, then the alternative is to wait for the next official release.

Great! Thank's a lot for this information!