无业游民错误:无法挂载VirtualBox共享文件夹(来宾添加，vboxsf) [英] Vagrant Error: Unable to Mount VirtualBox Shared Folders (Guest Additions, vboxsf)

问题描述

我在Windows 10上安装了Vagrant，因此可以在虚拟机中创建个人本地开发环境.我所读到的有关Vagrant的所有内容都说我什至可以启动多个系统，并使用NAT端口转发测试它们之间的通信.但是首先，我只想创建一个开发环境虚拟机，然后再进行其余工作.

I installed Vagrant on Windows 10 so I can create a personal local development environment in a virtual machine. Everything I've read about Vagrant said I can even spin up multiple systems and test communication between them with NAT port forwarding. But first, I just want to get one development environment virtual machine created before I go too far with the rest of it.

我根据此SitePoint教程安装了VirtualBox，Vagrant，PuTTy和PuTTYGen: https://www.sitepoint.com/getting-started-vagrant-windows/.接下来，我在C:驱动器上创建了一个无所不在的项目文件夹，做了vagrant init，删除了Vagrantfile，最后是了vagrant init ubuntu/trusty64.然后我做了vagrant up，但是该过程失败并显示以下错误:

I installed VirtualBox, Vagrant, PuTTy, and PuTTYGen, per this SitePoint tutorial: https://www.sitepoint.com/getting-started-vagrant-windows/. Next I created a vagrant project folder on C: drive, did vagrant init, deleted the Vagrantfile, and finally, vagrant init ubuntu/trusty64. Then I did vagrant up, but the process failed with the error:

Vagrant无法挂载VirtualBox共享文件夹.通常是 因为文件系统"vboxsf"不可用.该文件系统是 通过VirtualBox Guest Additions和内核模块提供. 请确认这些来宾添加项已正确安装在 来宾.这不是Vagrant中的错误，通常是由错误引起的 无业游民的箱子.对于上下文，尝试的命令为:

Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid = 1000，gid = 1000流浪者/vagrant

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

该命令的错误输出为:

:没有这样的文件或目录

: No such file or directory

这是我的Windows命令行的屏幕截图:

Here's a screenshot of my Windows command line:

这是文本版本:

C:\vagrant\sitepoint-test-2017-02-05>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: A newer version of the box 'ubuntu/trusty64' is available! You currently
==> default: have version '20160602.0.0'. The latest is version '20170202.0.0'. Run
==> default: `vagrant box update` to update.
==> default: Setting the name of the VM: sitepoint-test-2017-02-05_default_1486399403587_55255
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => C:/vagrant/sitepoint-test-2017-02-05
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

: No such file or directory

我的设置

OS: Microsoft Windows [Version 10.0.14393]
VirtualBox Version: 4.3.10 r93012
GuestAdditions Version: ???
Vagrant Version: 1.9.1 (Latest)
PuTTy Version: 0.67
PuTTYGen Version: 0.67

插头和放大器;已安装扩展程序

Vagrant:
- vagrant-share (1.1.6, system)
- vagrant-vbguest (0.13.0)

我已经尝试过的东西

这篇文章似乎是最有希望的我的研究.

What I tried already

This post seemed the most promising in my research.

不幸的是，没有提供的解决方案，也没有提供的任何链接都解决了该问题.我已经尝试了很多东西，但是我不是系统管理员(我想这是您需要对此进行故障排除的技能组).特别令人不安的是，最近有迹象表明，2013/2014年的许多解决方案"不再起作用.这些解决方案讨论与符号链接不起作用有关的事情，安装诸如vagrant-vbguest之类的插件，以及有关vbox添加项不匹配的问题.我不是很了解所有这些，但是我尽了最大的努力.这是我已经尝试过但尚未解决的问题:

Unfortunately, none of the solutions offered, nor any of the links provided solved the issue. I've tried a bunch of stuff already, but I'm not a system admin (which, I'm guessing is the skillset that you'd need to troubleshoot this). It was particularly troubling that many of the "solutions" from 2013/2014, are more recently indicated as not working any more. These solutions talk about something to do with symlinks not working, installing plugins like vagrant-vbguest, and something about vbox additions not matching something. I don't really understand all of that, but I tried my best. Here is what I tried already that hasn't solved it yet:

1. vagrant plugin install vagrant-vbguest. Vagrant显示插件已安装，但是在vagrant up上我收到相同的错误.

1. vagrant plugin install vagrant-vbguest. Vagrant shows the plugin as installed, but I get the same error on vagrant up.

在研究此问题时没有提供有效解决方案的链接列表.

List of links I read in researching this issue that provided no working solution.

• 流浪者无法在Windows 7上通过VirtualBox Guest Additions在Linux guest虚拟机中安装
• Vagrant-我该怎么办挂载virtualbox共享文件夹? ("vboxsf"不可用)
• https://github.com/mitchellh/vagrant/issues/3341 #issuecomment-144271026
• https://www.virtualbox.org/ticket/12879 (此VirtualBox票证在其他列出的链接中被海报引用了.不幸的是，这张票无法解决问题.它没有固定并且仍然损坏...或者...也许这张票是相关的，但与我所遇到的问题略有不同和其他人仍在体验中.
• https://gist.github.com/fernandoaleman/5083680

• Vagrant unable to mount in Linux guest with VirtualBox Guest Additions on Windows 7
• Vagrant - How can I mount the virtualbox shared folder? ("vboxsf" not available)
• https://github.com/mitchellh/vagrant/issues/3341#issuecomment-144271026
• https://www.virtualbox.org/ticket/12879 (This VirtualBox ticket is referenced by posters in some of the other listed links. Unfortuantely, this ticket doesn't fix the issue. It's not fixed and is still broken ... OR ... perhaps this ticket is related, but slightly differerent than the issue I and others are still experiencing).
• https://gist.github.com/fernandoaleman/5083680
• VAGRANT SHARED FOLDERS DO NOT MOUNT - Windows 7 - Vagrant 1.7.4 - Ubuntu 12.04 precise64 - VirtualBox 5.0.10 with Guest Additions

我的问题

1. 我怀疑问题出在VirtualBox，而不是Vagrant.这是真的吗?

1. I suspect the issue is with VirtualBox, not Vagrant. Is this true?

如何解决此问题，以便继续学习本教程?

How can I fix this so I can continue with the tutorial?

自2014年左右以来，关于Stack Overflow的Vagrant问题似乎急剧下降.这是什么原因? Vagrant/VirtualBox不再被视为最佳实践"吗?有没有更好的解决方案，所以用户可以忽略无业游民的问题?

There seems to have been a drastic drop in Vagrant questions answered on Stack Overflow since around 2014. What is the reason for this? Is Vagrant/VirtualBox no longer considered "best practice"? Is there a better solution so users are ignoring the Vagrant questions?

同样，我不是系统管理员，但是我精通技术并且可以按照技术说明进行操作.

Again, I'm not a system administrator, but I am technically savvy and can follow technical directions.

推荐答案

此问题已在VirtualBox 5.1.18中解决.

This problem is solved in VirtualBox 5.1.18.

这篇关于无业游民错误:无法挂载VirtualBox共享文件夹(来宾添加，vboxsf)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！