blocks|key|2713756|text|此问题已通过以下方式解决：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2713757|yum+install+gcc+kernel-devel+make|code-block|syntax|javascript|2713758|解决方法在这里：https://gist.github.com/larsar/1687725|offset|length|2713759|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/larsar/1687725^0|0|0|8|12|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

This was resolved by:

<pre><code>yum install gcc kernel-devel make
</code></pre>

workaround is here: <a href="https://gist.github.com/larsar/1687725" rel="noreferrer">https://gist.github.com/larsar/1687725</a>

blocks|key|2926398|text|我的共享文件夹/剪贴板由于某种原因停止工作(可能是因为我的虚拟机上安装了补丁)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926399|sudo+mount+-t+vboxsf+Shared_Folder+~/SF/|offset|length|style|CODE|2926400|给出了如下结果：|2926401|VirtualBox:+mount.vboxsf:+mounting+failed+with+the+error:+No+such+device|2926402|对我来说，的解决方案是停止vboxadd并在此之后进行设置：|BOLD|2926403|cd+/opt/VBoxGuestAdditions-*/init++
sudo+./vboxadd+setup|code-block|syntax|javascript|2926404|entityMap^0|0|0|14|0|0|0|20|0|5|P|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@$D|14|E|15|F|N]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|16|8|@]|9|@]|A|$R|S]]|$1|T|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|U|$]]

My shared folder/clipboard stopped to work for some reason (probably due to a patch installation on my virtual machine).

<code>sudo mount -t vboxsf Shared_Folder ~/SF/</code>

Gave following result:

<code>VirtualBox: mount.vboxsf: mounting failed with the error: No such device</code>

The solution for me was to stop vboxadd and do a setup after that:

<pre><code>cd /opt/VBoxGuestAdditions-*/init 
sudo ./vboxadd setup
</code></pre>

blocks|key|2713785|text|好吧，每个人都遗漏了一个基本事实。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2713786|mkdir+/test+-在当前目录中生成子目录。|offset|length|style|CODE|2713787|sudo+mkdir+/test+-在根目录中创建目录。|2713788|因此，如果您的共享目录名是shared，并执行以下操作：|2713789|mkdir+/test
sudo+mount+-t+vboxsf+shared+/test|code-block|syntax|javascript|2713790|它会生成以下错误：|2713791|sbin/mount.vboxsf:+mounting+failed+with+the+error:+No+such+file+or+directory|2713792|因为目录在错误的位置！是的，这就是这个错误所说的。错误不是说重新加载VBOX来宾选项。|2713793|但是如果你这样做：|2713794|sudo+mkdir+~/test
sudo+mount+-t+vboxsf+shared+~/test|2713795|那么它工作得很好。|2713796|有多少人建议重新加载Vbox来宾插件来解决这个错误，或者编写一个复杂的程序来解决在错误位置创建的目录，这真的让我感到惊讶。|2713797|entityMap^0|0|0|B|0|0|G|0|D|6|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1G|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|1I|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|N|7|1L|8|@]|9|@]|A|$O|P]]|$1|10|3|11|5|6|7|1M|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1N|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|15|$]]

Okay everyone is missing a basic fact.

<code>mkdir /test</code> - Makes sub directory in current directory.

<code>sudo mkdir /test</code> - Make directory in Root.

So if your shared directory name is <code>shared</code> and you do the following:

<pre><code>mkdir /test
sudo mount -t vboxsf shared /test
</code></pre>

It generates this error:

<pre><code>sbin/mount.vboxsf: mounting failed with the error: No such file or directory
</code></pre>

Because the directory is in the wrong place! Yes that's what this error is saying. The error is not saying reload the VBOX guest options.

But if you do this:

<pre><code>sudo mkdir ~/test
sudo mount -t vboxsf shared ~/test
</code></pre>

Then it works fine.

It really amazes me how many people suggest reloading the Vbox guest additions to solve this error or writing a complex program to solve a directory created in the wrong place.

blocks|key|140622|text|我可以通过在命令下运行来解决这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|140623|modprobe+-a+vboxguest+vboxsf+vboxvideo|offset|length|style|CODE|140624|entityMap^0|0|0|12|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I am able to resolved this by running below commmand

<code>modprobe -a vboxguest vboxsf vboxvideo</code>

blocks|key|2713833|text|我还有一个正常工作的系统，它突然停止了工作，出现了所描述的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2713834|在我的/lib/modules中查找之后，vboxvfs模块似乎不再存在了。相反，modprobe+vboxsf是让一切重启的必备咒语。|offset|length|style|CODE|2713835|不知道这种变化是什么时候发生的，但它让我大吃一惊。|2713836|entityMap^0|0|L|7|15|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

I also had a working system that suddenly stopped working with the described error.

After furtling around in my /lib/modules it would appear that the <code>vboxvfs</code> module is no more. Instead <code>modprobe vboxsf</code> was the required incantation to get things restarted.

Not sure when that change ocurred, but it caught me out.

