Vagrant up fails on mount of 'vboxsf'

During the last weeks I have completed following MongoDB courses without any problems:
M001: MongoDB Basics¨
M103: Basic Cluster Administration
M201: MongoDB Performance
M040: New Features and Tools in MongoDB 4.0

Had no problems at all running vagrant for these courses, but with M310 vagrant fails to initiate. This is the error that I get:

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 home_vagrant_shared /home/vagrant/shared
The error output from the command was:
mount: unknown filesystem type ‘vboxsf’

Tried this in order to make it work:

  1. Upgraded vagrant from 2.2.3 -> 2.2.4
  2. vagrant plugin install vagrant-vbguest
  3. Trying to start vagrant:

C:\Work\MongoDB\Courses\M310-Security>vagrant up
Bringing machine ‘database’ up with ‘virtualbox’ provider…
Bringing machine ‘infrastructure’ up with ‘virtualbox’ provider…
==> database: Checking if box ‘ubuntu/trusty64’ version ‘20190116.1.0’ is up to date…
==> database: Machine already provisioned. Run vagrant provision or use the --provision
==> database: flag to force provisioning. Provisioners marked to run always will still run.
==> infrastructure: Checking if box ‘centos/7’ version ‘1902.01’ is up to date…
==> infrastructure: Machine already provisioned. Run vagrant provision or use the --provision
==> infrastructure: flag to force provisioning. Provisioners marked to run always will still run.

Still no luck.

What is not working
At the end of this message are you able to check status?
Did not face any issue during my install

==> infrastructure: Configuring and enabling network interfaces…
==> infrastructure: Rsyncing folder: /cygdrive/c/Users/ramrt/M310/m310-vagrant-env/ => /vagrant
==> infrastructure: Mounting shared folders…
infrastructure: /home/vagrant/shared => C:/Users/ramrt/M310/m310-vagrant-env/shared
==> infrastructure: Machine already provisioned. Run vagrant provision or use the --provision
==> infrastructure: flag to force provisioning. Provisioners marked to run always will still run.

C:\Users\ramrt\M310\m310-vagrant-env>vagrant status
Current machine states:

database running (virtualbox)
infrastructure running (virtualbox)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run vagrant status NAME.

C:\Users\ramrt\M310\m310-vagrant-env>vagrant ssh database
Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-164-generic x86_64)

vagrant@database:~ date Tue Feb 19 14:21:39 UTC 2019 vagrant@database:~

I was still not able to connect with ‘ssh’.

But after another reinstall of vagrant 2.2.4 + MinGW it is working fine.

It seems as there was some kind of version conflict with the vagrant environment and vagrant 2.2.3.
All my previous vagrant environments were working fine, but M310 was failing.

@ Allan_77788

Glad you got it working. You might want to go into the Oracle VirtualBox manager and see what all VMs you have defined. It’s certainly possible that there are some version conflicts or that you’ve got more running than you thought. Good luck.