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

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

Closed
Telemakhos opened this Issue Apr 29, 2013 · 133 comments

Comments

Projects
None yet
@Telemakhos

Telemakhos commented Apr 29, 2013

Hi, I'm getting this error when 'vagrant up'

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

It appeared suddenly. I assumed this is a Virtualbox issue so I checked the Virtualbox GUI and got this alert..

Kernel driver not installed (rc=-1908)

Screen Shot 2013-04-29 at 8 58 30 PM

I reinstalled Virtualbox and all was working ok again... for some hours.

Now and I'm having the same issue. Any clues? I've seen on #vagrant IRC at least one guy with the same problem.

System specs:
Mountain Lion 10.8.3
Vagrant 1.2.2
VirtualBox 4.2.12 r84980

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh Apr 30, 2013

Member

Fixed. Thanks! (There is better error output now)

Member

mitchellh commented Apr 30, 2013

Fixed. Thanks! (There is better error output now)

@mitchellh mitchellh closed this Apr 30, 2013

@lslucas

This comment has been minimized.

Show comment
Hide comment
@lslucas

lslucas Aug 5, 2013

Same error with me, I don't know if this error is on vagrant but I really think that is on virtualbox.

What maybe be cause the problem:
I need vagrant to work, so I use every day on my macbook, I reboot or shutdown my computer some times too but last day I take off my RAM to change for a new one, that don't work (memory with problem) so I put my old memory back. Then, when I try to vagrant up I got that error; but ok, I was with a old version (vagrant and vbox) so I upgrade both and all work again, even rebooting and vagrant up again, all fine.
Today after putting my new memory I got the same error but I found a better solution, restarting virtualbox and all start to working again.

Solution:
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
http://d.pr/i/1Bvi

I wrote this just for any one who have the same or similar issue and maybe I lead to where to look to fix the bug or unless display a better explain about what to do on that error.

Vagrant version 1.2.7
Virtualbox version 4.2.16

lslucas commented Aug 5, 2013

Same error with me, I don't know if this error is on vagrant but I really think that is on virtualbox.

What maybe be cause the problem:
I need vagrant to work, so I use every day on my macbook, I reboot or shutdown my computer some times too but last day I take off my RAM to change for a new one, that don't work (memory with problem) so I put my old memory back. Then, when I try to vagrant up I got that error; but ok, I was with a old version (vagrant and vbox) so I upgrade both and all work again, even rebooting and vagrant up again, all fine.
Today after putting my new memory I got the same error but I found a better solution, restarting virtualbox and all start to working again.

Solution:
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
http://d.pr/i/1Bvi

I wrote this just for any one who have the same or similar issue and maybe I lead to where to look to fix the bug or unless display a better explain about what to do on that error.

Vagrant version 1.2.7
Virtualbox version 4.2.16

@gvt

This comment has been minimized.

Show comment
Hide comment
@gvt

gvt Aug 8, 2013

+1

sudo /Library/StartupItems/VirtualBox/VirtualBox restart fixed it for me.

gvt commented Aug 8, 2013

+1

sudo /Library/StartupItems/VirtualBox/VirtualBox restart fixed it for me.

@lldong

This comment has been minimized.

Show comment
Hide comment
@lldong

lldong commented Aug 8, 2013

+1

@nathanjo

This comment has been minimized.

Show comment
Hide comment
@nathanjo

nathanjo Aug 9, 2013

+1 sudo /Library/StartupItems/VirtualBox/VirtualBox restart

nathanjo commented Aug 9, 2013

+1 sudo /Library/StartupItems/VirtualBox/VirtualBox restart

@Telemakhos

This comment has been minimized.

Show comment
Hide comment
@Telemakhos

Telemakhos Aug 9, 2013

Thanks for the tip! Works like a charm

Telemakhos commented Aug 9, 2013

Thanks for the tip! Works like a charm

@gmacaire