blocks|key|140655|text|除了@Mats+answer之外，我还添加了更多的信息(这对我使用Debian8很有帮助)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|140656|我的共享文件夹/剪贴板由于某种原因停止工作(可能是因为我的虚拟机上安装了补丁)。|140657|sudo+mount+-t+vboxsf+Shared_Folder+~/SF/|code-block|syntax|javascript|140658|给了我以下结果：|140659|VirtualBox:+mount.vboxsf:+mounting+failed+with+the+error:+No+such+device|140660|对我来说，的解决方案是停止vboxadd并在此之后进行设置：|style|BOLD|140661|cd+/opt/VBoxGuestAdditions-*/init+
sudo+./vboxadd+setup|140662|此时，如果您仍然收到以下错误：|140663|140664|没有这样的设备。来宾添加安装可能已失败。该错误已记录在/var/log/vboxadd-install.log中|blockquote|CODE|140665|140666|140667|您需要安装linux头文件：|140668|apt-get+install+linux-headers-$(uname+-r)|140669|然后，您可以安装Guest+Additions：|140670|sh+/media/cdrom/VBoxLinuxAdditions.run+--nox11|140671|并通过以下方式重新启动Linux：|140672|reboot|140673|然后你就可以挂载你的共享文件夹了！|140674|mount+-t+vboxsf+Shared_Folder+~/SF/|140675|更多信息(法语)，请查看此page。|140676|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/29456128/55075|1|http://pazpop.fr/installer-les-additions-invite-de-virtualbox-sur-debian-8/^0|2|C|0|0|0|0|0|0|5|P|0|0|0|0|R|S|0|0|0|0|0|0|0|0|0|0|0|D|4|1|0^^$0|@$1|2|3|4|5|6|7|1V|8|@]|9|@$A|1W|B|1X|1|1Y]]|C|$]]|$1|D|3|E|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|20|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|21|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|22|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|23|8|@$A|24|B|25|Q|R]]|9|@]|C|$]]|$1|S|3|T|5|H|7|26|8|@]|9|@]|C|$I|J]]|$1|U|3|V|5|6|7|27|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|28|8|@]|9|@]|C|$]]|$1|X|3|Y|5|Z|7|29|8|@$A|2A|B|2B|Q|10]]|9|@]|C|$]]|$1|11|3|-4|5|6|7|2C|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|2D|8|@]|9|@]|C|$]]|$1|13|3|14|5|6|7|2E|8|@]|9|@]|C|$]]|$1|15|3|16|5|H|7|2F|8|@]|9|@]|C|$I|J]]|$1|17|3|18|5|6|7|2G|8|@]|9|@]|C|$]]|$1|19|3|1A|5|H|7|2H|8|@]|9|@]|C|$I|J]]|$1|1B|3|1C|5|6|7|2I|8|@]|9|@]|C|$]]|$1|1D|3|1E|5|H|7|2J|8|@]|9|@]|C|$I|J]]|$1|1F|3|1G|5|6|7|2K|8|@]|9|@]|C|$]]|$1|1H|3|1I|5|H|7|2L|8|@]|9|@]|C|$I|J]]|$1|1J|3|1K|5|6|7|2M|8|@]|9|@$A|2N|B|2O|1|2P]]|C|$]]|$1|1L|3|-4|5|6|7|2Q|8|@]|9|@]|C|$]]]|1M|$1N|$5|1O|1P|1Q|C|$1R|1S]]|1T|$5|1O|1P|1Q|C|$1R|1U]]]]

In addition to <a href="https://stackoverflow.com/a/29456128/55075">@Mats answer</a>, I'm adding some more info (it helped me on Debian 8).

My shared folder/clipboard stopped to work for some reason (probably due to a patch installation on my virtual machine).

<pre><code>sudo mount -t vboxsf Shared_Folder ~/SF/
</code></pre>

Gave me following result:

<pre><code>VirtualBox: mount.vboxsf: mounting failed with the error: No such device
</code></pre>

The solution for me was to stop vboxadd and do a setup after that:

<pre><code>cd /opt/VBoxGuestAdditions-*/init 
sudo ./vboxadd setup
</code></pre>

At this point, if you still get the following error:

<blockquote>
 No such device. The Guest Additions installation may have failed. The error has been logged in <code>/var/log/vboxadd-install.log</code>
</blockquote>

You need to install linux headers:

<pre><code>apt-get install linux-headers-$(uname -r)
</code></pre>

then you can install Guest Additions:

<pre><code>sh /media/cdrom/VBoxLinuxAdditions.run --nox11
</code></pre>

and restart your Linux by:

<pre><code>reboot
</code></pre>

then you will be able to mount your shared folder!

<pre><code>mount -t vboxsf Shared_Folder ~/SF/
</code></pre>

More informations (in French), check this <a href="http://pazpop.fr/installer-les-additions-invite-de-virtualbox-sur-debian-8/" rel="noreferrer">page</a>.

blocks|key|141775|text|共享文件夹之前对我有效，但突然停止工作(Virualbox+-+host是Windows7，Guest是OpenSuSe)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141776|modprobe+-a+vboxguest+vboxsf+vboxvideo|offset|length|style|CODE|141777|然后是mount+-t+vboxsf+testsf+/opt/tsf+(testsf是添加到Virtualbox共享文件夹中的Windows+C驱动器中的文件夹-+/opt/tsf是OpenSuse中的文件夹|141778|entityMap^0|0|0|12|0|3|V|10|6|2A|8|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|K|$]]

Shared folder was earlier working for me but all f sudden it stopped working (Virualbox - host was Windows 7, Guest was OpenSuSe)

<code>modprobe -a vboxguest vboxsf vboxvideo</code>

then 
<code>mount -t vboxsf testsf /opt/tsf</code> (<code>testsf</code> was the folder in Windows C drive which was added in Virtualbox shared folder --- and <code>/opt/tsf</code> is the folder in OpenSuse

blocks|key|2713923|text|在Ubuntu上，这是可行的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2713924|sudo+apt-get+install+build-essential+linux-headers-`uname+-r`+dkms|code-block|syntax|javascript|2713925|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|$]]

On Ubuntu this worked:

<pre><code>sudo apt-get install build-essential linux-headers-`uname -r` dkms
</code></pre>

