Re: Big Sur Host Issues
Posted: 13. Nov 2020, 17:20
Yes. I am already add Oracle to trust extension + make full disk access for VBox but problem not resolve
I upgraded today and getting the exact same problem, tried reinstalling but no joy.Prosperot wrote:It gives this message:
Kernel driver not installed (rc=-1908)
Make sure the kernel module has been loaded successfully.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
This worked for me in Big Sur. In the General tab of the Security & Privacy preferences, there will be a button near the bottom (but above the lock icon). You will probably need to unlock the UI with the admin password, and then click the button to see the apps that need attention. A new window will pop up confirming a reboot. Accept the reboot and the changes will be applied when the restart is completed. It's a lousy UX, but it worked.estamos wrote:1. Uninstall VirtualBox using VirtualBox_uninstall.tooljimstrong wrote:Managed to open VirtualBox, but got the following when starting a virtual machine:-
The virtual machine 'Windows 10 Pro' 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}
2. Clean install VirtualBox using VirtualBox.pkg
3. At the end of the install, go to System Preferences, Security and Privacy, and the click the allow button
This should solve your issue .
Can't seem to find it on mine, I unlock the padlock and above that all as I have is Allow apps downloaded from : App Store or App Store and identified developersjared_ wrote:This worked for me in Big Sur. In the General tab of the Security & Privacy preferences, there will be a button near the bottom (but above the lock icon). You will probably need to unlock the UI with the admin password, and then click the button to see the apps that need attention. A new window will pop up confirming a reboot. Accept the reboot and the changes will be applied when the restart is completed. It's a lousy UX, but it worked.estamos wrote:1. Uninstall VirtualBox using VirtualBox_uninstall.tooljimstrong wrote:Managed to open VirtualBox, but got the following when starting a virtual machine:-
The virtual machine 'Windows 10 Pro' 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}
2. Clean install VirtualBox using VirtualBox.pkg
3. At the end of the install, go to System Preferences, Security and Privacy, and the click the allow button
This should solve your issue .
Unrelated to this exact problem, but turned out to be the next roadblockL: The next step for me was to install the extension pack to allow USB3 for my Windows guest. Then everything worked as expected.
In my case, it appeared after a restart (although the VirtualBox installer does not require it). After clicking the button a second restart is needed. After that, VirtualBox seems to function normally.Can't seem to find it on mine, I unlock the padlock and above that all as I have is Allow apps downloaded from : App Store or App Store and identified developers
Code: Select all
csrutil clear
reboot
Code: Select all
csrutil enable --without debug --without fs
Thank you, vbox_tom!vbox_tom wrote:For me none of the solutions above worked.
But what works (tested twice) is booting to recovery (cmd+R) and enabling all components of sip.
Open Terminal in Recovery and type:Then uninstall and re-install virtualbox.Code: Select all
csrutil clear reboot
If needed go to System Preferences - Privacy - General and accept the extensions.
Code: Select all
sudo kextstat | grep -i virtualbox
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
187 3 0xffffff7fa156a000 0xb2000 0xb2000 org.virtualbox.kext.VBoxDrv (6.1.16) DAF044F0-5043-3B8E-8758-5A462567BDAA <8 6 5 3 1>
189 0 0xffffff7fa1647000 0x5000 0x5000 org.virtualbox.kext.VBoxUSB (6.1.16) CA33FA52-5933-3F0E-9B40-8B1ECF4D6A36 <188 187 65 8 6 5 3 1>
190 0 0xffffff7fa1642000 0x4000 0x4000 org.virtualbox.kext.VBoxNetFlt (6.1.16) C93EAF6A-676F-3370-BAE2-BDFD2BF16582 <187 8 6 5 3 1>
191 0 0xffffff7fa163c000 0x2000 0x2000 org.virtualbox.kext.VBoxNetAdp (6.1.16) 76200407-D2F0-3D84-BCCF-7EEA18F16654 <187 6 5 1>
Code: Select all
csrutil clear
reboot
That also worked for me!davnozdu wrote:Many thanks
Command fix my problem, now VBox workCode: Select all
csrutil clear reboot
It worked for me, so really, *REALLY* thank you!vbox_tom wrote:For me none of the solutions above worked.
But what works (tested twice) is booting to recovery (cmd+R) and enabling all components of sip.
Open Terminal in Recovery and type:Then uninstall and re-install virtualbox.Code: Select all
csrutil clear reboot
If needed go to System Preferences - Privacy - General and accept the extensions.
Worked perfectly here as well - THANK YOU!!!! I did / do have the issue where it's worked flawlessly with bridged networking before, won't work with it now after various attempts. It works just fine with NAT though so a non-issue. Running both a Windows 10 VM and an Ubuntu Linux v20 VM - both with guest additions.vbox_tom wrote:For me none of the solutions above worked.
But what works (tested twice) is booting to recovery (cmd+R) and enabling all components of sip.
Open Terminal in Recovery and type:Then uninstall and re-install virtualbox.Code: Select all
csrutil clear reboot
If needed go to System Preferences - Privacy - General and accept the extensions.