VBoxManage error Failed to create the host-only adapter

Question

I am running vagrant 1 4 and virtual box 4 3 on fedora 17 machine  When I do  vagrant up   I get this error   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  VBoxNetAdpCtl  ioctl failed for  dev vboxnetctl  Inappropriate ioctl for devic 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

User · Answer

I m running Oracle VM Virtualbox on Ubuntu 16 04 LTS   The solution that worked was to reinstall virtualbox as mentioned here   sudo apt remove virtualbox virtualbox-5 0 virtualbox-4    sudo apt-get install virtualbox  I couldn t find my VirtualBox installation folder  as such could not issue the command     sudo  Library StartupItems VirtualBox VirtualBox restart

User · Answer

My solution     System Preferences -  System Security Privacy -  Allow oracle xxxx  then reinstalling the virtualBox

User · Answer

If you are sure you have allow Oracle from system preference and the error still persist  It is highly possible you have not started VirtualBox  Ensure it is running and run vagrant up again

User · Answer

sudo  Library StartupItems VirtualBox VirtualBox restart   Worked great for me on Mac  This normally happens when I shut down my computer without running    vagrant suspend

User · Answer

I encountered this problem on Windows 8 1  VirtualBox 5 1 18 and Vagrant 1 9 3   Deleting the VirtualBox Hosts-only Ethernet Adapter from VirtualBox Preferences  Network --  Hosts-only networks  fixed this for me  and vagrant up could continue and start the VM

User · Answer

I want to mention that       Open VirtualBox and shut down every VM running     The shut down should be power off   And if your virtualbox has been added in the Path in linux  Mine is Ubuntu   You can just use command  virtualbox restart

User · Answer

I faced this issue on mac    I did the following  Go to   Launcher- Virtualbox  Click the icon to open Virtualbox  Start Virtualbox with the button that pops up once Virtualbox starts  Wait till the terminal window gives you the prompt    docker boot2docker   Then try to open docker  Hope it works

User · Answer

I had this issue after upgrading to OS X El Captian   Upgrading to the latest version of VB solved the issue for me   Virtual box will give you the latest link if you go to the virtualbox menu at the top of your screen and clicking check for updates

User · Answer

Tried multiple solutions but the below sequence works for me  Virtual Box  5 2 34 Vagrant  2 2 5 Mac OSX  10 14 6 First Allow access to oracle inc   Go to System Preferences  gt  Security  amp  Privacy Then hit the  quot Allow quot  button to let Oracle  VirtualBox  load   Then restart VBox by this command  sudo  Library Application  Support VirtualBox LaunchDaemons VirtualBoxStartup sh restart  Now try Vagrant up again

User · Answer

Sometimes this can be fixed by provisioning the box on vagrant up vagrant up --provision

User · Answer

I had the same problem today  The reason was that I had another VM running in VirtualBox   Solution     Open VirtualBox and shut down every VM running Restart VirtualBox    sudo   Library Application Support VirtualBox LaunchDaemons VirtualBoxStartup sh  restart   You should now be able to run vagrant up or vagrant reload and have your new host configured      As mentioned in this answer  recent versions of macOS can block VirtualBox    Solution    Go to System Preferences  gt  Security  amp  Privacy Then hit the  Allow  button to let Oracle  VirtualBox  load    thanks to  pazhyn  amp   lsimonetti for clarifications

User · Answer

My solution   Make sure you have the following files under System32   vboxnetadp sys  vboxnetflt sys   You can download them from here   http   www sysfilesdownload com V VBoxNetFltsys html  http   www sysfilesdownload com U VBoxNetAdp sys html

User · Answer

If you are on Linux  simply run  sudo vboxreload

User · Answer

I ve just had the same problem after upgrading to mac os Big Sur Linus solution worked for me  Grant permission to VirtualBox under System Preferences  gt  Security  amp  Privacy  gt  General  this request is new to macOS High Sierra  Open Terminal and run  sudo  quot  Library Application Support VirtualBox LaunchDaemons VirtualBoxStartup sh quot  restart  https   stackoverflow com a 47652517 6146535

User · Answer

In my case  I was able to solve this issue by reinstalling virtual box  I was trying to use laravel s homestead and was having this error  Reinstalling helps creating the directories that are needed for virtual box again  Took me an hour to figure out

User · Answer

Windows 10 Pro VirtualBox 5 2 12  In my case I had to edit the Host Only Ethernet Adapter in the VirtualBox GUI  Click Global Tools -  Host Network Manager -  Select the ethernet adapter  then click Properties  Mine was set to configure automatically  and the IP address it was trying to use was different than what I was trying to use with drupal-vm and vagrant  I just had to change that to manual and correct the IP address  I hope this helps someone else

User · Answer

For Mac OS X 10 9 3 and Vagrant 1 6 3 and VirtualBox 4 3 6 this problem was fixed with restarting the VirtualBox  sudo   Library Application Support VirtualBox LaunchDaemons VirtualBoxStartup sh  restart

User · Answer

Try these    sudo modprobe vboxnetadp  sudo modprobe vboxnetflt  sudo modprobe vboxdrv

User · Answer

If you are on Linux   sudo service virtualbox restart