blocks|key|139465|text|在两种情况下可能会出现错误/不正确的方法。两个都检查一下，然后弄清楚|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139466|场景1+:|offset|length|style|BOLD|139467|+ ++++ ++++ ++Once+you+are+running+the+VBoxLinuxAdditions.run+or+VBoxSolarisAdditions.pkg+or+VBoxWindowsAdditions.exe+,+check+if+all+the+modules+are+getting+installed+properly.+|code-block|syntax|javascript|139468|1.1.a.在VBoxLinuxAdditions，的情况下|139469|构建VirtualBox来宾添加内核模块失败，|139470|检查/var/log/vboxadd-install.log中的日志文件。如果错误是由内核版本引起的，请更新内核并重新启动vm。在fedora的情况下，|139471|1.1.b.yum更新内核*|139472|1.1.c.重新启动|139473|1.2。如果没有失败，那么一切都很好。您已经拥有预期的内核版本|139474|场景2+:|139475|检查是否安装了VBoxGuestAdditions+(检查文件夹/opt/VBoxGuestAdditions-*是否存在...*表示版本)挂载前需要启动。|139476|2.1。cd+/opt/VBoxGuestAdditions-*/init+&&+./vboxadd+start|139477|*您需要将vm用户的用户id和组id指定为mount命令的选项。|139478|2.2.a.获取用户的uid和gid：|139479|id+-u+<'user'>|139480|id+-g+<'user'>|139481|2.2.b。在mount命令的选项中设置uid和gid：|139482|mount+-t+vboxsf+-o+uid=x，gid=x+shared_folder_name+guest_folder|139483|entityMap^0|0|0|5|0|0|7|I|0|0|K|0|2|S|13|2|17|4|1T|6|0|6|8|0|6|4|0|0|0|5|0|0|4|1G|0|0|0|0|E|0|0|E|0|0|0|1Q|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1M|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1N|8|@$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1T|8|@$D|1U|E|1V|F|G]|$D|1W|E|1X|F|G]|$D|1Y|E|1Z|F|G]|$D|20|E|21|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|22|8|@$D|23|E|24|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|25|8|@$D|26|E|27|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|28|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|29|8|@$D|2A|E|2B|F|G]]|9|@]|A|$]]|$1|10|3|11|5|6|7|2C|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2D|8|@$D|2E|E|2F|F|G]]|9|@]|A|$]]|$1|14|3|15|5|6|7|2G|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2H|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2I|8|@$D|2J|E|2K|F|G]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2L|8|@$D|2M|E|2N|F|G]]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2P|8|@$D|2Q|E|2R|F|G]]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]]|1H|$]]

&nbsp;&nbsp;&nbsp; There can be errors/incorrect approach in two scenarios. Check both of it and figure it out 
 
SCENARIO 1 : 
 
 &nbsp; &nbsp; &nbsp; Once you are running the VBoxLinuxAdditions.run or VBoxSolarisAdditions.pkg or VBoxWindowsAdditions.exe , check if all the modules are getting installed properly. 
1.1.a. In case of VBoxLinuxAdditions, if Building the VirtualBox Guest Additions kernel modules gets failed, 
check the log file in /var/log/vboxadd-install.log . If the error is due to kernel version update your kernel and reboot the vm. In case of fedora, 
1.1.b. yum update kernel* 
1.1.c. reboot 
1.2. If nothing gets failed, then all is fine. You are already having the expected kernel version

SCENARIO 2 : 
 
&nbsp; &nbsp; &nbsp;If the VBoxGuestAdditions is installed (check for a folder /opt/VBoxGuestAdditions-* is present .... * represents version) you need to start it before mounting. 
2.1. cd /opt/VBoxGuestAdditions-*/init &amp;&amp; ./vboxadd start 
&nbsp; &nbsp; &nbsp; You need to specify the user id and group id of your vm user as options to the mount command. 
2.2.a. Getting uid and gid of a user: 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; id -u &lt;'user'> 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; id -g &lt;'user'> 
2.2.b. Setting uid and gid in options of mount command: 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mount -t vboxsf -o uid=x,gid=x &nbsp;&nbsp; shared_folder_name &nbsp;&nbsp; guest_folder

