Vagrant: macOS Big Sur 11.0.1 cannot execute vagrant up

[XanxusVerVR]

This happened when I upgraded macOS to Big Sur.
Vagrant could not start the VM, even if I upgraded both Vagrant and VirtualBox to the latest version...

Vagrant version

Vagrant 2.2.13

VirtualBox version

6.1.16 r140961 (Qt5.6.3)

VirtualBox Extension Pack version

6.1.16

Host operating system

macOS Big Sur
11.0.1(20B29)

Guest operating system

centos 7

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.define "master1" do |master1|
    master1.vm.box = "centos/7"
    master1.vm.hostname = 'k8s-master1'
    master1.vm.define vm_name = 'master1'
    master1.vm.network :private_network, ip: "10.1.7.152"
    master1.vm.provider :virtualbox do |v|
      v.customize ["modifyvm", :id, "--cpus", 2]
      v.customize ["modifyvm", :id, "--memory", 4096]
      v.customize ['modifyvm', :id, '--nicpromisc1', 'allow-all']
    end
  end
end

Debug output

https://gist.githubusercontent.com/XanxusVerVR/cd06edba6159ee99f6460ab5eb966db8/raw/6bce3d437e9a062c348f4fa9d40a9ffe6d75f796/vagrant.log

Expected behavior

It should be able to start the CentOS VM.

Actual behavior

When I executed vagrant up, the following error message came out:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp

Steps to reproduce

1. macOS upgraded to Big Sur version 11.0.1
   Install or upgrade Vagrant 2.2.13 version
   Install or upgrade VirtualBox 6.1.16 version
   Install or upgrade VirtualBox Extension Pack 6.1.16 version
2. use the Vagrantfile I provided above
3. Execute vagrant up master1 --debug
4. You should get the same result as me...

References

#12045

Does anyone know how to solve it?

[flavoi]

Hey, I solved this issue manually:
1) Uninstall VirtualBox via the their official uninstaller script
2) Do a clean install of VirtualBox using VirtualBox.pkg
3) Adjust the privacy settings of Big Sur: System Preferences > Security and Privacy > click the allow button

Hope this helps, cheers.

[dkoether]

We can confirm this. Following @flavoi steps fixes this error. Thanks!

[XanxusVerVR]

I followed the steps provided by @flavoi and still got the same error. I even manually removed the files and directories related to VirtualBox, but it didn't work...

[4levels]

The privacy settings are easily overlooked, since they open in a disabled state and are barely visible (great UI design apple #not)
After allowing the settings, the os should ask you to reboot.

[XanxusVerVR]

I took a look at my privacy settings and found that there was an oracle thing that was disabled...it didn't even pop up a prompt asking me to turn it on.
After I turned it on, I restarted and it was ready to work.

I ignored the privacy setting and did not double check, thanks all, the problem is solved !

@flavoi 's advice is useful !

[pboese]

Mhh, I am getting the exact same error after upgrading to Big Sur but I can't find any "allow" button or similar. Or am I blind?

I uninstalled VirtualBox via their script and reinstalled it.

Thanks a lot for any help here

[marceloglacial]

@pboese

Mhh, I am getting the exact same error after upgrading to Big Sur but I can't find any "allow" button or similar. Or am I blind?

Try to run the virtual machine directly from Virtualbox. MacOS will ask for new permissions and you can approve it one by one. :)

[tuananh]

@pboese

Mhh, I am getting the exact same error after upgrading to Big Sur but I can't find any "allow" button or similar. Or am I blind?

Try to run the virtual machine directly from Virtualbox. MacOS will ask for new permissions and you can approve it one by one. :)

i did that and got this error

[orangegirl85]

@tuananh

This link has helped solve the problem.

https://www.howtogeek.com/658047/how-to-fix-virtualboxs-%E2%80%9Ckernel-driver-not-installed-rc-1908-error/

[tuananh]

Thanks but the thing is it doesn't appear in privacy settings

On Sat, Nov 28, 2020 at 4:04 AM Nico Ianosi [e-mail]
wrote:

@tuananh https://github.com/tuananh

This link has helped solve the problem.

https://www.howtogeek.com/658047/how-to-fix-virtualboxs-%E2%80%9Ckernel-driver-not-installed-rc-1908-error/

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hashicorp/vagrant/issues/12049#issuecomment-734989410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEZETQZSDUALDE7225BNHDSSAH6VANCNFSM4TWJZLSA
.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.