This comment has been minimized.

Show comment
Hide comment
@gmacaire

gmacaire Aug 14, 2013

+1 Thank you very much for the tip ! :)

gmacaire commented Aug 14, 2013

+1 Thank you very much for the tip ! :)

@johntdyer

This comment has been minimized.

Show comment
Hide comment
@johntdyer

johntdyer Oct 1, 2013

Any idea why this seems to be required now?

johntdyer commented Oct 1, 2013

Any idea why this seems to be required now?

@qualbeen

This comment has been minimized.

Show comment
Hide comment
@qualbeen

qualbeen Oct 2, 2013

+1 sudo /Library/StartupItems/VirtualBox/VirtualBox restart

qualbeen commented Oct 2, 2013

+1 sudo /Library/StartupItems/VirtualBox/VirtualBox restart

@tiptronic

This comment has been minimized.

Show comment
Hide comment
@tiptronic

tiptronic commented Oct 4, 2013

+1

@chrismaddern

This comment has been minimized.

Show comment
Hide comment
@chrismaddern

chrismaddern Oct 7, 2013

Thanks @lslucas that worked great!

chrismaddern commented Oct 7, 2013

Thanks @lslucas that worked great!

@danielnegri

This comment has been minimized.

Show comment
Hide comment
@danielnegri

danielnegri commented Oct 8, 2013

+1

@seriouslysean

This comment has been minimized.

Show comment
Hide comment
@seriouslysean

seriouslysean Oct 9, 2013

That little piece of code works like a charm. The weird part is that I need to run that command every single time I restart my machine -- any ideas what the root cause is or how to fix it short of using this snippet?

sudo /Library/StartupItems/VirtualBox/VirtualBox restart

OS X 10.9
Vagrant 1.3.4
VirtualBox 4.2.18 r88780

screen shot 2013-10-09 at 9 57 57 am

seriouslysean commented Oct 9, 2013

That little piece of code works like a charm. The weird part is that I need to run that command every single time I restart my machine -- any ideas what the root cause is or how to fix it short of using this snippet?

sudo /Library/StartupItems/VirtualBox/VirtualBox restart

OS X 10.9
Vagrant 1.3.4
VirtualBox 4.2.18 r88780

screen shot 2013-10-09 at 9 57 57 am

@neogan74

This comment has been minimized.

Show comment
Hide comment
@neogan74

neogan74 Oct 11, 2013

+1 Thank you very much for the tip =)

neogan74 commented Oct 11, 2013

+1 Thank you very much for the tip =)

@mhenrixon

This comment has been minimized.

Show comment
Hide comment
@mhenrixon

mhenrixon commented Oct 13, 2013

👍

@jasonmadigan

This comment has been minimized.

Show comment
Hide comment
@jasonmadigan

jasonmadigan Oct 14, 2013

I also have to run this after every restart with OS X Mavericks. I assume it's a VB bug.

jasonmadigan commented Oct 14, 2013

I also have to run this after every restart with OS X Mavericks. I assume it's a VB bug.

@jasonmadigan

This comment has been minimized.

Show comment
Hide comment
@jasonmadigan

jasonmadigan commented Oct 14, 2013

Related VirtualBox issue: https://www.virtualbox.org/ticket/8940

@seriouslysean

This comment has been minimized.

Show comment
Hide comment
@seriouslysean

seriouslysean Oct 15, 2013

I really, really don't recommend fixing it this way, but it's saved me the frustration of running the restart command every time I restart OS X:

In Automator, create a workflow to run an AppleScript:

on run {input, parameters}

    do shell script "sudo /Library/StartupItems/VirtualBox/VirtualBox restart" password "password" with administrator privileges

    return input
end run

Once you finish that, save it as a .app and set it to run when you log in. This will automatically restart VirtualBox and stop that error from happening so you can vagrant up without having to run that other command first.

