Skip to content

Instantly share code, notes, and snippets.

@easternbloc
Created March 10, 2014 12:40
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save easternbloc/9464293 to your computer and use it in GitHub Desktop.
Save easternbloc/9464293 to your computer and use it in GitHub Desktop.
~/Projects/pp-development (gh:(3923957...)*) $ vagrant up
The following plugins were installed with a version of Vagrant
that had different versions of underlying components. Because
these component versions were changed (which rarely happens),
the plugins must be uninstalled and reinstalled.
To ensure that all the dependencies are properly updated as well
it is _highly recommended_ to do a `vagrant plugin uninstall`
prior to reinstalling.
This message will not go away until all the plugins below are
either uninstalled or uninstalled then reinstalled.
The plugins below will not be loaded until they're uninstalled
and reinstalled:
vagrant-aws
Bringing machine 'pp-development-1' up with 'virtualbox' provider...
[pp-development-1] Clearing any previously set forwarded ports...
[pp-development-1] 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 68 of file VBoxManageHostonly.cpp
~/Projects/pp-development (gh:(3923957...)*) $ sudo /Library/StartupItems/VirtualBox/VirtualBox restart
@easternbloc
Copy link
Author

Running the second line fixes it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment