`vagrant up` fails with `failed to open/dev/vboxnetctl: No such file or directory`

Asked 2 years ago, Updated 2 years ago, 74 views

vagrant up encountered the following error:

There was an error while executing `VBoxManage', a CLI used by Vagrant
for controlling VirtualBox.The command and stderris show 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: "inthandleCreate(HandlerArg*, int, int*)" at line 66 of file VBoxManageHostonly.cpp

Uninstalling and installing VirtualBox, Vagrant has no effect.

Refer to "Error while adding new interface: failed to open/dev/vboxnetctl: No such file or directory #1671" in Issue and

$sudolaunchctl load/Library/LaunchDaemons/org.virtualbox.startup.plist

I have tried , but this is also ineffective.

However, not all fancy machines fail vagrant up, and some virtual machines can do vagrant up as usual.So it's probably not the VirtualBox or Vagrant side that has the problem.

However, I don't know what kind of approach to take from here on out. I would appreciate your help.

Development Environment:

  • VirtualBox 4.3.20
  • Vagrant 1.7.1
  • OS X Yosemite 10.10.1

vagrant virtualbox

2022-09-30 20:29

1 Answers

In addition to the Issue, the solution was organized into "SO:vagrant up failed,/dev/vboxnetctl:no such file or directory"

" as you suggested.

Depending on the Mac OS X version, the location of the file seems to be different, so you can't find the file by that method. Try the following commands while referring to Stackoverflow's answers:

  • sudo/Library/StartupItems/VirtualBox/VirtualBox restart
  • sudo/Library/StartupItems/VirtualBox/VirtualBox start
  • sudolaunchctl load/Library/LaunchDaemons/org.virtualbox.startup.plist<=This failed
  • sudo"/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart


2022-09-30 20:29

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.