It's likely insecure and I don't recommend doing it but since I'm the only person using my computer, it's worked for me.

seriouslysean commented Oct 15, 2013

I really, really don't recommend fixing it this way, but it's saved me the frustration of running the restart command every time I restart OS X:

In Automator, create a workflow to run an AppleScript:

on run {input, parameters}

    do shell script "sudo /Library/StartupItems/VirtualBox/VirtualBox restart" password "password" with administrator privileges

    return input
end run

Once you finish that, save it as a .app and set it to run when you log in. This will automatically restart VirtualBox and stop that error from happening so you can vagrant up without having to run that other command first.

It's likely insecure and I don't recommend doing it but since I'm the only person using my computer, it's worked for me.

@jasonmadigan

This comment has been minimized.

Show comment
Hide comment
@jasonmadigan

jasonmadigan commented Oct 16, 2013

This is resolved in VirtualBox 4.3: https://www.virtualbox.org/ticket/8940

@johntdyer

This comment has been minimized.

Show comment
Hide comment
@johntdyer

johntdyer Oct 16, 2013

Anyone been brave enough to try 4.3 w/ Vagrant ?

johntdyer commented Oct 16, 2013

Anyone been brave enough to try 4.3 w/ Vagrant ?

@seriouslysean

This comment has been minimized.

Show comment
Hide comment
@seriouslysean

seriouslysean Oct 16, 2013

I'm running Vagrant 1.3.3 and it said it doesn't support VirtualBox 4.3 so I had to downgrade.

seriouslysean commented Oct 16, 2013

I'm running Vagrant 1.3.3 and it said it doesn't support VirtualBox 4.3 so I had to downgrade.

@lslucas

This comment has been minimized.

Show comment
Hide comment
@lslucas

lslucas Oct 16, 2013

Vagrant 1.3.5 released with VirtualBox 4.3 support. Also a handful of solid bug fixes. https://t.co/saBOnsa9Z2 http://t.co/oncK4tjLbQ

— Mitchell Hashimoto (@mitchellh) October 15, 2013
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

lslucas commented Oct 16, 2013

Vagrant 1.3.5 released with VirtualBox 4.3 support. Also a handful of solid bug fixes. https://t.co/saBOnsa9Z2 http://t.co/oncK4tjLbQ

— Mitchell Hashimoto (@mitchellh) October 15, 2013
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
@seriouslysean

This comment has been minimized.

Show comment
Hide comment
@seriouslysean

seriouslysean Oct 16, 2013

