Vagrant error Failed to mount folders in Linux guest

Question

I have some issues with Vagrant shared folders  my base system is Ubuntu 13 10 desktop   I do not understand why I have this error is something that is not right configured   Is a NFS issue or Virtualbox Guest Additions   I have tried with different many boxes but the same issue   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  The command attempted was       mount -t vboxsf -o uid  id -u vagrant  gid  getent group vagrant   cut -d  -f3   vagrant  vagrant     mount -t vboxsf -o uid  id -u vagrant  gid  id -g vagrant   vagrant  vagrant   Here is the complete process after vagrant up      vagrant up Bringing machine  default  up with  virtualbox  provider       gt  default  Importing base box  u131032        gt  default  Matching MAC address for NAT networking       gt  default  Setting the name of the VM  vagrant default 1396020504136 46442    gt  default  Clearing any previously set forwarded ports       gt  default  Clearing any previously set network interfaces       gt  default  Preparing network interfaces based on configuration        default  Adapter 1  nat     default  Adapter 2  hostonly    gt  default  Forwarding ports        default  22   gt  2222  adapter 1     gt  default  Running  pre-boot  VM customizations       gt  default  Booting VM       gt  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  Error  Connection timeout  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying        default  Error  Remote connection disconnect  Retrying       gt  default  Machine booted and ready  GuestAdditions versions on your host  4 3 10  and guest  4 2 16  do not match     Stopping VirtualBox Additions       done  Reading package lists    Building dependency tree    Reading state information    The following packages were automatically installed and are no longer required    dkms libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfontenc1   libgl1-mesa-dri libglapi-mesa libice6 libllvm3 3 libpciaccess0 libpixman-1-0   libsm6 libtxc-dxtn-s2tc0 libxaw7 libxcomposite1 libxdamage1 libxfixes3   libxfont1 libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1 libxt6   x11-common x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils   xserver-common xserver-xorg-core Use  apt-get autoremove  to remove them  The following packages will be REMOVED    virtualbox-guest-dkms  virtualbox-guest-utils  virtualbox-guest-x11  0 upgraded  0 newly installed  3 to remove and 0 not upgraded  After this operation  11 1 MB disk space will be freed   Reading database     65615 files and directories currently installed   Removing virtualbox-guest-dkms      -------- Uninstall Beginning -------- Module   virtualbox-guest Version  4 2 16 Kernel   3 11 0-18-generic  i686  -------------------------------------  Status  Before uninstall  this module version was ACTIVE on this kernel   vboxguest ko   - Uninstallation    - Deleting from   lib modules 3 11 0-18-generic updates dkms   - Original module    - No original module was found for this module on this kernel     - Use the dkms install command to reinstall any previous module version    vboxsf ko   - Uninstallation    - Deleting from   lib modules 3 11 0-18-generic updates dkms   - Original module    - No original module was found for this module on this kernel     - Use the dkms install command to reinstall any previous module version    vboxvideo ko   - Uninstallation    - Deleting from   lib modules 3 11 0-18-generic updates dkms   - Original module    - No original module was found for this module on this kernel     - Use the dkms install command to reinstall any previous module version   depmod      DKMS  uninstall completed   ------------------------------ Deleting module version  4 2 16 completely from the DKMS tree  ------------------------------ Done  Removing virtualbox-guest-x11     Purging configuration files for virtualbox-guest-x11     Removing virtualbox-guest-utils     Purging configuration files for virtualbox-guest-utils     Processing triggers for ureadahead     Processing triggers for man-db     Reading package lists    Building dependency tree    Reading state information    dkms is already the newest version  dkms set to manually installed  linux-headers-3 11 0-18-generic is already the newest version  linux-headers-3 11 0-18-generic set to manually installed  The following packages were automatically installed and are no longer required    libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libfontenc1 libgl1-mesa-dri   libglapi-mesa libice6 libllvm3 3 libpciaccess0 libpixman-1-0 libsm6   libtxc-dxtn-s2tc0 libxaw7 libxcomposite1 libxdamage1 libxfixes3 libxfont1   libxkbfile1 libxmu6 libxpm4 libxrandr2 libxrender1 libxt6 x11-common   x11-xkb-utils xfonts-base xfonts-encodings xfonts-utils xserver-common   xserver-xorg-core Use  apt-get autoremove  to remove them  0 upgraded  0 newly installed  0 to remove and 0 not upgraded  Copy iso file  usr share virtualbox VBoxGuestAdditions iso into the box  tmp VBoxGuestAdditions iso mount  block device  tmp VBoxGuestAdditions iso is write-protected  mounting read-only Installing Virtualbox Guest Additions 4 3 10 - guest version is 4 2 16 Verifying archive integrity    All good  Uncompressing VirtualBox 4 3 10 Guest Additions for Linux             VirtualBox Guest Additions installer Copying additional installer modules     Installing additional modules     Removing existing VirtualBox DKMS kernel modules    done  Removing existing VirtualBox non-DKMS kernel modules    done  Building the VirtualBox Guest Additions kernel modules    done  Doing non-kernel setup of the Guest Additions    done  Starting the VirtualBox Guest Additions    done  Installing the Window System drivers Could not find the X Org or XFree86 Window System  skipping  An error occurred during installation of VirtualBox Guest Additions 4 3 10  Some functionality may not work as intended  In most cases it is OK that the  Window System drivers  installation failed     gt  default  Checking for guest additions in VM       gt  default  Setting hostname       gt  default  Configuring and enabling network interfaces       gt  default  Exporting NFS shared folders       gt  default  Preparing to edit  etc exports  Administrator privileges will be required    nfsd running sudo   usr bin exportfs  command not found    gt  default  Mounting NFS shared folders       gt  default  Mounting shared folders        default   vagrant   gt   home me Documents Work project vagrant 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  The command attempted was   mount -t vboxsf -o uid  id -u vagrant  gid  getent group vagrant   cut -d  -f3   vagrant  vagrant mount -t vboxsf -o uid  id -u vagrant  gid  id -g vagrant   vagrant  vagrant   My Vagrantfile configuration is      - - mode  ruby - -   vi  set ft ruby      Vagrantfile API syntax version  Don t touch unless you know what you re doing  VAGRANTFILE API VERSION    2   personalization   File expand path     Personalization     FILE    load personalization  Vagrant configure VAGRANTFILE API VERSION  do  config    config vm box    base box   config vm box url    base box url    config vm hostname    vhost     dev     config hostsupdater aliases     api      vhost     dev    mysql      vhost     dev     config hostsupdater remove on suspend   true      set auto update to ture to check the correct      additions version when booting the machine   config vbguest auto update   true   config vbguest auto reboot   true    config vm network  private network  ip   ip    config vm synced folder          srv www vhosts      vhost     dev   type   nfs     config vm provider  virtualbox do  v      v customize   modifyvm    id   --memory   2048      v customize   modifyvm    id   --cpus    1       v customize   modifyvm    id   --cpuexecutioncap    100       v customize   modifyvm    id   --ioapic    off       v customize   modifyvm    id   --natdnshostresolver1    on     end    config vm provision  shell  do  s      s path    vagrant-bootstrap sh      s args    vhost          mysql password          application database   end end   The Personalization file is      Name of the vhost to create  vhost    project     Use the Ubunut 32bit or 64bit  base box url    http   cloud-images ubuntu com vagrant saucy current saucy-server-cloudimg-i386-vagrant-disk1 box     VM IP  ip    192 168 7 7     Base box name  base box    u131032     MySQL  mysql password    admin   application database    project    The following plugins are enabled in Vagrant     vagrant plugin list vagrant-hostsupdater  0 0 11  vagrant-login  1 0 1  system  vagrant-share  1 0 1  system  vagrant-vbguest  0 10 0

