Hi Everyone,
I'm having a strange issue with Vagrant + VBox on MacOS High Sierra. I've created a custom Vagrant box for my team, and it works fine on Win10 and MacOS Sierra hosts. However, one of my team members is on a newer Mac Pro laptop with MacOs High Sierra, and we get the following error when doing the same setup as the other hosts after "vagrant up":
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "a3c41dcb-841b-4395-9a04-28c50eea6781", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'Vagrant_default_1513972955067_49566' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
This error gives very little to go on. I've researched it for a few days via Google, and have tried multiple suggested fixes like vboxdrv setup, setting DISPLAY env var, verifying host-only network settings, removing and reinstalling vagrant and virtual box, removing ~/.vagrant.d and .vagrant, etc. Everything gives the same error as above. It does not even get to a point where it will create a vbox log file.
One small glimmer of the issue is if I manually run:
$ VBoxHeadless -s "vagrant_default"
The VBox VM starts up as expected, however if I manually run:
$ VBoxManage startvm "vagrant_default" --type headless
The VBox VM fails to start with the same error as above. Has anyone seen this issue before? Is there a way to force vagrant to use VBoxHeadless instead of VBoxManage?
Vagrant Version: 2.0.1
VirtualBox Version: 5.2.4
Any thoughts would be appreciated, I'm not sure what else to do at this point!
Thanks,
- Ryan Langley