I\'m trying to do a vagrant up on a box, and I get the following error.
INFO interface: error: There was an error executing the following command with VBo
Looks like this is experienced on Mac OSX Mavericks (10.9) and it's a permissions issue.
You can fix it by running:
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
I just recently updated to OS X 10.9 and had this problem with vagrant up
.
If you're running VirtualBox version 4.2 or older, this should work:
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
However, if you're running a newer version of VirtualBox (4.3 or newer), try:
sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist
As noted in this question: vagrant up failed, /dev/vboxnetctl: no such file or directory
In my case it was also :
sudo modprobe vboxnetflt
try with this: sudo modprobe vboxnetadp
in my case it works
I've experienced a similar problem, only there were no visible errors at all: the private network simply was never created. The solution was as dumb and simple as always in such cases:
$ pacman -S net-tools
I didn't see the version of VirtualBox you are running in your question but for version 4.2.x the command listed by the previous answers:
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
should fix your issue. If you are running 4.3.x though the equivalent to this command is:
sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist
This will also restart the VirtualBox services and should fix your issue.
As a side note I have run into the issue where running that command will silently fail and cause VirtualBox to emit the same behavior you described. This is usually caused due to a VM still being active and can usually be resolved by suspending or destroying your vagrant instances or other VMs and rerunning the command.