blocks|key|182275|text|如果您的系统最近更新了内核，您可能需要重新运行vbox设置。如果是这种情况，当您运行virtualbox+start命令时，您将看到以下消息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|182276|$+sudo+/path/to/virtualbox+start
WARNING:+The+vboxdrv+kernel+module+is+not+loaded.+Either+there+is+no+module
+++++++++available+for+the+current+kernel+(2.6.32-358.23.2.el6.x86_64)+or+it+failed+to
+++++++++load.+Please+recompile+the+kernel+module+and+install+it+by

+++++++++++sudo+/etc/init.d/vboxdrv+setup

+++++++++You+will+not+be+able+to+start+VMs+until+this+problem+is+fixed.|code-block|syntax|javascript|182277|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If your system recently updated the kernel, you many need to rerun the vbox setup again. 
If this is the case, you will see the following messages when you run virtualbox start command: 

<pre><code>$ sudo /path/to/virtualbox start
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
 available for the current kernel (2.6.32-358.23.2.el6.x86_64) or it failed to
 load. Please recompile the kernel module and install it by

 sudo /etc/init.d/vboxdrv setup

 You will not be able to start VMs until this problem is fixed.
</code></pre>

blocks|key|180621|text|当我得到错误的时候...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180622|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%25...
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|code-block|syntax|javascript|180623|下面的代码对我有效，并且不返回错误，这样我就可以成功地带上流浪汉了|180624|sudo+/Library/StartupItems/VirtualBox/VirtualBox+restart|180625|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

When I get the error...

<pre><code>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 68 of file VBoxManageHostonly.cpp
</code></pre>

The following works for me and returns no errors, I am then able to bring vagrant up successfully

<pre><code>sudo /Library/StartupItems/VirtualBox/VirtualBox restart
</code></pre>

blocks|key|3003433|text|最重要的是尝试了所有的补救措施，尽管执行了很少的命令，但仍然不起作用。我的排序/库/StartupItems/Vir*的Mac中没有任何内容，下面的命令失败：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3003434|sudo+/Library/StartupItems/VirtualBox/VirtualBox+restart|code-block|syntax|javascript|3003435|重新安装最新的VirtualBox，然后运行下面的命令帮助我让虚拟机正常运行|3003436|sudo+launchctl+load+/Library/LaunchDaemons/org.virtualbox.startup.plist|3003437|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Tried above all remedies, few commands although executed, did not work.
Nothing is present in my Mac (el captain) of sort /Library/StartupItems/Vir*, and below command failed:

<pre><code>sudo /Library/StartupItems/VirtualBox/VirtualBox restart
</code></pre>

Reinstalling latest VirtualBox and then running below command helped me having VM running

<pre><code>sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist
</code></pre>

blocks|key|182285|text|我在High+Sierra上启动一个虚拟盒子时也遇到了类似的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|182286|182287|+macOS+High+Sierra+10.13引入了一项新功能，在加载新安装的第三方内核扩展(KEXT)之前需要用户批准。当请求加载用户尚未批准的KEXT时，加载请求将被拒绝。将KEXT加载失败视为硬错误的应用程序或安装程序将需要更改以处理此新情况。|blockquote|182288|182289|182290|要解决此问题，您必须在“系统首选项”>“安全性与隐私”中手动批准KEXT。|182291|以下是来自苹果的技术笔记：|182292|https://developer.apple.com/library/content/technotes/tn2459/_index.html|offset|length|182293|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|0|20|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@$N|14|O|15|1|16]]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|M]]]]

I had a similar problem starting a virtual box on High Sierra. 

<blockquote>
 macOS High Sierra 10.13 introduces a new feature that requires user approval before loading newly-installed third-party kernel extensions (KEXTs). When a request is made to load a KEXT that the user has not yet approved, the load request is denied. Apps or installers that treat a KEXT load failure as a hard error will need to be changed to handle this new case.
</blockquote>

To resolve, you must manually approve the KEXT in System Preferences > Security &amp; Privacy.

Here is the Technical Note from Apple:

<a href="https://developer.apple.com/library/content/technotes/tn2459/_index.html" rel="nofollow noreferrer">https://developer.apple.com/library/content/technotes/tn2459/_index.html</a>

