Published 3 years ago by graham
It looks like the Beta of OS X (El Capitan) breaks Vagrant.
It's reported that this is because /usr/bin is no longer writeable and anything that was previously installed there (e.g. Vagrant) is removed.
This is the fix that worked for me:
sudo ln -s /opt/vagrant/bin/vagrant /usr/local/bin/vagrant
Hat tip to pointless ramblings: http://pointlessramblings.com/posts/El_Capitan/
Bother. I'm getting the following error:
Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'laravel/homestead' is up to date... ==> default: Clearing any previously set network interfaces... 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 HostNetworkInterface, interface IHostNetworkInterface VBoxManage: error: Context: "int handleCreate(HandlerArg*, int, int*)" at line 66 of file VBoxManageHostonly.cpp
I had the same problem as @AlexanderWright Reinstalled Virutalbox (5.0.4) and then got the error
The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant has detected that you have a version of VirtualBox installed that is not supported. Please install one of the supported versions listed below to use Vagrant: 4.0, 4.1, 4.2, 4.3
Then also reinstalled vagrant, and now it seems to be working again...
I've had the same issue after upgrading to el capitan, re-installed virtualbox and vagrant, but now
vagrant up leeds to endless "default: Warning: Connection timeout. Retrying..."
Had a google but can't find any solutions from people having the same message. Anyone else encountered this?