NS_ERROR_FAILURE "Failed to create the host-only adapter"

[lsh-0]

Modified the Vagrantfile to use the ubuntu/trusty64 box.

Ran vagrant up and received:

$ vagrant up
Bringing machine 'puppet' up with 'virtualbox' provider...
Bringing machine 'client1' up with 'virtualbox' provider...
Bringing machine 'client2' up with 'virtualbox' provider...
==> puppet: Importing base box 'ubuntu/trusty64'...
==> puppet: Matching MAC address for NAT networking...
==> puppet: Checking if box 'ubuntu/trusty64' is up to date...
==> puppet: Setting the name of the VM: puppet-sandbox_puppet_1409175947884_69336
==> puppet: Clearing any previously set forwarded ports...
==> puppet: 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'm investigating now, but I'm new to puppet - does this seem like a problem with my setup?

[lsh-0]

Problem is not with project. This is a known Virtualbox bug that has apparently been fixed. I fixed it by running sudo vboxreload on my Arch system, which appears to simply unload and then reload kernel modules. I put these kernel modules into /etc/modprobe.d/vboxdrv.conf to be loaded up on boot.

http://stackoverflow.com/questions/18149546/vagrant-up-failed-dev-vboxnetctl-no-such-file-or-directory