vboxsf is not available

[joshuacox]

vagrant up     
Bringing machine 'master0' up with 'virtualbox' provider...
Bringing machine 'master1' up with 'virtualbox' provider...
Bringing machine 'master2' up with 'virtualbox' provider...
Bringing machine 'slave0' up with 'virtualbox' provider...
Bringing machine 'slave1' up with 'virtualbox' provider...
Bringing machine 'slave2' up with 'virtualbox' provider...
==> master0: Checking if box 'generic/alpine312' version '3.3.4' is up to date...
==> master0: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> master0: flag to force provisioning. Provisioners marked to run always will still run.
==> master1: Checking if box 'generic/alpine312' version '3.3.4' is up to date...
==> master1: Clearing any previously set forwarded ports...
==> master1: Fixed port collision for 22 => 2222. Now on port 2200.
==> master1: Clearing any previously set network interfaces...
==> master1: Preparing network interfaces based on configuration...
    master1: Adapter 1: nat
    master1: Adapter 2: bridged
    master1: Adapter 3: hostonly
==> master1: Forwarding ports...
    master1: 22 (guest) => 2200 (host) (adapter 1)
==> master1: Running 'pre-boot' VM customizations...
==> master1: Booting VM...
==> master1: Waiting for machine to boot. This may take a few minutes...
    master1: SSH address: 127.0.0.1:2200
    master1: SSH username: vagrant
    master1: SSH auth method: private key
==> master1: Machine booted and ready!
==> master1: Checking for guest additions in VM...
==> master1: Mounting shared folders...
    master1: /vagrant_data => /home/thoth/jh/vagrant-consul-nomad/data/common
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,_netdev vagrant_data /vagrant_data

The error output from the command was:

mount: mounting vagrant_data on /vagrant_data failed: Invalid argument

vagrant up  10.61s user 5.43s system 37% cpu 43.146 total

[joshuacox]

in the VM logs:

00:00:00.155351 Per-VM extradata API settings:
00:00:00.155375   VBoxInternal2/SharedFoldersEnableSymlinksCreate/etc_hashicorp.d="1"
00:00:00.155524   VBoxInternal2/SharedFoldersEnableSymlinksCreate/vagrant_data="1"

00:00:00.373895 SharedFolders host service: Adding host mapping
00:00:00.373902     Host path '/home/thoth/jh/vagrant-consul-nomad/data/common', map name 'vagrant_data', writable, automount=false, automntpnt=, create_symlinks=true, missing=false

But then further down I see:

00:06:04.644479 VMMDev: Guest Log: 16:48:45.060884 automount Error: vbsvcAutomounterMountIt: Failed to mount 'vagrant_data' on '/vagrant_data' because it is probably mounted elsewhere arleady!

And yet if I vagrant ssh master0 and investigate:

master0:~# df -h
Filesystem                Size      Used Available Use% Mounted on
devtmpfs                 10.0M         0     10.0M   0% /dev
shm                     494.9M         0    494.9M   0% /dev/shm
/dev/sda2               125.4G      1.3G    117.7G   1% /
tmpfs                    99.0M    252.0K     98.7M   0% /run
/dev/sda1                92.8M     15.3M     70.5M  18% /boot
cgroup_root              10.0M         0     10.0M   0% /sys/fs/cgroup
/dev/sda2               125.4G      1.3G    117.7G   1% /var/lib/docker
master0:~# fdisk -l
Disk /dev/sda: 128 GB, 137438953472 bytes, 268435456 sectors
16709 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sda1 *  0,32,33     12,223,19         2048     206847     204800  100M 83 Linux
/dev/sda2    12,223,20   325,85,16       206848  268435455  268228608  127G 83 Linux