VirtualBox alert - current version incompatible with macOS Mojave

Vagrant ‘VBoxManage’ issue on Mojave

2nd November 2018

Reading Time:

I updated to the new macOS Mojave last night, which was a mostly seamless process for once – until I tried to ‘vagrant up’

Error executing VBoxManage

With our team production meeting out of the way this morning, I checked my emails and tried to fire up Vagrant to get down to work. As soon as I ran ‘vagrant up’ I go the following 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 94 of file VBoxManageHostonly.cpp

I’ve had some issues running Vagrant after updating macOS in the past, but thankfully this time around it was an easy fix.

I tried to run VirtualBox and straight discovered that the version I was running wasn’t compatible with Mojave. Once you update to Mojave you’ll need to upgrade to VirtualBox 5.2.13 or higher – I’m now running 5.2.20 without any problems.

Share this post

One response to “Vagrant ‘VBoxManage’ issue on Mojave”

  1. Anand says:

    Thanks for the tip, this worked!

Leave a Reply

Your email address will not be published. Required fields are marked *