You might have noticed that in the pre-release Mac OS Hosts discussion was resolved by people discovering that on Big Sur, it seems VB now *requires* SIP to be enabled. Here's the discussion in question: (I can't seem to link , but it's the last page of the topic titled 'Big Sur Host Issues' on the pre-release Mac OS Hosts forum.)
This is an issue because in my case, I have another tool that requires SIP to be disabled, so I have to keep it disabled. However, that makes VB not work. The error is below. All the kexts are loading just fine both when SIP is enabled and disabled. By simply enabling or disabling SIP, I can switch from a working to a non-working state and vice versa. To be super clear, this is different from the 'VB doesn't work when SIP is enabled' issues I've seen on the forums. I'm seeing the exact opposite: VB *only* works when SIP is enabled. It does not work when SIP is disabled.
I have also replicated this behaviour on my iMac Pro and on my Macbook Pro as well. They both behave the same. SIP disabled means Virtualbox will fail with the exact same error below on both machines.
The SIP permission that appears to make a difference is the fs permission, so a custom SIP config where eveything else is enabled, but SIP Filesystem protection is disabled
Code: Select all
csrutil enable —without fsI'm running:
VB: Version 6.1.16 r140961 (Qt5.6.3)
Mac OS Big Sur: 11.0.1 (20B28)
This is not a beta or an otherwise developer-only release, this is the current, public version of Mac OS.
Code: Select all
The virtual machine '[redacted]' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}