Updated to Vagrant 1.3.5 and VirtualBox 4.3 -- my VM setup booted up without any issues. The only thing I had to do was update the Guest Additions (and it isn't even required).

seriouslysean commented Oct 16, 2013

Updated to Vagrant 1.3.5 and VirtualBox 4.3 -- my VM setup booted up without any issues. The only thing I had to do was update the Guest Additions (and it isn't even required).

@lslucas

This comment has been minimized.

Show comment
Hide comment
@lslucas

lslucas Oct 16, 2013

Running vagrant up here, all good so far on vagrant 1.3.5 and vb4.3.
http://d.pr/i/4r5G

lslucas commented Oct 16, 2013

Running vagrant up here, all good so far on vagrant 1.3.5 and vb4.3.
http://d.pr/i/4r5G

@seriouslysean

This comment has been minimized.

Show comment
Hide comment
@seriouslysean

seriouslysean Oct 17, 2013

After a restart, I'm still getting that error:

[skennedy:~/Sites] (master) $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[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

Running Vagrant 1.3.5 and VirtualBox 4.3.0 r89960. Any of you still experiencing the same thing?

seriouslysean commented Oct 17, 2013

After a restart, I'm still getting that error:

[skennedy:~/Sites] (master) $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[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

Running Vagrant 1.3.5 and VirtualBox 4.3.0 r89960. Any of you still experiencing the same thing?

@levinotik

This comment has been minimized.

Show comment
Hide comment
@levinotik

levinotik Oct 22, 2013

👍 sudo /Library/StartupItems/VirtualBox/VirtualBox restart

levinotik commented Oct 22, 2013

👍 sudo /Library/StartupItems/VirtualBox/VirtualBox restart

@jasonrm

This comment has been minimized.

Show comment
Hide comment
@jasonrm

jasonrm Oct 23, 2013

Just ran into this as well.
Vagrant 1.3.5
VirtualBox 4.3.0 r89960
OS X 10.9 (13A598)

Was unable to create a host-only network even from the Network tab in the VirtualBox Preferences until I ran:
sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist

It's possible I've only had VirtualBox 4.3.0 installed on this machine as, unlike everyone else, /Library/StartupItems/VirtualBox/VirtualBox does not even exist on this machine.

jasonrm commented Oct 23, 2013

Just ran into this as well.
Vagrant 1.3.5
VirtualBox 4.3.0 r89960
OS X 10.9 (13A598)

Was unable to create a host-only network even from the Network tab in the VirtualBox Preferences until I ran:
sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist

It's possible I've only had VirtualBox 4.3.0 installed on this machine as, unlike everyone else, /Library/StartupItems/VirtualBox/VirtualBox does not even exist on this machine.

@evgeny-l

This comment has been minimized.

Show comment
Hide comment
@evgeny-l

evgeny-l Oct 4, 2015

Broken in El Capitan. Reinstall VirtualBox 4.3 fixed the problem.

evgeny-l commented Oct 4, 2015

Broken in El Capitan. Reinstall VirtualBox 4.3 fixed the problem.

@restlessdesign

This comment has been minimized.

Show comment
Hide comment
@restlessdesign

restlessdesign Oct 5, 2015

Confirming that re-installing Virtualbox works.

restlessdesign commented Oct 5, 2015

Confirming that re-installing Virtualbox works.

@kevnk

This comment has been minimized.

Show comment
Hide comment
@kevnk

kevnk Oct 7, 2015

Upgrading to 4.3.30 worked for me (I'm on El Capitan)

kevnk commented Oct 7, 2015

Upgrading to 4.3.30 worked for me (I'm on El Capitan)

@thomasleduc

This comment has been minimized.

Show comment
Hide comment
@thomasleduc

thomasleduc Oct 8, 2015

Same for me, I think it can be close.

thomasleduc commented Oct 8, 2015

Same for me, I think it can be close.

@ericramirez

This comment has been minimized.

Show comment
Hide comment
@ericramirez

ericramirez Oct 9, 2015

I'm using Arch and I'm experiencing the same issue. Will I need to type sudo vboxreload again and again or does a workaround exist?

ericramirez commented Oct 9, 2015

I'm using Arch and I'm experiencing the same issue. Will I need to type sudo vboxreload again and again or does a workaround exist?

@paolooo

This comment has been minimized.

Show comment
Hide comment
@paolooo

paolooo Oct 9, 2015

Broken in El Capitan too. Installing updates did worked for me.
Go to Check for updates > Download > Install. That's it.

paolooo commented Oct 9, 2015

Broken in El Capitan too. Installing updates did worked for me.
Go to Check for updates > Download > Install. That's it.

@localjo

This comment has been minimized.

Show comment
Hide comment
@localjo

localjo Oct 14, 2015

I ran into this problem last week after upgrading to El Capitan. Updating VirtualBox to 4.3.3 fixed it, but....

I'm running into the error again this morning, only on one of my Vagrant boxes, after I shut it down via the VirtualBox GUI rather than the command line.

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

Running sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh start fails with;

/Applications/VirtualBox.app/Contents/MacOS/VBoxAutostart => /Applications/VirtualBox.app/Contents/MacOS/VBoxAutostart-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxBalloonCtrl => /Applications/VirtualBox.app/Contents/MacOS/VBoxBalloonCtrl-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxDD2GC.gc => /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2GC.gc-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxDDGC.gc => /Applications/VirtualBox.app/Contents/MacOS/VBoxDDGC.gc-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxExtPackHelperApp => /Applications/VirtualBox.app/Contents/MacOS/VBoxExtPackHelperApp-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless => /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage => /Applications/VirtualBox.app/Contents/MacOS/VBoxManage-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdpCtl => /Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdpCtl-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxNetDHCP => /Applications/VirtualBox.app/Contents/MacOS/VBoxNetDHCP-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxNetNAT => /Applications/VirtualBox.app/Contents/MacOS/VBoxNetNAT-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxSVC => /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOMIPCD => /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOMIPCD-amd64
/Applications/VirtualBox.app/Contents/MacOS/VMMGC.gc => /Applications/VirtualBox.app/Contents/MacOS/VMMGC.gc-amd64
/Applications/VirtualBox.app/Contents/MacOS/VirtualBox => /Applications/VirtualBox.app/Contents/MacOS/VirtualBox-amd64
/Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM => /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM-amd64
/Applications/VirtualBox.app/Contents/MacOS/vboxwebsrv => /Applications/VirtualBox.app/Contents/MacOS/vboxwebsrv-amd64
Error: VBoxDrv.kext is already loaded
Fatal error: VirtualBox

And sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart fails with;

Unloading VBoxUSB.kext
Unloading VBoxNetFlt.kext
Unloading VBoxNetAdp.kext
Unloading VBoxDrv.kext
(kernel) Can't remove kext org.virtualbox.kext.VBoxDrv; services failed to terminate - 0xe00002c7.
Failed to unload org.virtualbox.kext.VBoxDrv - (iokit/common) unsupported function.
Error: Failed to unload VBoxDrv.kext
Fatal error: VirtualBox

I suppose reinstalling VirtualBox will probably work, but I'm trying to avoid that for now, since I'm on my mobile hotspot.

localjo commented Oct 14, 2015

I ran into this problem last week after upgrading to El Capitan. Updating VirtualBox to 4.3.3 fixed it, but....

I'm running into the error again this morning, only on one of my Vagrant boxes, after I shut it down via the VirtualBox GUI rather than the command line.

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

Running sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh start fails with;

/Applications/VirtualBox.app/Contents/MacOS/VBoxAutostart => /Applications/VirtualBox.app/Contents/MacOS/VBoxAutostart-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxBalloonCtrl => /Applications/VirtualBox.app/Contents/MacOS/VBoxBalloonCtrl-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxDD2GC.gc => /Applications/VirtualBox.app/Contents/MacOS/VBoxDD2GC.gc-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxDDGC.gc => /Applications/VirtualBox.app/Contents/MacOS/VBoxDDGC.gc-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxExtPackHelperApp => /Applications/VirtualBox.app/Contents/MacOS/VBoxExtPackHelperApp-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless => /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage => /Applications/VirtualBox.app/Contents/MacOS/VBoxManage-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdpCtl => /Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdpCtl-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxNetDHCP => /Applications/VirtualBox.app/Contents/MacOS/VBoxNetDHCP-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxNetNAT => /Applications/VirtualBox.app/Contents/MacOS/VBoxNetNAT-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxSVC => /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC-amd64
/Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOMIPCD => /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOMIPCD-amd64
/Applications/VirtualBox.app/Contents/MacOS/VMMGC.gc => /Applications/VirtualBox.app/Contents/MacOS/VMMGC.gc-amd64
/Applications/VirtualBox.app/Contents/MacOS/VirtualBox => /Applications/VirtualBox.app/Contents/MacOS/VirtualBox-amd64
/Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM => /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM-amd64
/Applications/VirtualBox.app/Contents/MacOS/vboxwebsrv => /Applications/VirtualBox.app/Contents/MacOS/vboxwebsrv-amd64
Error: VBoxDrv.kext is already loaded
Fatal error: VirtualBox

And sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart fails with;

Unloading VBoxUSB.kext
Unloading VBoxNetFlt.kext
Unloading VBoxNetAdp.kext
Unloading VBoxDrv.kext
(kernel) Can't remove kext org.virtualbox.kext.VBoxDrv; services failed to terminate - 0xe00002c7.
Failed to unload org.virtualbox.kext.VBoxDrv - (iokit/common) unsupported function.
Error: Failed to unload VBoxDrv.kext
Fatal error: VirtualBox

I suppose reinstalling VirtualBox will probably work, but I'm trying to avoid that for now, since I'm on my mobile hotspot.

@cfperea

This comment has been minimized.

Show comment
Hide comment
@cfperea

cfperea Oct 19, 2015

I had the same issue when upgraded from Yosemite to El Capitan. Updated VirtualBox to 4.3.30 and the problem was resolved.

cfperea commented Oct 19, 2015

I had the same issue when upgraded from Yosemite to El Capitan. Updated VirtualBox to 4.3.30 and the problem was resolved.

@imikay

This comment has been minimized.

Show comment
Hide comment
@imikay

imikay Nov 11, 2015

Same problem here when I upgraded to El Capitan, reinstalled both new versions of VirtualBox and Vagrant solved the problem.

imikay commented Nov 11, 2015

Same problem here when I upgraded to El Capitan, reinstalled both new versions of VirtualBox and Vagrant solved the problem.

@thiagoeliasr

This comment has been minimized.

Show comment
Hide comment
@thiagoeliasr

thiagoeliasr Dec 10, 2015

Had the same problem after updating to El Capitain. Just here to confirm that I reinstalled VirtualBox version 4.3.34 and the problem was solved. 😀

thiagoeliasr commented Dec 10, 2015

Had the same problem after updating to El Capitain. Just here to confirm that I reinstalled VirtualBox version 4.3.34 and the problem was solved. 😀

@coryschwartz

This comment has been minimized.

Show comment
Hide comment
@coryschwartz

coryschwartz Jan 12, 2016

This problem has to do with modules loaded in virtualbox. For those who have re-installed virtualbox, your distro/packaging system might have done this for you. For correct operation, including the vbox networking, you have to have these:

$ lsmod | grep vbox
vboxpci 24576 0
vboxnetflt 28672 0
vboxnetadp 28672 0
vboxdrv 385024 3 vboxnetadp,vboxnetflt,vboxpci

coryschwartz commented Jan 12, 2016

This problem has to do with modules loaded in virtualbox. For those who have re-installed virtualbox, your distro/packaging system might have done this for you. For correct operation, including the vbox networking, you have to have these:

$ lsmod | grep vbox
vboxpci 24576 0
vboxnetflt 28672 0
vboxnetadp 28672 0
vboxdrv 385024 3 vboxnetadp,vboxnetflt,vboxpci

@anonRegions

This comment has been minimized.

Show comment
Hide comment
@anonRegions

anonRegions Apr 6, 2016

I'm having the same problem noted above. As per coryschwartz, I ran this:

$ lsmod | grep vbox

yielding this:

vboxdrv 446786 0

So vboxnetadp,vboxnetflt & vboxpci are missing.

Please advise ASAP. I'm dead in the water.

anonRegions commented Apr 6, 2016

I'm having the same problem noted above. As per coryschwartz, I ran this:

$ lsmod | grep vbox

yielding this:

vboxdrv 446786 0

So vboxnetadp,vboxnetflt & vboxpci are missing.

Please advise ASAP. I'm dead in the water.

@kkiernan

This comment has been minimized.

Show comment
Hide comment
@kkiernan

kkiernan Jan 27, 2017

Just updated to macOS Sierra and had this same problem. Updating to VirtualBox 5.1.14 fixed the issue for me.

kkiernan commented Jan 27, 2017

Just updated to macOS Sierra and had this same problem. Updating to VirtualBox 5.1.14 fixed the issue for me.

@javasgl

This comment has been minimized.

Show comment
Hide comment
@javasgl

javasgl Apr 1, 2017

the same error meet up after update to macOS Sierra. And i reinstall the VirtualBox and vagrant fixed .

javasgl commented Apr 1, 2017

the same error meet up after update to macOS Sierra. And i reinstall the VirtualBox and vagrant fixed .

@snipebin

This comment has been minimized.

Show comment
Hide comment
@snipebin

snipebin May 10, 2017

Reinstalling VBox in El Captain fixed for me.

snipebin commented May 10, 2017

Reinstalling VBox in El Captain fixed for me.

@kevinreynolds

This comment has been minimized.

Show comment
Hide comment
@kevinreynolds

kevinreynolds Jul 10, 2017

Updating to v5.1.22 fixed this issue for me in macOS Sierra

kevinreynolds commented Jul 10, 2017

Updating to v5.1.22 fixed this issue for me in macOS Sierra

@austenpayan

This comment has been minimized.

Show comment
Hide comment
@austenpayan

austenpayan Aug 27, 2017

Updating to Vbox v5.1.26 fixed for me in macOS Sierra v10.12.6

austenpayan commented Aug 27, 2017

Updating to Vbox v5.1.26 fixed for me in macOS Sierra v10.12.6

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Oct 20, 2017

sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart worked for me.
Initially, it gave me a message that my system preferences blocked it when I executed the above command. I opened system preferences, privacy settings, and hit allow for oracle plugin and use same command, then it worked.

ghost commented Oct 20, 2017

sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart worked for me.
Initially, it gave me a message that my system preferences blocked it when I executed the above command. I opened system preferences, privacy settings, and hit allow for oracle plugin and use same command, then it worked.

@JohnVonNeumann

This comment has been minimized.

Show comment
Hide comment
@JohnVonNeumann

JohnVonNeumann Nov 1, 2017

For those of you of the Linux persuasion:

sudo service virtualbox restart

JohnVonNeumann commented Nov 1, 2017

For those of you of the Linux persuasion:

sudo service virtualbox restart

@saltcod

This comment has been minimized.

Show comment
Hide comment
@saltcod

saltcod Feb 12, 2018

In High Sierra:
I had to unblock this blocked kext execution attempt here: https://developer.apple.com/library/content/technotes/tn2459/_index.html

Then sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

Then I could vagrant up.

saltcod commented Feb 12, 2018

In High Sierra:
I had to unblock this blocked kext execution attempt here: https://developer.apple.com/library/content/technotes/tn2459/_index.html

Then sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

Then I could vagrant up.

@pnoeric

This comment has been minimized.

Show comment
Hide comment
@pnoeric

pnoeric Mar 23, 2018

Just to echo @saltcod - this appears to be the solution if you are running Mac OS High Sierra.

pnoeric commented Mar 23, 2018

Just to echo @saltcod - this appears to be the solution if you are running Mac OS High Sierra.

@fergalmonaghan

This comment has been minimized.

Show comment
Hide comment
@fergalmonaghan

fergalmonaghan Apr 11, 2018

Ditto, I am on Mac OS High Sierra and @saltcod 's note worked for me

fergalmonaghan commented Apr 11, 2018

Ditto, I am on Mac OS High Sierra and @saltcod 's note worked for me

@kunth

This comment has been minimized.

Show comment
Hide comment
@kunth

kunth Jun 4, 2018

Maybe a little different with saltcod's solution, on Mac High Sierra, I solved this by:

  1. close the virtualbox
  2. execute the
sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart

and you would see the following

Unloading VBoxUSB.kext
Unloading VBoxNetFlt.kext
Unloading VBoxNetAdp.kext
Unloading VBoxDrv.kext
Loading VBoxDrv.kext
Loading VBoxUSB.kext
Loading VBoxNetFlt.kext
Loading VBoxNetAdp.kext
  1. start the virtualbox, and it would turn out to be all right.

kunth commented Jun 4, 2018

Maybe a little different with saltcod's solution, on Mac High Sierra, I solved this by:

  1. close the virtualbox
  2. execute the
sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart

and you would see the following

Unloading VBoxUSB.kext
Unloading VBoxNetFlt.kext
Unloading VBoxNetAdp.kext
Unloading VBoxDrv.kext
Loading VBoxDrv.kext
Loading VBoxUSB.kext
Loading VBoxNetFlt.kext
Loading VBoxNetAdp.kext
  1. start the virtualbox, and it would turn out to be all right.
@smitjainsj

This comment has been minimized.

Show comment
Hide comment
@smitjainsj

smitjainsj Sep 25, 2018

This the same error in new release on Mojave !!

VirtualBox 5.2.18

Also, post boot of the machine, the VM is stuck.

smitjainsj commented Sep 25, 2018

This the same error in new release on Mojave !!

VirtualBox 5.2.18

Also, post boot of the machine, the VM is stuck.

@piyushkantm

This comment has been minimized.

Show comment
Hide comment
@piyushkantm

piyushkantm Sep 25, 2018

Another victim of Mojave update!! :(

piyushkantm commented Sep 25, 2018

Another victim of Mojave update!! :(

@tohjg

This comment has been minimized.

Show comment
Hide comment
@tohjg

tohjg Sep 26, 2018

Another victom of Mojave update. Just reinstalled virtualbox via homebrew and it works.

brew cask reinstall virtualbox

tohjg commented Sep 26, 2018

Another victom of Mojave update. Just reinstalled virtualbox via homebrew and it works.

brew cask reinstall virtualbox

@piyushkantm

This comment has been minimized.

Show comment
Hide comment
@piyushkantm

piyushkantm Sep 26, 2018

I also fixed it by updating the virtualbox and vagrant. I had installed it via package so downloaded the latest from their website.

Piyushs-MacBook-Pro:~ piyushkantm$ vboxmanage --version
5.2.18r124319

Piyushs-MacBook-Pro:~ piyushkantm$ vagrant --version
Vagrant 2.1.5

Additionally if you're using laravel, also update vagrant box to 6.3.0.

Piyushs-MacBook-Pro:~ piyushkantm$ vagrant global-status
id       name        provider   state    directory                           
-----------------------------------------------------------------------------
5d694e6  homestead-7 virtualbox poweroff /Users/piyushkantm/Homestead        




Piyushs-MacBook-Pro:~ piyushkantm$ vagrant box update 5d694e6

piyushkantm commented Sep 26, 2018

I also fixed it by updating the virtualbox and vagrant. I had installed it via package so downloaded the latest from their website.

Piyushs-MacBook-Pro:~ piyushkantm$ vboxmanage --version
5.2.18r124319

Piyushs-MacBook-Pro:~ piyushkantm$ vagrant --version
Vagrant 2.1.5

Additionally if you're using laravel, also update vagrant box to 6.3.0.

Piyushs-MacBook-Pro:~ piyushkantm$ vagrant global-status
id       name        provider   state    directory                           
-----------------------------------------------------------------------------
5d694e6  homestead-7 virtualbox poweroff /Users/piyushkantm/Homestead        




Piyushs-MacBook-Pro:~ piyushkantm$ vagrant box update 5d694e6

@akashnimare

This comment has been minimized.

Show comment
Hide comment
@akashnimare

akashnimare Sep 26, 2018

This should work on Mojave

brew cask reinstall virtualbox
brew cask reinstall vagrant
vagrant plugin update

akashnimare commented Sep 26, 2018

This should work on Mojave

brew cask reinstall virtualbox
brew cask reinstall vagrant
vagrant plugin update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment