Encountered Vagrant Up error on MacOs Big Sur Upgrade

vagrant virtualbox macos-big-sur
Sam picture Sam · Nov 13, 2020 · Viewed 9.2k times · Source

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?

Answer

Lester picture Lester · Nov 13, 2020

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.

Related questions

Vagrant stuck connection timeout retrying

My vagrant was working perfectly fine last night. I've just turned the PC on, hit vagrant up, and this is what I get: ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: …

Read More
Failed to open/create the internal network Vagrant on Windows10

I upgraded my Windows 10 to the last update yesterday and now, when I launch vagrant up command, I get this error : ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... The guest …

Read More
Vagrant ssh authentication failure

The problem with ssh authentication: ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: bridged ==> default: Forwarding ports... default: 22 =&…

Read More