User · Answer

I came here  working with kitchen-CI and having problems with vagrant  After  re- moving the     kitchen -directory the kitchen converge was successfull again

User · Answer

This issue appears to be fixed by installing the latest version of Virtual Box

User · Answer

Got the error in Mac after the update to Mojave  Probably you have an older version of virtual box  Update to a recent version of virtualbox   5 2 at the time of wrting this post  Edit  adding  lsimonetti s comment  In addition to that upgrade to Virtualbox 5 2  you need Vagrant  gt   2 0 1

User · Answer

TL DR MacOS is probably blocking VirtualBox  Go to System Preferences  gt  Security  amp  Privacy Then hit the  Allow       Solution  Go to System Preferences  gt  Security  amp  Privacy Then hit the  Allow  button to let Oracle  VirtualBox  load    MacOS by default can block kexts from loading  You must click the  allow  button before executing the VirtualBoxStartup sh script   Then run   sudo   Library Application Support VirtualBox LaunchDaemons VirtualBoxStartup sh  restart like the answer above    This article provides more clarity to MacOS kernel extension loading

User · Answer

I had the same problem while following a tutorial on setting up Laravel Homestead for Windows 10  The tutorial provides an example IP address 192 168 10 10 to use for the server  The problem with their example IP is that if you already have a VirtualBox Host-Only Adapter set up  the IP you use for your vagrant server must have the same first three parts of the IP address of your current adapter   You can check what your current Virtualbox Host-Only Adapter IP address is by running ipconfig  windows  ifconfig  mac linux  and looking for VirtualBox Host-Only Adapter s IPv4 address  192 168 56 1 was mine  Usually if the host IP is 192 168 56 1 then the guest IP will be 192 168 56 101 so instead of using the example IP I used 192 168 56 102  Any IP that is within 192 168 56   that is not already taken should work   After this homestead up worked perfectly for me      TL DR - If your current VirtualBox Host-Only Adapter IP is 192 168 56 1  make your Vagrant server IP 192 168 56 102

User · Answer

I had to reinstall Virtual Box on my machine   Here s the downloads page  Downloads Page  Then vagrant up worked for me after

User · Answer

For macOS Mojave  this solution worked   sudo   Library Application Support VirtualBox LaunchDaemons VirtualBoxStartup sh  restart

User · Answer

If you use macOS High Sierra or upper version you can find the bash script at the location    sudo  Library Application  Support VirtualBox LaunchDaemons VirtualBoxStartup sh restart   So If you got this kind of error       Library Application Support VirtualBox VBoxDrv kext failed to load -  libkern kext  system policy prevents loading  check the system kernel logs for errors or try kextutil 8     You can solve it via System Preferences  gt  Security  amp  Privacy section and Allow the VirtualBox

User · Answer

I am using ubuntu 14 04   I have genymotion installed on virtualbox   Every time I start genymotion I had no problem  but suddenly one time it said unable to load virtualbox engine and it didn t open   I went through the log file and found out it could not create a new host only network because it has already created all possible host only networks   And the problem is that it cannot allocate memory for a new network   Fix  go to your virtual box File --  Preferences --  Network  Click the host-only tab and just delete some of the host-only networks so that you will get some memory freed and next time  a new network can be created easily   Deletion fixed my problem

User · Answer

I had the same problem just now and it was solved by simply reinstalling to the latest version of VirtualBox    For those on Mac OS High Sierra - the installation might fail at first but you need to go to System Preferences   Security  amp  Policy and click on the  Allow  button to allow Oracle installing the software

User · Answer

I fixed this error by installing VirtualBox 4 2 instead of 4 3  I think the latest version of vagrant and VB 4 3 are incompatible on a fedora system

User · Answer

What helped me on Opensuse 42 1 is to install VirtualBox and Vagrant from the official RPMs instead of from Opensuse repositories

User · Answer

CentOS Linux release 7 2 1511  Core   VirtualBox-5 0   I came across this tread while searching Google for     VBoxManage  error  Failed to create the host-only adapter  I was using VirtualBox-5 0 to test some virtual machines created with Vagrant and setting private networks in my Vagrantfile   web vm network  private network   ip   192 168 10 2   When evoking the command   vagrant up I would get the above mentioned error along with  dev vboxnetcrl does not exist     It seems that my version of VirtualBox did not have the proper kernel module compiled for my version of Linux and the device   dev vboxnetcrl  does not get created   Since I wanted to test virtual machine and not troubleshoot VirtualBox  my work around  not a solution  was to      yum remove VirtualBox-5 0    yum install VirtualBox-4 3    After that I was able to create the virtual machines with specified host-adapters  And of course  under VirtualBox-4 3   dev vboxnetcrl was there   Now on to testing my VMs  And when I have time  I ll see if I can get it working under VirtualBox 5 0

User · Answer

I m running Debian 8  Jessie   Vagrant 1 6 5 and Virtual Box 4 3 x with the same problem   For me it got fixed executing   sudo  etc init d vboxdrv setup

[virtual-machine] VBoxManage: error: Failed to create the host-only adapter

Examples related to virtual-machine

Examples related to virtualbox

Examples related to development-environment

Examples related to vagrant