You are not logged in.
Just installed virtualbox and vagrant on a fully updated system.
Installed the following package versions in the following order:
virtualbox 4.3.6-3
vagrant 1.4.3-1
Ran through all of the instructions as documented, including reloading the vboxdrv module
andrew@orion ~/vm % modprobe vboxdrv
One thing that is not documented is that you have to reload virtualbox *after* installing vagrant. Otherwise the following error will be presented:
andrew@orion ~/vm % vagrant up (env: achieve)
Bringing machine 'default' up with 'virtualbox' provider...
[default] Clearing any previously set forwarded ports...
[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
To fix, reload virtualbox via CLI:
andrew@orion ~/vm % sudo vboxreload
This is resolved, just wanted to document.
Last edited by andrewjsledge (2014-02-13 16:43:16)
Offline
Thanks!you save my time!
Offline
I solved this problem by enabling vboxnetadp and vboxnetflt kernel modules:
https://wiki.archlinux.org/index.php/Vi … el_modules
Offline
thanks, searched and tried different things till finally this worked for me.
andrew@orion ~/vm % sudo vboxreload
Offline