blocks|key|139498|text|您正在使用共享文件夹，因此您需要在虚拟机中安装VirtualBox+Guest+Additions以支持该功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|139499|流浪汉|139500|如果您使用的是Vagrant+(OS+X：brew+cask+install+vagrant)，请运行：|style|CODE|139501|vagrant+plugin+install+vagrant-vbguest
vagrant+vbguest|code-block|syntax|javascript|139502|如果失败，请检查日志，例如|139503|vagrant+ssh+-c+"cat+/var/log/vboxadd-install.log"|139504|也许你只是缺少内核头文件。|139505|虚拟机|139506|在VM内部，您应该安装Guest+Additions、内核头并启动服务，并仔细检查内核扩展是否正在运行。|139507|这取决于来宾操作系统，所以这里有一些简单的步骤：|139508|139509|安装内核包含标头(+VBoxLinuxAdditions).|ordered-list-item|139510|需要|139511|-+RHEL:+`sudo+apt-get+update+&&+sudo+apt-get+install+kernel-devel`
-+CentOS:+`sudo+yum+update+&&+sudo+yum+-y+install+kernel-headers+kernel-devel`|139512|​|139513|139514|安装来宾添加(这取决于操作系统)。|139515|139516|如果你找不到它，可以通过aptitude+search+virtualbox进行检查。|139517|-+Debian：sudo+apt-get+-y+install+build-essential+module-assistant+virtualbox-ose-guest-utils|139518|如果找不到，可以通过dpkg+-l+%7C+grep+virtualbox查看。|139519|-手动下载虚拟机内部的iso+file+(例如wget)并安装，例如|139520|139521|++++1.+`wget+http://download.virtualbox.org/virtualbox/5.0.16/VBoxGuestAdditions_5.0.16.iso+-P+/tmp`
++++2.+`sudo+mount+-o+loop+/tmp/VBoxGuestAdditions_5.0.16.iso+/mnt`
++++3.+`sudo+sh+-x+/mnt/VBoxLinuxAdditions.run+#+--keep`|139522|额外调试：cd+~/install+&&+sh+-x+./install.sh+/mnt/VBoxLinuxAdditions.run|139523|139524|139525|139526|仔细检查内核扩展是否已启动并正在运行：|139527|139528|-+`sudo+modprobe+vboxsf`|139529|139530|139531|Start/restart服务：|139532|139533|-+manually:+`sudo+/opt/VBoxGuestAdditions*/init/vboxadd+setup`+(add+`sudo+sh+-x`+to+debug)
-+Debian:+`sudo+/etc/init.d/vboxadd-service+start`
-+Fedora:+`sudo+/etc/init.d/vboxdrv+setup`
-+CentOS:+`sudo+service+VBoxService+start`|139534|139535|构建主Guest+Additions模块|139536|如果上面不起作用，这里有更复杂的步骤来修复它。这假设您已经安装了VBoxGuestAdditions+(如上所示)。|139537|挂载共享文件夹失败的最常见原因可能与构建Guest+Additions模块失败有关。如果在/var/log/vboxadd-install.log中出现以下错误：|139538|139539|找不到当前运行的内核的标头。|blockquote|139540|139541|139542|这意味着要么你没有安装内核源代码，要么你找不到它们。|139543|如果您已经按照上面的说明安装了它们，请运行以下命令：|139544|$+sudo+sh+-x+/opt/VBoxGuestAdditions-5.0.16/init/vboxadd+setup+2>&1+%7C+grep+KERN
%2B+KERN_VER=2.6.32-573.18.1.el6.x86_64
%2B+KERN_DIR=/lib/modules/2.6.32-573.18.1.el6.x86_64/build|139545|因此，基本上vboxadd脚本期望您的内核源代码在以下目录中可用：|139546|ls+-la+/lib/modules/$(uname+-r)/build|139547|检查内核目录是否存在(符号链接指向现有文件夹)。如果不是，请将它们安装到正确的文件夹中(例如在/usr/src/kernels中)。|139548|因此，vboxadd脚本可以进入您的内核源代码目录并运行make+kernelrelease，获取该值并与当前内核版本进行比较。|139549|逻辑如下：|139550|KERN_VER=`uname+-r`
KERN_DIR="/lib/modules/$KERN_VER/build"
if+[+-d+"$KERN_DIR"+];+then
++++KERN_REL=`make+-sC+$KERN_DIR+--no-print-directory+kernelrelease+2>/dev/null+%7C%7C+true`
++++if+[+-z+"$KERN_REL"+-o+"x$KERN_REL"+=+"x$KERN_VER"+];+then
++++++++return+0
++++fi
fi|139551|如果内核版本与源代码不匹配，也许您必须升级您的Linux内核(以防源代码比您的内核新)。|139552|CentOS|139553|尝试：|139554|vagrant+plugin+install+vagrant-vbguest+vagrant+vbgues|139555|如果不起作用，请尝试对CentOS执行以下手动步骤：|139556|$+sudo+yum+update
$+sudo+yum+install+kernel-$(uname+-r)+kernel-devel+kernel-headers+#+or:+reinstall
$+rpm+-qf+/lib/modules/$(uname+-r)/build
kernel-2.6.32-573.18.1.el6.x86_64
$+ls+-la+/lib/modules/$(uname+-r)/build
$+sudo+reboot+#+and+re-login
$+sudo+ln+-sv+/usr/src/kernels/$(uname+-r)+/lib/modules/$(uname+-r)/build
$+sudo+/opt/VBoxGuestAdditions-*/init/vboxadd+setup|139557|entityMap|0|LINK|mutability|MUTABLE|url|https://www.virtualbox.org/wiki/Downloads|1|https://www.vagrantup.com/|2|https://virtualboxes.org/doc/installing-guest-additions-on-debian/|3^0|N|Q|0|0|0|L|P|7|7|1|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|C|Q|0|9|2B|2|6|2|0|A|P|0|N|4|B|8|3|0|0|0|5|1Q|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|19|S|0|0|0|0|0|0|0|0|6|7|0|0|1B|G|0|3|7|S|I|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|3Q|8|@]|9|@$A|3R|B|3S|1|3T]]|C|$]]|$1|D|3|E|5|6|7|3U|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|3V|8|@$A|3W|B|3X|H|I]]|9|@$A|3Y|B|3Z|1|40]]|C|$]]|$1|J|3|K|5|L|7|41|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|42|8|@]|9|@]|C|$]]|$1|Q|3|R|5|L|7|43|8|@]|9|@]|C|$M|N]]|$1|S|3|T|5|6|7|44|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|45|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|46|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|47|8|@]|9|@]|C|$]]|$1|10|3|-4|5|6|7|48|8|@]|9|@]|C|$]]|$1|11|3|12|5|13|7|49|8|@]|9|@]|C|$]]|$1|14|3|15|5|6|7|4A|8|@]|9|@]|C|$]]|$1|16|3|17|5|L|7|4B|8|@]|9|@]|C|$M|N]]|$1|18|3|19|5|6|7|4C|8|@]|9|@]|C|$]]|$1|1A|3|-4|5|6|7|4D|8|@]|9|@]|C|$]]|$1|1B|3|1C|5|13|7|4E|8|@]|9|@]|C|$]]|$1|1D|3|-4|5|6|7|4F|8|@]|9|@]|C|$]]|$1|1E|3|1F|5|6|7|4G|8|@$A|4H|B|4I|H|I]]|9|@]|C|$]]|$1|1G|3|1H|5|6|7|4J|8|@$A|4K|B|4L|H|I]]|9|@$A|4M|B|4N|1|4O]]|C|$]]|$1|1I|3|1J|5|6|7|4P|8|@$A|4Q|B|4R|H|I]]|9|@]|C|$]]|$1|1K|3|1L|5|6|7|4S|8|@$A|4T|B|4U|H|I]]|9|@$A|4V|B|4W|1|4X]]|C|$]]|$1|1M|3|-4|5|6|7|4Y|8|@]|9|@]|C|$]]|$1|1N|3|1O|5|L|7|4Z|8|@]|9|@]|C|$M|N]]|$1|1P|3|1Q|5|6|7|50|8|@$A|51|B|52|H|I]]|9|@]|C|$]]|$1|1R|3|19|5|6|7|53|8|@]|9|@]|C|$]]|$1|1S|3|19|5|6|7|54|8|@]|9|@]|C|$]]|$1|1T|3|-4|5|6|7|55|8|@]|9|@]|C|$]]|$1|1U|3|1V|5|13|7|56|8|@]|9|@]|C|$]]|$1|1W|3|-4|5|6|7|57|8|@]|9|@]|C|$]]|$1|1X|3|1Y|5|L|7|58|8|@]|9|@]|C|$M|N]]|$1|1Z|3|19|5|6|7|59|8|@]|9|@]|C|$]]|$1|20|3|-4|5|6|7|5A|8|@]|9|@]|C|$]]|$1|21|3|22|5|13|7|5B|8|@]|9|@]|C|$]]|$1|23|3|-4|5|6|7|5C|8|@]|9|@]|C|$]]|$1|24|3|25|5|L|7|5D|8|@]|9|@]|C|$M|N]]|$1|26|3|19|5|6|7|5E|8|@]|9|@]|C|$]]|$1|27|3|28|5|6|7|5F|8|@]|9|@]|C|$]]|$1|29|3|2A|5|6|7|5G|8|@]|9|@]|C|$]]|$1|2B|3|2C|5|6|7|5H|8|@$A|5I|B|5J|H|I]]|9|@]|C|$]]|$1|2D|3|-4|5|6|7|5K|8|@]|9|@]|C|$]]|$1|2E|3|2F|5|2G|7|5L|8|@]|9|@]|C|$]]|$1|2H|3|-4|5|6|7|5M|8|@]|9|@]|C|$]]|$1|2I|3|-4|5|6|7|5N|8|@]|9|@]|C|$]]|$1|2J|3|2K|5|6|7|5O|8|@]|9|@]|C|$]]|$1|2L|3|2M|5|6|7|5P|8|@]|9|@]|C|$]]|$1|2N|3|2O|5|L|7|5Q|8|@]|9|@]|C|$M|N]]|$1|2P|3|2Q|5|6|7|5R|8|@$A|5S|B|5T|H|I]]|9|@]|C|$]]|$1|2R|3|2S|5|L|7|5U|8|@]|9|@]|C|$M|N]]|$1|2T|3|2U|5|6|7|5V|8|@$A|5W|B|5X|H|I]]|9|@]|C|$]]|$1|2V|3|2W|5|6|7|5Y|8|@$A|5Z|B|60|H|I]|$A|61|B|62|H|I]]|9|@]|C|$]]|$1|2X|3|2Y|5|6|7|63|8|@]|9|@]|C|$]]|$1|2Z|3|30|5|L|7|64|8|@]|9|@]|C|$M|N]]|$1|31|3|32|5|6|7|65|8|@]|9|@]|C|$]]|$1|33|3|34|5|6|7|66|8|@]|9|@]|C|$]]|$1|35|3|36|5|6|7|67|8|@]|9|@]|C|$]]|$1|37|3|38|5|L|7|68|8|@]|9|@]|C|$M|N]]|$1|39|3|3A|5|6|7|69|8|@]|9|@]|C|$]]|$1|3B|3|3C|5|L|7|6A|8|@]|9|@]|C|$M|N]]|$1|3D|3|-4|5|6|7|6B|8|@]|9|@]|C|$]]]|3E|$3F|$5|3G|3H|3I|C|$3J|3K]]|3L|$5|3G|3H|3I|C|$3J|3M]]|3N|$5|3G|3H|3I|C|$3J|3O]]|3P|$5|3G|3H|3I|C|$3J|3K]]]]

