Home > Software design >  Vagrant up fails on macOS 13.x / Ventura with latest (2.3.2) vagrant release
Vagrant up fails on macOS 13.x / Ventura with latest (2.3.2) vagrant release

Time:10-27

After upgrading mac os to 13 Ventura now i always get this error. Vagrant version 2.3.2, VirtualBox 7.02

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%...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 105 of file VBoxManageHostonly.cpp`

Tried lot of older solutions after older mac os upgrades, nothing helps. Has anyone already found any solution?

CodePudding user response:

This is a bug in Vagrant. It does not support private networking from Virtualbox 7.

Downgrading to Virtualbox 6.1.40 should fix this.

https://github.com/hashicorp/vagrant/issues/12967

CodePudding user response:

I am getting the same issue since the Ventura 13.0 update 2 days ago. Tried with VirtualBox 6.1.38, 6.1.40 and 7.0.0

CodePudding user response:

I have the same issue. I think this is a OSX Ventura/Vagrant compatibility issue. See https://discuss.hashicorp.com/t/vagrant-up-fails-on-macos-13-x-ventura-with-latest-2-3-2-vagrant-release/46043

CodePudding user response:

Ventura will not load the kexts (kernel extensions) used by VirtualBox 6.1.40 and earlier. You must use VirtualBox 7.0.2 (or later) on Ventura.

And vagrant not support virtualbox 7.0.0

See virtualbox forum

  • Related