blocks|key|180633|text|我运行的是macOS+High+Sierra+10.13.1和VirtualBox+5.2.2。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180634|这对我很有效：|180635|180636|在系统首选项>安全和隐私>常规下向VirtualBox授予权限(此请求是macOS高塞拉的新请求)|ordered-list-item|180637|开放终端并运行：sudo+"/Library/Application+Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh"+restart|offset|length|style|CODE|180638|180639|entityMap^0|0|0|0|0|8|2H|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|U|8|@$J|V|K|W|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

I'm running macOS High Sierra 10.13.1 and VirtualBox 5.2.2.
<h3>This worked for me:</h3>
<ol>
<li>Grant permission to VirtualBox under System Preferences &gt; Security &amp; Privacy &gt; General (this request is new to macOS High Sierra)</li>
<li>Open Terminal and run: <code>sudo &quot;/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh&quot; restart</code></li>
</ol>

blocks|key|3003472|text|我在Ubuntu+17.10上运行vbox时遇到了一些问题，当时我启动了一个主机仅适配/桥接网络的虚拟机。在寻找答案时，我发现了许多在遇到这种问题时很有用的命令。下面是它们：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3003473|虚拟主机问题|3003474|3003475|无法打开/dev/vboxnetctl|blockquote|3003476|3003477|3003478|vboxnet0+--这就是制造所有麻烦的坏人。|offset|length|style|CODE|3003479|3003480|+VBoxNetAdpCtl:添加新接口时出错:无法打开/dev/vboxnetctl:没有此类文件或目录。|3003481|3003482|3003483|这些命令没有特定的使用顺序。它们通常只是有用的和解决问题的。|3003484|1)+sudo+modprobe+vboxdrv|BOLD|3003485|2)+sudo+modprobe+vboxnetadp+-(仅主机接口)|3003486|3)+sudo+modprobe+vboxnetflt+-(使vboxnet0可访问)|3003487|如果您在运行第一个命令时遇到安全启动问题，我建议在BIOS中禁用安全启动(或重新启动)。|3003488|一般modprobe:+FATAL:在目录/lib/+|3003489|+/4.13.0-21-generic中找不到模块vboxnetftl|3003490|3003491|3003492|(网桥网络)|3003493|4)+sudo+apt-get+install+virtualbox-dkms+(扩展)+->在此之后转到命令1|3003494|5)如果创建，则仅sudo+sudo管理主机|3003495|这些有时可能会起作用：|3003496|I.+服务--状态-所有|3003497|II+服务service_name重启|3003498|entityMap^0|0|0|0|0|0|0|0|8|0|0|0|0|0|0|3|L|0|3|O|0|3|O|0|0|0|0|0|0|0|3|10|0|9|D|0|0|B|0|0|C|0|0|J|0^^$0|@$1|2|3|4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1S|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1V|8|@$L|1W|M|1X|N|O]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|Q|3|R|5|G|7|1Z|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|22|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|23|8|@$L|24|M|25|N|Y]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|26|8|@$L|27|M|28|N|Y]]|9|@]|A|$]]|$1|11|3|12|5|6|7|29|8|@$L|2A|M|2B|N|Y]]|9|@]|A|$]]|$1|13|3|14|5|6|7|2C|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|2D|8|@]|9|@]|A|$]]|$1|17|3|18|5|G|7|2E|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|2H|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|2I|8|@$L|2J|M|2K|N|Y]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|2L|8|@$L|2M|M|2N|N|Y]]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|2O|8|@$L|2P|M|2Q|N|Y]]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|2R|8|@$L|2S|M|2T|N|Y]]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|2U|8|@$L|2V|M|2W|N|Y]]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]]|1O|$]]

I had some problems with vbox running on Ubuntu 17.10 when starting a virtual machine with host-only adapted/bridge network. Looking for an answer I found numerous commands that are useful when having that kind of problems. Here they are: 

VIRTUAL HOST PROBLEMS

<blockquote>
 failed to open /dev/vboxnetctl
</blockquote>

<code>vboxnet0</code> - this is the bad guy who is causing all the trouble. 

<blockquote>
 VBoxNetAdpCtl: Error while adding new interface: failed to open
 /dev/vboxnetctl: No such file or directory.
</blockquote>

These commands are not used in particular order. They are just generally useful and problem-solving. 

1) sudo modprobe vboxdrv

2) sudo modprobe vboxnetadp - (host only interface)

3) sudo modprobe vboxnetflt - (make vboxnet0 accecible) 

IF YOU HAVE PROBLEMS WITH SECURE BOOT RUNNING the FIRST COMMAND I RECOMMEND DISABLING SECURE BOOT IN BIOS (or reboot). 