You're using share folders, so you need to install <a href="https://www.virtualbox.org/wiki/Downloads" rel="noreferrer">VirtualBox Guest Additions</a> inside your virtual machine to support that feature.

<h3>Vagrant</h3>

If you're using <a href="https://www.vagrantup.com/" rel="noreferrer">Vagrant</a> (OS X: <code>brew cask install vagrant</code>), run:

<pre><code>vagrant plugin install vagrant-vbguest
vagrant vbguest
</code></pre>

In case it fails, check the logs, e.g.

<pre><code>vagrant ssh -c "cat /var/log/vboxadd-install.log"
</code></pre>

Maybe you're just missing the kernel header files.

<h3>VM</h3>

Inside VM, you should install Guest Additions, kernel headers and start the service and double check if kernel extension is running.

This depends on the guest operating system, so here are brief steps:

<ol>
<li>Install kernel include headers (required by VBoxLinuxAdditions).

<ul>
<li>RHEL: <code>sudo apt-get update &amp;&amp; sudo apt-get install kernel-devel</code></li>
<li>CentOS: <code>sudo yum update &amp;&amp; sudo yum -y install kernel-headers kernel-devel</code></li>
</ul></li>
<li>Install Guest Additions (this depends on the operating system).

<ul>
<li>Ubuntu: <code>sudo apt-get -y install dkms build-essential linux-headers-$(uname -r) virtualbox-guest-additions-iso</code>

If you can't find it, check by <code>aptitude search virtualbox</code>.</li>
<li><a href="https://virtualboxes.org/doc/installing-guest-additions-on-debian/" rel="noreferrer">Debian</a>: <code>sudo apt-get -y install build-essential module-assistant virtualbox-ose-guest-utils</code>

