Home > other >  Vagrant up fails on macOS 13 (Ventura) with latest Vagrant (2.3.2) release
Vagrant up fails on macOS 13 (Ventura) with latest Vagrant (2.3.2) release

Time:10-28

After upgrading macOS to macOS 13 (Ventura) I now always get this error. Vagrant is version 2.3.2 and VirtualBox is version 7.0.2.

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 macOS upgrades, nothing helps.

Has anyone already found any solution?

CodePudding user response:

Although Vagrant is supporting VirtualBox 7 starting on version 2.3.2 (https://github.com/hashicorp/vagrant/blob/main/CHANGELOG.md#232-october-18-2022), there is an issue preventing private networks to be created. You should keep an eye here: https://github.com/hashicorp/vagrant/issues/12967

I believe we should find a solution soon.

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:

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