User · Answer

I arrived at this page whilst looking for the same error message. For me the cause was different: I had ran a yum update on the system that installed a new kernel. The guest additions where out of date so it couldn't load them.

I rebuilt them with

sudo /etc/init.d/vboxadd setup

And a vagrant reload later my guest was up and running again.

I'm just adding it here in case someone else gets here the same way I did.

Edit (Per KCD's comment):
It is possible that you get an error saying:

The headers for the current running kernel were not found

This can be resolved by installing kernel-devel (yum install kernel-devel)

User · Answer

Fix Step by step   If you not have vbguest plugin  install it     vagrant plugin install vagrant-vbguest   Run Vagrant  It is show a error     vagrant up   Login on VM    vagrant ssh   Fix   In the guest  VM logged      sudo ln -s  opt VBoxGuestAdditions-4 3 10 lib VBoxGuestAdditions  usr lib VBoxGuestAdditions   Back on the host  reload Vagrant    vagrant reload

User · Answer

The plugin vagrant-vbguest   solved my problem      vagrant plugin install vagrant-vbguest   Output     vagrant reload    gt  default  Attempting graceful shutdown of VM           gt  default  Machine booted and ready  GuestAdditions 4 3 12 running --- OK     gt  default  Checking for guest additions in VM       gt  default  Configuring and enabling network interfaces       gt  default  Exporting NFS shared folders       gt  default  Preparing to edit  etc exports  Administrator privileges will be required       gt  default  Mounting NFS shared folders       gt  default  VM already provisioned  Run  vagrant provision  or use  --provision  to force it   Just make sure you are running the latest version of VirtualBox

User · Answer

I was running Vagrant with VirtualBox 5 1 X  and had to downgrade to VirtualBox 5 0 40  and install the vbguest plugin to solve this problem  My steps were   Uninstall VirtualBox 5 1 X Install Vagrant 5 0 40 Reboot my machine Run vagrant up for my vagrant  It ll fail  Run vagrant plugin install vagrant-vbguest while my VM is running  to install the vagrant plugin  This manages syncing VirtualBox Guest versions between host and guest  Run vagrant reload to reload my virtual machine Magic

User · Answer

One more step I had to complete after following the first suggestion that kenzie made was to run the mount commands listed in the error message with sudo from the Ubuntu command line  14 04 Server   After that  everything was good to go

User · Answer

Just for future reference  this problem happened with me  using Vagrant 1 7 4 and VirtualBox 5 0 10 r104061  when I provisioned a shared folder in   and created a symbolic link to my home folder  Something like this    folder   folder - gt   folder   Apparently  this operation is not allowed by Vagrant due to security purposes and throws the described error   I solved it by provisioning the desired folder directly to my home directory  such as  home vagrant folder

User · Answer

For me  with VBoxGuestAdditions 5 1 20  the problem was that  sbin mount vboxsf pointed to the wrong location   sudo ln -sf  opt VBoxGuestAdditions-5 1 20 lib VBoxGuestAdditions mount vboxsf  sbin mount vboxsf  fixed it for me

User · Answer

In my case on a previously working Ubuntu 16 04 image  the error started after installing vagrant-vbguest for a different vagrant image  and then starting the Ubuntu VM   It upgraded the guest additions to 5 1 20  and since then the mounts started failing   Updated the box  apt update   upgrade and the same  vbguest would install the newer 5 1 20 version   It was solved by manually running   sudo apt-get update sudo apt-get install virtualbox-guest-dkms    And also disabling the  config vbguest auto update   false for this VM  might not be necessary

User · Answer

This seems to be due to an incompatibility with the vbguest vagrant plugin and the latest version s  of vagrant  It is trying to update the guest additions and failing to do it completely properly

User · Answer

This is 2017  Just in case someone faces the same issue    For bento centos-6 7  I was getting same error  That was solved by adding plugin vagrant-vbguest  0 13 0   c   vagrant plugin install vagrant-vbguest  Box url  http   opscode-vm-bento s3 amazonaws com vagrant virtualbox opscode centos-7 0 chef-provisionerless box  This centos-7 version was giving me same error   Error      gt  build  Mounting shared folders        build   vagrant   gt  C  projects  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    sbin mount vboxsf  mounting failed with the error  No such device   My Configuration   C  projects gt vagrant -v Vagrant 1 9 1  C  projects gt  vboxmanage -v 5 0 10r104061  C  projects gt vagrant plugin list vagrant-cachier  1 2 1  vagrant-hostmanager  1 8 5  vagrant-hosts  2 8 0  vagrant-omnibus  1 5 0  vagrant-share  1 1 6  system  vagrant-vbguest  0 13 0  vagrant-vbox-snapshot  0 0 10    Since I already have vagrant-vbguest plugin  it tries to update the VBoxGuestAdditions in centos-7 when it sees different version of VBGuestAdditions are installed in Host 5 0 10 and guest 4 3 20    I even have checked that symbolic link exists    root build VBoxGuestAdditions   ls -lrt  usr lib lrwxrwxrwx   1 root root   53 Jan 14 12 06 VBoxGuestAdditions - gt   opt VBoxGuestAdditions-5 0 10 lib VBoxGuestAdditions  root build VBoxGuestAdditions   mount -t vboxsf -o uid 1000 gid 1000 vagrant  vagrant  sbin mount vboxsf  mounting failed with the error  No such device   This did not work as suggested by user3006381  vagrant ssh sudo yum -y install kernel-devel sudo yum -y update exit vagrant reload --provision   Solution for centos-7  as given by psychok7 worked  Diabled autoupdate   config vbguest auto update   false Then vagrant destroy --force and vagrant up  Result   javareport  Guest Additions Version  4 3 20 javareport  VirtualBox Version  5 0    gt  javareport  Setting hostname       gt  javareport  Configuring and enabling network interfaces       gt  javareport  Mounting shared folders    javareport   vagrant   gt  C  projects  C  project gt

User · Answer

Try like it   vagrant plugin install vagrant-vbguest   In Vagrantfile add   config vbguest iso path    http   download virtualbox org virtualbox VERSION VBoxGuestAdditions VERSION iso  config vbguest auto update   false config vbguest installer arguments    w --nox11 -- --force    Run   vagrant vbguest --do install -f -b  vagrant reload

User · Answer

Your log complains about not finding exportfs       sudo   usr bin exportfs  command not found  The exportfs makes local directories available for NFS clients to mount

User · Answer

In configuration where windows is a host  and linux is a guest I found solution of the same problem in other place   So again  the error message was  Failed to mount folders in Linux guest  This is usually because the  vboxsf  file system is not available          This was caused because I have made mistake by doing symlink inside the guest system from  vagrant into  home vagrant vagrant  The point is  that the directory  vagrant is a normal linux directory that has a symlink  so all ok   but when booting up by  vagrant up   it tries to mount windows directory on that place  and windows directory cannot work as a symlink  Windows host does not support linux symlinks   So what You can do then  is to ssh into guest  remove the symlink wherever You have it  and reload machine   In my configuration it was  Vagrant 1 7 2  VBoxGuestAdditions 4 3 28 and VBox 4 3 28

User · Answer

Install the vagrant-vbguest plugin by running this command   vagrant plugin install vagrant-vbguest

User · Answer

I believe this is the most updated answer now and it worked for me   Guest Additions Version  5 0 6  VirtualBox Version  4 3 16  Ubuntu 14 04 LTS   https   github com mitchellh vagrant issues 3341 issuecomment-144271026  Basically i says   Simple and Quick Solution for Failed to mount folders in Linux guest issue   Add the following line to your Homestead Vagrantfile   config vbguest auto update   false Your Homestead Vagrantfile should looks like this         Vagrant configure VAGRANTFILE API VERSION  do  config        To avoid install and uninstall VBoxGuessAdditions during vagrant provisioning      config vbguest auto update   false       Save it and execute    vagrant destroy --force   vagrant up

User · Answer

I experienced the same issue with Centos 7  I assume due to an outdated kernel in combination with an updated version of VirtualBox  Based on Blizz s update  this is what worked for me  vagrant-vbguest plugin already installed    vagrant ssh sudo yum -y install kernel-devel sudo yum -y update exit vagrant reload --provision

User · Answer

As mentioned in Vagrant issue  3341 this was a Virtualbox bug  12879   It affects only VirtualBox 4 3 10 and was completely fixed in 4 3 12

User · Answer

Update February 2016  This took me hours to solve independently  Yes  this problem does still exist with latest Vagrant and Virtual Box installs      vagrant -v Vagrant 1 8 1    vboxmanage -v 5 0 14r105127   The symptoms for me were messages something like    Checking for guest additions in VM    The guest additions on this VM do not match the installed version of VirtualBox   followed by a failure to mount NFS drives   1   Install the vagrant-vbguest plugin   Depending on version of Vagrant you are using  issue one of the following commands     For vagrant  lt  1 1 5   vagrant gem install vagrant-vbguest    For vagrant 1 1 5    vagrant plugin install vagrant-vbguest   Next  do vagrant halt  followed by vagrant up - chances are you still have issues   2   ssh into your guest and setup a soft link to the correct version of Guest Additions  here  5 0 14      vagrant ssh    sudo ln -s  opt VBoxGuestAdditions-5 0 14 lib VBoxGuestAdditions  usr lib VBoxGuestAdditions   exit    vagrant reload   You should be all good  By default  the mounted drive on guest is at  vagrant  Final comment   IF you still have problems related to mounting NFS drives  then here is a workaround that worked for me  I had a vagrantfile with config something like   Simply remove the mount type information  and slim down the mount options settings so they work universally  Vagrant will now automatically choose the best synced folder option for your environment

User · Answer

by now the mounting works on some machines  ubuntu  and some doesn t  centos 7  but installing the plugin solves it  vagrant plugin install vagrant-vbguest   without having to do anything else on top of that  just  vagrant reload

User · Answer

vagrant plugin install vagrant-vbguest vagrant destroy  clean rhel yum repos vagrant up  And on the config file  config vbguest auto update   false  important so that any changes to the base image don t affect on reload

User · Answer

I found this issue addressed here vagrant issues  Two ways to do it    Run this on guest  i e  after you ssh into vbox via vagrant ssh    sudo ln -s  opt VBoxGuestAdditions-4 3 10 lib VBoxGuestAdditions  usr lib VBoxGuestAdditions   Then run vagrant reload to correctly mount the folders   As  klang pointed out  update the VBoxGuestAdditions iso file on your mac   wget https   www virtualbox org download testcase VBoxGuestAdditions 4 3 11-93070 iso   sudo cp VBoxGuestAdditions 4 3 11-93070 iso  Applications VirtualBox app Contents MacOS VBoxGuestAdditions iso    UPDATE  16may2014   Since the iso is no longer available  you can use the 4 3 12 one  http   dlc sun com edgesuite net virtualbox 4 3 12 VBoxGuestAdditions 4 3 12 iso   note   the binary vbox4 3 12 for os X is not available at this time

User · Answer

from my comment above   Following the problem to it s roots    specifically the part in the comments saying this   wget https   www virtualbox org download testcase VBoxGuestAdditions 4 3 11-93070 iso    sudo cp VBoxGuestAdditions 4 3 11-93070 iso  Applications VirtualBox app Contents MacOS VBoxGuestAdditions iso   After doing that  I have business as usual with all my virtual machines  and their current Vagrantfiles  of course   When you have to do something in a freshly created virtual machine  to make it work  something is wrong

[ubuntu] Vagrant error : Failed to mount folders in Linux guest

Examples related to ubuntu

Examples related to virtualbox

Examples related to vagrant

Examples related to nfs