If you can't find it, check by <code>dpkg -l | grep virtualbox</code>.</li>
<li>manually by downloading the <a href="https://www.virtualbox.org/wiki/Downloads" rel="noreferrer">iso file</a> inside VM (e.g. <code>wget</code>) and installing it, e.g.

<ol>
<li><code>wget http://download.virtualbox.org/virtualbox/5.0.16/VBoxGuestAdditions_5.0.16.iso -P /tmp</code></li>
<li><code>sudo mount -o loop /tmp/VBoxGuestAdditions_5.0.16.iso /mnt</code></li>
<li><code>sudo sh -x /mnt/VBoxLinuxAdditions.run # --keep</code>

Extra debug: <code>cd ~/install &amp;&amp; sh -x ./install.sh /mnt/VBoxLinuxAdditions.run</code></li>
</ol></li>
</ul></li>
<li>Double check that kernel extensions are up and running:

<ul>
<li><code>sudo modprobe vboxsf</code></li>
</ul></li>
<li>Start/restart the service:

<ul>
<li>manually: <code>sudo /opt/VBoxGuestAdditions*/init/vboxadd setup</code> (add <code>sudo sh -x</code> to debug)</li>
<li>Debian: <code>sudo /etc/init.d/vboxadd-service start</code></li>
<li>Fedora: <code>sudo /etc/init.d/vboxdrv setup</code></li>
<li>CentOS: <code>sudo service VBoxService start</code></li>
</ul></li>
</ol>

<h3>Building the main Guest Additions module</h3>

If above didn't work, here are more sophisticated steps to fix it. This assumes that you've already VBoxGuestAdditions installed (as shown above).

The most common reason why mounting shared folder doesn't work may related to building Guest Additions module which failed. If in <code>/var/log/vboxadd-install.log</code> you've the following error:

<blockquote>
 The headers for the current running kernel were not found.
</blockquote>

this means either you didn't install kernel sources, or they cannot be found.

If you installed them already as instructed above, run this command:

<pre><code>$ sudo sh -x /opt/VBoxGuestAdditions-5.0.16/init/vboxadd setup 2&gt;&amp;1 | grep KERN
+ KERN_VER=2.6.32-573.18.1.el6.x86_64
+ KERN_DIR=/lib/modules/2.6.32-573.18.1.el6.x86_64/build
</code></pre>

So basically <code>vboxadd</code> script is expecting your kernel sources to be available at the following dir:

<pre><code>ls -la /lib/modules/$(uname -r)/build
</code></pre>

Check if the kernel dir exists (symbolic link points to the existing folder). If it's not, please install them to the right folder (e.g. in <code>/usr/src/kernels</code>).

So <code>vboxadd</code> script can enter your kernel source directory and run <code>make kernelrelease</code>, get the value and compare with your current kernel version.

Here is the logic:

<pre><code>KERN_VER=`uname -r`
KERN_DIR="/lib/modules/$KERN_VER/build"
if [ -d "$KERN_DIR" ]; then
 KERN_REL=`make -sC $KERN_DIR --no-print-directory kernelrelease 2&gt;/dev/null || true`
 if [ -z "$KERN_REL" -o "x$KERN_REL" = "x$KERN_VER" ]; then
 return 0
 fi
fi
</code></pre>

If the kernel version doesn't match with the sources, maybe you've to upgrade your Linux kernel (in case the sources are newer than your kernel).

<h3>CentOS</h3>

Try:

<pre><code>vagrant plugin install vagrant-vbguest vagrant vbgues
</code></pre>

If won't work, try the following manual steps for CentOS:

<pre><code>$ sudo yum update
$ sudo yum install kernel-$(uname -r) kernel-devel kernel-headers # or: reinstall
$ rpm -qf /lib/modules/$(uname -r)/build
kernel-2.6.32-573.18.1.el6.x86_64
$ ls -la /lib/modules/$(uname -r)/build
$ sudo reboot # and re-login
$ sudo ln -sv /usr/src/kernels/$(uname -r) /lib/modules/$(uname -r)/build
$ sudo /opt/VBoxGuestAdditions-*/init/vboxadd setup
</code></pre>

blocks|key|141828|text|这是唯一对我有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141829|安装Vagrant插件：vagrant-vbguest，它可以让你的VirtualBox访客更新到最新版本。|offset|length|141830|vagrant+plugin+install+vagrant-vbguest|code-block|syntax|javascript|141831|来源：https://github.com/aidanns/vagrant-reload/issues/4#issuecomment-230134083|141832|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dotless-de/vagrant-vbguest|1|https://github.com/aidanns/vagrant-reload/issues/4#issuecomment-230134083^0|0|C|F|0|0|0|3|21|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]]]

This was the only solution what worked for me:

Install Vagrant plugin: <a href="https://github.com/dotless-de/vagrant-vbguest" rel="noreferrer">vagrant-vbguest</a>, which can keep your VirtualBox Guest Additions up to date.

<pre><code>vagrant plugin install vagrant-vbguest
</code></pre>

Source: <a href="https://github.com/aidanns/vagrant-reload/issues/4#issuecomment-230134083" rel="noreferrer">https://github.com/aidanns/vagrant-reload/issues/4#issuecomment-230134083</a>

blocks|key|140776|text|我的主机是Windows10，我的虚拟机客户是流浪者构建的ubuntu。这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|140777|vagrant+plugin+install+vagrant-winnfsd|code-block|syntax|javascript|140778|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|$]]

My host is Windows10 my VM guest is ubuntu build by vagrant. This worked for me: 

<pre><code>vagrant plugin install vagrant-winnfsd
</code></pre>

blocks|key|2926728|text|使用VirtualBox+5.0.16/rXXX时出现了同样的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926729|安装了最新的VirtualBox+5.0.18和最新的Vagrant+1.9.3，问题到了。|2926730|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Had the same issue with VirtualBox 5.0.16/rXXX