<blockquote>
 modprobe: FATAL: Module vboxnetftl not found in directory
 /lib/modules/4.13.0-21-generic
</blockquote>

(bridge networking)

4) sudo apt-get install virtualbox-dkms (extension) -> go to command 1 after this

5) sudo vboxmanage hostonlyif create

These sometimes might work:

I. service --status-all

II service service_name restart

blocks|key|179728|text|跑|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179729|$+sudo+modprobe+vboxdrv
$+sudo+modprobe+vboxnetadp
$+sudo+vboxreload|code-block|syntax|javascript|179730|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

RUN

<pre><code>$ sudo modprobe vboxdrv
$ sudo modprobe vboxnetadp
$ sudo vboxreload
</code></pre>

blocks|key|3003511|text|我被困在这个问题上有一段时间了。在尝试运行sudo:+/Library时，我一直看到“未找到命令”。命令。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3003512|然而，这对我来说是有效的：|3003513|sudo+/Library/Application\+Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh+restart|code-block|syntax|javascript|3003514|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was stuck on this for a while. I kept seeing 'command not found' when trying to run the sudo: /Library.. command. 

However, this did work for me:

<pre><code>sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart
</code></pre>

blocks|key|178309|text|感谢福克斯，这对我很管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178310|178311|将权限授予系统偏好设置>安全与隐私>常规VirtualBox下的VirtualBox+|ordered-list-item|178312|将/Applications/VirtualBox从您的.dmg文件|178313|中丢弃到VirtualBox|178314|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Thank forks, it worked for me.
<ol>
<li>Grant permission to VirtualBox under System Preferences &gt; Security &amp; Privacy &gt; General</li>
<li>Throw away /Applications/VirtualBox into the trash</li>
<li>Re-install VirtualBox from your .dmg file</li>
</ol>

blocks|key|179742|text|这对我很有效(macOS蒙特利)。这将重新加载所有VirtualBox的内核扩展。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179743|sudo+kmutil+load+-b+org.virtualbox.kext.VBoxUSB
sudo+kmutil+load+-b+org.virtualbox.kext.VBoxNetFlt
sudo+kmutil+load+-b+org.virtualbox.kext.VBoxNetAdp
sudo+kmutil+load+-b+org.virtualbox.kext.VBoxDrv|code-block|syntax|javascript|179744|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This worked for me (macOS Monterey). This reloads all VirtualBox's kernel extensions.
<pre><code>sudo kmutil load -b org.virtualbox.kext.VBoxUSB
sudo kmutil load -b org.virtualbox.kext.VBoxNetFlt
sudo kmutil load -b org.virtualbox.kext.VBoxNetAdp
sudo kmutil load -b org.virtualbox.kext.VBoxDrv
</code></pre>

Can be useful, I found this error. The common solution is reinstall virtualbox but there are a better way.

Solution

<pre><code>sudo /Library/StartupItems/VirtualBox/VirtualBox restart
</code></pre>

or

<pre><code>sudo /Library/StartupItems/VirtualBox/VirtualBox start
</code></pre>

VirtualBox 4.3+

On recents versions, the file (/Library/StartupItems/VirtualBox/VirtualBox) don't exists, so you need to use the command below:

<pre><code>sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist
</code></pre>

<hr>

Error

Print: <a href="http://d.pr/i/1Bvi" rel="noreferrer">http://d.pr/i/1Bvi</a>

<blockquote>
 There was on error while executing <code>VBoxManage</code>, 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 68 of file VBoxManageHostonly.cpp
</blockquote>

Vagrant Git issue about the error: <a href="https://github.com/mitchellh/vagrant/issues/1671#issuecomment-22304107" rel="noreferrer">https://github.com/mitchellh/vagrant/issues/1671#issuecomment-22304107</a>

macOS - vagrant up failed, /dev/vboxnetctl: no such file or directory

可以很有用，我发现了这个错误。常见的解决方案是重新安装virtualbox，但还有更好的方法。解决方案sudo /Library/StartupItems/VirtualBox/VirtualBox restart或sudo /Library/StartupItems/VirtualBox/VirtualBox sta...

问macOS - vagrant up失败，/dev/vboxnetctl:没有这样的文件或目录
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问macOS - vagrant up失败，/dev/vboxnetctl:没有这样的文件或目录EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问macOS - vagrant up失败，/dev/vboxnetctl:没有这样的文件或目录
EN