我在fedora 17机器上运行vagrant 1.4和virtual box 4.3。当我执行"vagrant up“时,我得到了这个错误:
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
发布于 2014-01-26 20:32:05
今天我也遇到了同样的问题。原因是我在VirtualBox中运行了另一个VM。
解决方案:
sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
您现在应该能够运行vagrant up
或vagrant reload
并配置您的新主机。
正如this answer中提到的,最新版本的macOS可以阻止VirtualBox。
解决方案:
转到System Preferences > Security & Privacy
,然后点击“允许”按钮,让甲骨文(VirtualBox)加载。
(感谢@pazhyn,@lsimonetti & @dave-beauchesne澄清)
发布于 2014-07-01 21:22:41
对于Mac 10.9.3和Vagrant 1.6.3以及VirtualBox 4.3.6,此问题已通过重启VirtualBox修复
sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
发布于 2018-05-30 01:32:47
TL;DR MacOS可能阻止了VirtualBox。转到
System Preferences > Security & Privacy
,然后点击“允许”。
解决方案:转到System Preferences > Security & Privacy
,然后点击“允许”按钮,让甲骨文(VirtualBox)加载。
默认情况下,MacOS可以阻止kext加载。在执行VirtualBoxStartup.sh脚本之前,必须单击"allow“按钮。
然后像answer above一样运行:sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
。
(This article为MacOS内核扩展加载提供了更清晰的信息)
https://stackoverflow.com/questions/21069908
复制相似问题