macOS Monterey and VirtualBox 6.1.28

[petealves]

Hello. I am having some issues with running vagrant up in Mac OS Monterey 12.0.1.
I am running Virtual Box version 6.1.26 (I have tried 6.1.28, same problems) and Vagrant version 2.2.18.
During the installation of VBox I did went into System Preferences -> Privacy -> Allow Oracle....

So, the first problem is the following:

However, when I load the kexts (found this suggestion in other threads) by running sudo kextload -b org.virtualbox.kext.VBoxDrv sudo kextload -b org.virtualbox.kext.VBoxNetFlt sudo kextload -b org.virtualbox.kext.VBoxNetAdp sudo kextload -b org.virtualbox.kext.VBoxUSB it throws me another error which I could not find any solution for.

Is this some problem with MacOS Monterey? Thanks!

[mmihalev]

Absolutely the same issue here too.
I've also reported it to Oracle here: https://www.virtualbox.org/ticket/20636#comment:2

[tomektomczuk]

Same problem here after upgrading to Monterey

vagrant up

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-20.04' version '202107.28.0' is up to date...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "ccae549f-744e-40e2-8a06-0f6a1f7aeced", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'marcin.test' has terminated unexpectedly during startup because of signal 10
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

[ovunckesici]

Same problem here.

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

Command: ["startvm", "72222bee-d25d-4809-baa0-4e7749931097", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'homestead' has terminated unexpectedly during startup because of signal 10
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

[Vextil]

Same issue with Monterey.

Bringing machine 'pay' up with 'virtualbox' provider...
==> pay: Importing base box 'bento/ubuntu-20.04'...
==> pay: Matching MAC address for NAT networking...
==> pay: Checking if box 'bento/ubuntu-20.04' version '202107.28.0' is up to date...
==> pay: Setting the name of the VM: pay
==> pay: Clearing any previously set network interfaces...
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

[dsutphin]

A workaround I've found is to enable the VirtualBox GUI in the Vagrantfile.
https://www.vagrantup.com/docs/providers/virtualbox/configuration#gui-vs-headless

[petealves]

A workaround I've found is to enable the VirtualBox GUI in the Vagrantfile. https://www.vagrantup.com/docs/providers/virtualbox/configuration#gui-vs-headless

Can confirm, it worked as a workaround for me. Thanks!!

[mmihalev]

A workaround I've found is to enable the VirtualBox GUI in the Vagrantfile. https://www.vagrantup.com/docs/providers/virtualbox/configuration#gui-vs-headless

I can confirm that workaround worked with me as well. However, the IP address on the VM was not set to the one from the Vagrantfile / config.vm.network 'private_network', ip: '11.0.0.12' /.
Not sure if this is because of the workaround, or because of some other issue related to vagrant/virtualbox.

[tomektomczuk]

For me it stuck at

`==> default: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=3,udp 192.168.50.1:/System/Volumes/Data/Users/[localtion]/vagrant-nfs-marcin.test

Stdout from the command:

Stderr from the command:

mount.nfs: Connection timed out
exit status 1`

[dsutphin]

However, the IP address on the VM was not set to the one from the Vagrantfile / config.vm.network 'private_network', ip: '11.0.0.12' /.

I ran into this as well. Using config.vm.network "forwarded_port", guest: 80, host: 8080 for now. Keeping an eye out for better solutions.

[mmihalev]

For me it stuck at

`==> default: Mounting NFS shared folders... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!

mount -o vers=3,udp 192.168.50.1:/System/Volumes/Data/Users/[localtion]/vagrant-nfs-marcin.test

Stdout from the command:

Stderr from the command:

mount.nfs: Connection timed out exit status 1`

It stuck probably due to the same reason with the incorrect IP address set to the VM. It seems that with the workaround it's not setting the correct IP address.

[rockblings]

For me, it is still showing this error

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

[rockblings]

after enabling the VirtualBox Gui, then ran these commands: sudo kextload -b org.virtualbox.kext.VBoxDrv sudo kextload -b org.virtualbox.kext.VBoxNetFlt sudo kextload -b org.virtualbox.kext.VBoxNetAdp sudo kextload -b org.virtualbox.kext.VBoxUSB then it worked for me.

[tomektomczuk]

For me @rockblings solution haven't bring a temporary solution. Still stuck on Mounting NFS shared folders

Running command => vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-20.04' version '202107.28.0' is up to date...
==> 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: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
[default] GuestAdditions seems to be installed (6.1.28) correctly, but not running.
update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup
VirtualBox Guest Additions: or
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 5.4.0-80-generic.
update-initramfs: Generating /boot/initrd.img-5.4.0-80-generic
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
==> default: Mounting NFS shared folders...

[semul]

Hello. I am having some issues with running vagrant up in Mac OS Monterey 12.0.1. I am running Virtual Box version 6.1.26 (I have tried 6.1.28, same problems) and Vagrant version 2.2.18. During the installation of VBox I did went into System Preferences -> Privacy -> Allow Oracle....

So, the first problem is the following: However, when I load the kexts (found this suggestion in other threads) by running sudo kextload -b org.virtualbox.kext.VBoxDrv sudo kextload -b org.virtualbox.kext.VBoxNetFlt sudo kextload -b org.virtualbox.kext.VBoxNetAdp sudo kextload -b org.virtualbox.kext.VBoxUSB it throws me another error which I could not find any solution for.

Is this some problem with MacOS Monterey? Thanks!

I am having same issue :(

[mmihalev]

I think it may be related with Virtualbox running in headless mode. It looks like this issue here: https://www.virtualbox.org/ticket/20636