Vagrant Error: Unable to Mount VirtualBox Shared Folders (Guest Additions, vboxsf)

/sbin/mount.vboxsf: mounting failed with the error: no such device
mount: unknown filesystem type 'vboxsf'
virtualbox guest additions
vagrant vboxsf
vagrant virtualbox guest additions
vagrant-vbguest
no virtualbox guest additions installation found.
virtualbox mount vboxsf
The Issue

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.

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 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

Here's a screenshot of my Windows command line:

And here's a text version:

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
My Setup
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
Plugins & Extensions Installed
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.

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 shows the plugin as installed, but I get the same error on vagrant up.

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

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

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

  3. 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.

This problem is solved in VirtualBox 5.1.18.

Vagrant was unable to mount VirtualBox shared folders · Issue #296 , This filesystem is made available via the VirtualBox Guest Additions and kernel Vagrant was unable to mount VirtualBox shared folders #296 /sbin/mount.​vboxsf: mounting failed with the error: No such file or directory. Failed to mount folders in Linux guest. This is usually because the "vboxsf" file system is not available. Please verify that the guest additions are properly installed in the guest and can work properly.

You can downgrade VirtualBox or edit the line in the file:

On my setup this was Line 206 of:

C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.9.2\lib\vagrant\util\platform.rb

on my host machine.

I did this and it worked fine on Windows 10! I would like to add what I did with line 206:

Before edit: "\\?\" + path.gsub("/", "\")

After edit: path.gsub("/", "\")

Vagrant was unable to mount VirtualBox shared folders mount -t , Vagrant was unable to mount VirtualBox shared folders mount -t vboxsf -o made available via the VirtualBox Guest Additions and kernel module. /sbin/​mount.vboxsf: shared folder '/ansible' was not found (check VM settings / spelling) Sign up for free to subscribe to this conversation on GitHub. web: /vagrant => /home/david/code/turbine/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 plugin install vagrant-vbguest

This didn't work for me, it seems to be incompatible with vagrant 1.9.2, I uninstalled the latest version of virtual box (5.1.16) and installed version 5.1.12 with the latest version of vagrant 1.9.2 and homestead and it works for me.

Vagrant was unable to mount VirtualBox shared folders – Solved , Vagrant was unable to mount VirtualBox shared folders – Solved default: Checking for guest additions in VM default: The guest additions on was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output  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.

(synced folder not working (Ubuntu 16.04 hosting , a similar test works fine for a guest of type "ubuntu/xenial64 v20180215.0.0". vboxguest || echo "*** something went wrong while attempting to install the guest additions" HERE Vagrant was unable to mount VirtualBox shared folders. The error output from the command was: mount: unknown filesystem type 'vboxsf'. latest Overview. Zulip overview. Getting started; Contributing to Zulip. Community; Ways to contribute

There can be multiple cause :

  1. The version of the guest addition is not matching the version of VirtualBox, for this you can update the version of the guest addition by running vagrant plugin install vagrant-vbguest
  2. You hit a bug of vagrant with NFS on Windows : should be fixed so maybe try to update to the latest release of Vagrant and VirtualBox
  3. In this github issue https://github.com/fideloper/Vaprobash/issues/92, there is two thing that you can test : use the winnfsd plugin (https://github.com/winnfsd/vagrant-winnfsd) or try to configure the default mount with no NFS

I had the same issue, and it was just the guest addition that was not up-to-date ...

UDPATE : The bug on Vagrant with NFS on Windows (point 2) has been fixed in version 5.1.18, re-appears in version 5.1.20 and is fixed again in version 5.2.

Vagrant was unable to mount VirtualBox shared folders. This, Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. Robert Askam in vagrant up . This filesystem is made available via the VirtualBox Guest Additions and kernel module. The scenario is that my dev environment is on a Vagrant box on my laptop (host) and I would like to do browser testing in a vitualbox vm, so I need to see one vm from another. The vagrant box's port is :8080 which is forwarded to the host on the same port :8080. So I can see the server from the hos

Mount failed (unknown file system) in virtualbox in ubuntu 14.04 and , 2) install virtual box guest additions (referenced from here) /sbin/mount.vboxsf: mounting failed with the error: No such device vagrant@packer-virtualbox-iso​:~$ sudo mount -t vboxsf new ~/new Being logged as a root I mounted the shared folder: #mount -t vboxsf shared /home//shared_folder;; And all began to work. 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.

vagrant unable to mount shared folders, sign up log in For context, the command attempted was: mount -t vboxsf -o Looks like the latest version of Virtualbox (5.1.18) fixed this. Shared Folders: fixed case insensitive filename access (5.1.16 fixed access to long pathes (5.1.​16 regression; Windows guests only; bugs #14651, #16564). I am starting to develop multi-machine vagrant setups. I have noticed two methods of naming conventions in vagrant files for defining the machine name. The first method is with a "colon"

Vagrant virtualbox unable to mount shared folders error fix – webstuff, Error: "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." To fix it  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.

Comments
  • Hey Eric, have you found any solution? My friend experienced this problem too and I'm helping him to find the solution, but none of what I've found worked for him.
  • @softtama Best and the easiest solution is downgrade virtualbox to 5.1.14. Related to issue github.com/mitchellh/vagrant/issues/8352
  • This problem seems disappeared when I upgrade to 5.1.18 from 5.1.16.
  • I love the detailed answers that others gave, however, this one was the simplest and it worked. Unfortunately, it indicates that there was an issue that apparently wasn't well-known until shortly after I posted this question. Does that mean that no newbie has been able to install VirtualBox + Guest Additions for the past 3 years (since 2014 at least) due to this issue, or is it only an issue on VirtualBox on Windows?
  • Unfortunately this problem reappeared just now when I upgraded from 5.1.18 to 5.1.20
  • @SzczepanHołyszewski same here on 5.1.24
  • For me it also appeared with 5.1.20 again - but now there´s VirtualBox 5.2.0 out! Upgrade fixed it again for me. Eric Hepperle - CodeSlayer2010 - if you need a complete example for a working multi-machine-setup with Windows AND Linux, check out the first parts of this article blog.codecentric.de/en/2017/09/… (paragraph "A multi-machine Windows & Linux mixed OS Vagrant setup for Docker Swarm").
  • It is a solution until they fix it there github.com/mitchellh/vagrant/issues/8352
  • Updated everything: virtual box, vagrant (1.9.2), Guest Addition 5.1.16, the above method works. Note that you have to put a double backslash to escape the above line after edit.
  • This took me three days now to figure out. Thanks a lot for sharing this - it should be accepted as the correct answer (if it fixes the problem @Eric as well)!
  • this worked for me in windows 7 x64, using vagrant 1.9.2, virtualbox 5.1.16.! thanks!
  • This worked for me☺ ! I have Vagrant 1.9.2 and Virtual Box 5.1.16r113841
  • yeeeeeeeeeeeeeeeeeeeeeesssss.