Installed latest VirtualBox 5.0.18 and installed latest Vagrant 1.9.3, issue went toodles.

blocks|key|2714105|text|我添加为root用户|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2714106|/etc/rc.d/rc.local+
/root/mount-vboxsf.sh|code-block|syntax|javascript|2714107|然后|2714108|chmod+%2Bx+/etc/rc.d/rc.local|2714109|和示例脚本/root/mount-vboxsf.sh+(设置您自己的uid和gid选项)|offset|length|style|CODE|2714110|modprobe+-a+vboxguest+vboxsf+vboxvideo
mount+-t+vboxsf+NAME_SHARED_DIRECTORY+/media/sf_NAME_SHARED_DIRECTORY+-o+rw,uid=0,gid=0|2714111|您需要添加|2714112|chmod+%2B+/root/mount-vboxsf.sh|2714113|entityMap^0|0|0|0|0|5|L|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@$M|13|N|14|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

I added as root user

<pre><code>/etc/rc.d/rc.local 
/root/mount-vboxsf.sh
</code></pre>

then 

<pre><code>chmod +x /etc/rc.d/rc.local
</code></pre>

and the sample script <code>/root/mount-vboxsf.sh</code> (set your own the uid and gid options)

<pre><code>modprobe -a vboxguest vboxsf vboxvideo
mount -t vboxsf NAME_SHARED_DIRECTORY /media/sf_NAME_SHARED_DIRECTORY -o rw,uid=0,gid=0
</code></pre>

you need add 

<pre><code>chmod + /root/mount-vboxsf.sh
</code></pre>

blocks|key|2714120|text|我正在运行VirtualBox+5.1.20，并且遇到了类似的问题。下面是我找到补丁和我实现的补丁的url：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2714121|#+https://dsin.wordpress.com/2016/08/17/ubuntu-wrong-fs-type-bad-option-bad-superblock/
if+[+"5.1.20"+==+"${VBOXVER}"+];+then
++rm+/sbin/mount.vboxsf
++ln+-s+/usr/lib/VBoxGuestAdditions/mount.vboxsf+/sbin/mount.vboxsf
fi|code-block|syntax|javascript|2714122|这个链接类似于/usr/lib/VBoxGuestAdditions/other/mount.vboxsf，，而不是我在脚本摘录中的链接。|2714123|对于我在vagrant中用于添加的构建脚本：|2714124|https://github.com/rburkholder/vagrant/blob/master/scripts/additions.sh|offset|length|2714125|在https://www.virtualbox.org/ticket/16670上似乎有个解决办法|2714126|entityMap|0|LINK|mutability|MUTABLE|url|1|https://www.virtualbox.org/ticket/16670^0|0|0|0|0|0|1Z|0|0|1|13|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@]|9|@$M|14|N|15|1|16]]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@$M|18|N|19|1|1A]]|A|$]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|L]]|X|$5|T|U|V|A|$W|Y]]]]

I am running VirtualBox 5.1.20, and had a similar issue. Here is a url to where I found the fix, and the fix I implemented:

<pre><code># https://dsin.wordpress.com/2016/08/17/ubuntu-wrong-fs-type-bad-option-bad-superblock/
if [ "5.1.20" == "${VBOXVER}" ]; then
 rm /sbin/mount.vboxsf
 ln -s /usr/lib/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf
fi
</code></pre>

The link had something similar to /usr/lib/VBoxGuestAdditions/other/mount.vboxsf, rather than what I have in the script excerpt.

For a build script I use in vagrant for the additions:

<a href="https://github.com/rburkholder/vagrant/blob/master/scripts/additions.sh" rel="nofollow noreferrer" title="additions.sh">https://github.com/rburkholder/vagrant/blob/master/scripts/additions.sh</a>

Seems to be a fix at <a href="https://www.virtualbox.org/ticket/16670" rel="nofollow noreferrer">https://www.virtualbox.org/ticket/16670</a>

blocks|key|2926764|text|我有类似的问题，检查标题如果它不匹配，然后运行下面的命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926765|CentOS:+sudo+yum+update+&&+sudo+yum+-y+install+kernel-headers+kernel-devel|2926766|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have similar issue, check header if it's not match then run below command

CentOS: sudo yum update &amp;&amp; sudo yum -y install kernel-headers kernel-devel

blocks|key|140857|text|如果你在使用Debian：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|140858|1)通过Virtualbox+Guest+Additions+ISO文件删除所有已安装的包：|140859|sh+/media/cdrom/VBoxLinuxAdditions.run+uninstall|offset|length|style|CODE|140860|2)安装Virtualbox包：|140861|apt-get+install+build-essential+module-assistant+virtualbox-guest-dkms+virtualbox-guest-utils|140862|请注意，即使modprobe+vboxsf不返回任何内容(因此模块已正确加载)，vboxsf.so仍将调用virtualbox-guest-utils提供的名为mount.vboxsf的可执行文件。忽略这一点将使您无法理解错误的真正原因。|140863|strace+mount+/your-directory帮了大忙(在/sbin/mount.vboxsf上没有这样的文件或目录)。|140864|entityMap^0|0|0|0|1C|0|0|0|2L|0|6|F|14|9|1H|M|28|C|0|0|S|Y|I|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@$F|10|G|11|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@$F|13|G|14|H|I]|$F|15|G|16|H|I]|$F|17|G|18|H|I]|$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@$F|1C|G|1D|H|I]|$F|1E|G|1F|H|I]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|S|$]]

If you're on Debian:

1) remove all installed package through Virtualbox Guest Additions ISO file:

<code>sh /media/cdrom/VBoxLinuxAdditions.run uninstall</code>

