Encountered Vagrant Up error on MacOs Big Sur Upgrade

▲
19
▼

I just upgraded my mac OS from Catalina to Big Sur. My vagrant used to be working normally before and then I encountered this issue. (Vagrant version: 2.2.13)

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

When I tried to start it manually on the VirtualBox this is the return 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.

Does anyone have a clue on how to fix this issue?

vagrant
virtualbox
macos-big-sur
asked on Stack Overflow Nov 13, 2020 by Sam

7 Answers

▲
21
▼

I had the same issue after updating to Big Sur. I downloaded the latest versions of Vagrant, Virtualbox and VirtualBox Extension Pack. Actually, I don't know if installing the Extension Pack was necessary.

And in the system preferences of MacOS, in Privacy and Security, I had to approve the update from Oracle.

After these steps, I was able to 'vagrant up' again.

answered on Stack Overflow Nov 13, 2020 by Lester
▲
8
▼

Updating VirtualBox to 6.1.16 did it for me. I did not update Vagrant

answered on Stack Overflow Nov 15, 2020 by Lala
▲
2
▼

Updating VirtualBox to 6.1.16 did it for me, not working with 6.0.24. Also reinstalled Vagrant but not sure if necessary.

answered on Stack Overflow Nov 13, 2020 by Franjo Pintarić
▲
1
▼

The allow oracle button in privacy and security never showed up in my settings. Eventually I got it working by booting in recovery mode and running the command

csrutil clear

After that I was able to allow oracle in security and privacy.

answered on Stack Overflow Nov 16, 2020 by J. Doe
▲
0
▼

Fixed by reinstalling both Vagrant and VirtualBox :)

answered on Stack Overflow Nov 13, 2020 by Sam
▲
0
▼

I Also just ran into this issue today after updating to Big Sur. Using homebrew to update VirtualBox (v. 6.1.16) and approving in Security & Privacy did not resolve the problem. I had to give VirtualBox Full Disk Access in the Privacy Tab of Security & Privacy to solve this.

The last comment form the virtualbox forum is what helped me with the last step.

https://forums.virtualbox.org/viewtopic.php?f=39&t=98763#p488757

answered on Stack Overflow Nov 18, 2020 by SpaceJam
▲
0
▼

Upgrading virtual box to latest version (6.1.16 at this moment) works for me. Didn't had to upgrade vagrant version.

vagrant up worked right after upgrading the virtual box.

answered on Stack Overflow Nov 25, 2020 by Pevin

User contributions licensed under CC BY-SA 3.0