New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory #32

Open
bertob opened this Issue Jul 12, 2014 · 6 comments

Comments

Projects
None yet
7 participants
@bertob

bertob commented Jul 12, 2014

When trying to run configure.sh on my Arch GNU/Linux install, I get this error:

OS: linux
DIST: 
REV: 
DistroBasedOn: 
start vagrant with /home/tobias/code/foxbox/B2G
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/precise64' 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

The error seems to be the same as this one:
hashicorp/vagrant#1671
The problem is, the comments in that thread say that the issue is fixed in newer versions of Virtualbox (https://www.virtualbox.org/ticket/8940), but apparently that's not the case.

My setup:
linux 3.15.5-1
virtualbox 4.3.12-1
vagrant 1.6.3-1
nfs-utils 1.3.0-3
net-tools 1.60.20130531git-1

Have I missed anything (i.e. dependencies, daemons that have to be enabled etc.)?

@gerep

This comment has been minimized.

Show comment
Hide comment
@gerep

gerep Oct 16, 2014

Try this sudo modprobe vboxnetadp

gerep commented Oct 16, 2014

Try this sudo modprobe vboxnetadp

@etcet

This comment has been minimized.

Show comment
Hide comment
@etcet

etcet Dec 28, 2014

Thanks, gerep. I had a similar issue with the same error and loading vboxnetadp fixed it.

etcet commented Dec 28, 2014

Thanks, gerep. I had a similar issue with the same error and loading vboxnetadp fixed it.

@nottoseethesun

This comment has been minimized.

Show comment
Hide comment
@nottoseethesun

nottoseethesun Jun 21, 2015

+1 ; On Mac OS X Yosemite, per hashicorp/vagrant#1671 , this worked for me to workaround:

sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart

nottoseethesun commented Jun 21, 2015

+1 ; On Mac OS X Yosemite, per hashicorp/vagrant#1671 , this worked for me to workaround:

sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
@jago86

This comment has been minimized.

Show comment
Hide comment
@jago86

jago86 May 17, 2017

Great!! Worked for me in Ubuntu 16.04. Thanks @gerep

jago86 commented May 17, 2017

Great!! Worked for me in Ubuntu 16.04. Thanks @gerep

@NicholasDShaw

This comment has been minimized.

Show comment
Hide comment
@NicholasDShaw

NicholasDShaw Jul 14, 2017

sudo modprobe vboxnetadp then sudo modprobe vboxnetflt worked for me

NicholasDShaw commented Jul 14, 2017

sudo modprobe vboxnetadp then sudo modprobe vboxnetflt worked for me

@fo2rist

This comment has been minimized.

Show comment
Hide comment
@fo2rist

fo2rist Oct 6, 2018

@nottoseethesun thank! That helped on the MacOS 10.14

fo2rist commented Oct 6, 2018

@nottoseethesun thank! That helped on the MacOS 10.14

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