2) install Virtualbox packages:

<code>apt-get install build-essential module-assistant virtualbox-guest-dkms virtualbox-guest-utils</code>

Note that even with <code>modprobe vboxsf</code> returning nothing (so the module is correctly loaded), the <code>vboxsf.so</code> will call an executable named <code>mount.vboxsf</code>, which is provided by <code>virtualbox-guest-utils</code>. Ignoring this one will prevent you from understanding the real cause of the error.

<code>strace mount /your-directory</code> was a great help (No such file or directory on <code>/sbin/mount.vboxsf</code>).

blocks|key|2714245|text|我的解决方案就是要更新来宾添加|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2714246|(单击设备->+Insert+Guest+Additions+CD+image)|2714247|entityMap^0|2|4|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

The solution for me was to update guest additions

(click Devices -> Insert Guest Additions CD image)

blocks|key|2926877|text|对我来说，在苹果电脑上，我的机器上存储了一个没有元数据的旧VirtualBox镜像，所以它没有更新到最新版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926878|旧镜像中安装了较旧版本的vbguest插件，而我机器上较新的vbguest插件无法使用。|2926879|因此，为了修复它，我只是删除了我的Vagrant所基于的镜像，然后Vagrant下载了更新的版本，它工作得很好。|2926880|#+Remove+an+old+version+of+the+virtual+box+image+that+my+vagrant+was+using++++
$+vagrant+box+remove+centos/7+|code-block|syntax|javascript|2926881|您可以通过运行以下命令找出您的机器上缓存了哪些盒子：|2926882|$+vagrant+box+list|2926883|我也升级了我的vbguest插件，在我之前的尝试中，使用了以下过程，但我不认为这有什么帮助。仅供参考！|2926884|#+Get+rid+of+old+plugins
vagrant+plugin+expunge+

#+Globally+install+the+latest+version+of+the+vbguest+plugin`
vagrant+plugin+install+vagrant-vbguest+|2926885|如果你在添加来宾时发现fails+the+box失败，你可以尝试执行以下操作，以确保插件正确安装。这将为您的系统下载最新的基于镜像(适用于我的CentOS)和may+resolve+the+issue+(适用于我！)|offset|length|2926886|$+vagrant+box+update|2926887|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dotless-de/vagrant-vbguest/issues/298^0|0|0|0|0|0|0|0|0|27|L|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|19|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|1B|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|1D|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|1E|8|@]|9|@$U|1F|V|1G|1|1H]]|A|$]]|$1|W|3|X|5|H|7|1I|8|@]|9|@]|A|$I|J]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

For me, on a mac, it turned out I had an old VirtualBox image stored on my machine that didn't have metadata, so it wasn't being updated to the latest version.

That old image had an older version of the vbguest plugin installed in it, which the newer vbguest plugin on my machine couldn't work with.

So to fix it, I just removed the image that my Vagrant was based on, and then Vagrant downloaded the newer version and it worked fine. 

<pre><code># Remove an old version of the virtual box image that my vagrant was using 
$ vagrant box remove centos/7 
</code></pre>

You can find out which boxes you have cached on your machine by running:

<pre><code>$ vagrant box list
</code></pre>

I had also upgraded my vbguest plugin in my earlier attempts at getting this to work, using the following process, but I don't think this helped. FYI !

<pre><code># Get rid of old plugins
vagrant plugin expunge 

# Globally install the latest version of the vbguest plugin`
vagrant plugin install vagrant-vbguest 
</code></pre>

If you find bring the box fails on guest addtions, you can try doing the following to ensure the plugins install correctly. This downloads the latest based image for your system (for me CentOS), and <a href="https://github.com/dotless-de/vagrant-vbguest/issues/298" rel="nofollow noreferrer">may resolve the issue</a> (it did for me!)

<pre><code>$ vagrant box update
</code></pre>

blocks|key|143205|text|一个更新为我做了这个把戏！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|143206|$+vagrant+box+update
$+vagrant+plugin+install+vagrant-vbguest+|code-block|syntax|javascript|143207|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|$]]

An update did the trick for me !

<pre><code>$ vagrant box update
$ vagrant plugin install vagrant-vbguest 
</code></pre>

blocks|key|2714292|text|下面两个命令适用于我。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2714293|vagrant+ssh
sudo+mount+-t+vboxsf+-o+uid=1000,gid=1000+vagrant+/vagrant|code-block|syntax|javascript|2714294|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|$]]

Below two commands works for me.

<pre><code>vagrant ssh
sudo mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
</code></pre>

I'm using VirtualBox with OS X as host and CentOS on the guest VM.

In OS X I created folder <code>myfolder</code>, added it as shared folder to the VM, turned on the VM, in CentOS created folder <code>/home/user/myfolder</code> and typing:

<pre><code>sudo mount -t vboxsf myfolder /home/user/myfolder
</code></pre>

and have output:

<pre><code>/sbin/mount.vboxsf: mounting failed with the error: No such device
</code></pre>

What I'm doing wrong?

UPDATED:

<code>Guest Additions</code> installed.

VirtualBox: mount.vboxsf: mounting failed with the error: No such device

日志文件

虚拟机

Windows

CentOS

Ubuntu

Fedora

Debian

Linux

我使用VirtualBox和OS X作为主机，在来宾VM上使用CentOS。在OS X中，我创建了文件夹myfolder，将其作为共享文件夹添加到虚拟机，打开虚拟机，在CentOS中创建了文件夹/home/user/myfolder，然后键入：sudo mount -t vboxsf myfolder /home/us...

问VirtualBox: mount.vboxsf:挂载失败，错误为:没有这样的设备
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VirtualBox: mount.vboxsf:挂载失败，错误为:没有这样的设备EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VirtualBox: mount.vboxsf:挂载失败，错误为:没有这样的设备
EN