The current release version of vagrant (2.3.2) fails during vagrant up with the following error on macOS 13.x…
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”]
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
This occurs both with VirtualBox 6.x and 7.x and after allowing VirtualBox “Login items” access, etc. via the macOS Settings app.
Full un-installs and re-installs of both Vagrant and Virtualbox make no difference.
Looks like the kext’s are not signed properly and the OS is blocking them via SIP. I found a temporary workaround until they fix this by disabling SIP. (Warning: This may be unsafe for your Mac) Tested on VirtualBox 6.1.40.
Hosts running recent macOS versions do not support host-only adapters. These adapters are replaced by host-only networks, which define a network mask and an IP address range, where the host network interface receives the lowest address in the range.
Thanks Cromian! The post from Ivanner was in the right direction but this gist is what you need to change in your homestead.rb. Just ensure you use Virtualbox 7.0.2 and that you create a local network (everything is in the referred issue).
This issue has been addressed here and will be included in the 2.3.3 release. The 2.3.3 release is process is currently running and should be completed in the next hour or so. Until then, if you need something right now, you can grab a nightly package from here.