Issue seems to be a broken symlink within box geerlingguy/centos7 v 1.2.1. If you create a VM using geerlingguy/centos7 v1.2.1 you will not be able to mount /vagrant to the local filesystem where vagrant up
was run.
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant box list
centos/7 (virtualbox, 1703.01)
geerlingguy/centos7 (virtualbox, 1.2.1)
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'geerlingguy/centos7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'geerlingguy/centos7' is up to date...
==> default: Setting the name of the VM: vagrant_default_1497965107575_73585
==> 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 => /Users/dcastellani/Documents/git/dcastellani_infra/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 /vagrant
The error output from the command was:
mount: wrong fs type, bad option, bad superblock on vagrant,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
(1) dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant status
Current machine states:
default running (virtualbox)
The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant ssh
[vagrant@localhost ~]$ ll -ah /vagrant/
total 0
drwxr-xr-x. 2 root root 6 Jun 20 13:25 .
dr-xr-xr-x. 18 root root 239 Jun 20 13:25 ..
[vagrant@localhost ~]$ ll -ah /sbin/mount*
-rwxr-xr-x. 1 root root 41K Nov 5 2016 /sbin/mount.cifs
-rwsr-xr-x. 1 root root 111K Mar 3 07:09 /sbin/mount.nfs
lrwxrwxrwx. 1 root root 9 Apr 21 23:15 /sbin/mount.nfs4 -> mount.nfs
-rwxr-xr-x. 1 root root 35K Mar 3 07:09 /sbin/mountstats
lrwxrwxrwx. 1 root root 49 Apr 21 23:17 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/other/mount.vboxsf
[vagrant@localhost ~]$ ll -ah /opt/VBoxGuestAdditions-5.1.20/other/
ls: cannot access /opt/VBoxGuestAdditions-5.1.20/other/: No such file or directory
[vagrant@localhost ~]$ ll -ah /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.*
-rwxr-xr-x. 1 root root 19K Apr 18 08:51 /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf
[vagrant@localhost ~]$ sudo ln -sf /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf
[vagrant@localhost ~]$ ll -ah /sbin/mount*
-rwxr-xr-x. 1 root root 41K Nov 5 2016 /sbin/mount.cifs
-rwsr-xr-x. 1 root root 111K Mar 3 07:09 /sbin/mount.nfs
lrwxrwxrwx. 1 root root 9 Apr 21 23:15 /sbin/mount.nfs4 -> mount.nfs
-rwxr-xr-x. 1 root root 35K Mar 3 07:09 /sbin/mountstats
lrwxrwxrwx. 1 root root 66 Jun 20 13:30 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf
[vagrant@localhost ~]$ exit
logout
Connection to 127.0.0.1 closed.
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'geerlingguy/centos7' is up to date...
==> 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: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => /Users/dcastellani/Documents/git/dcastellani_infra/vagrant
dcastellani@dcastellani-mbp ~/D/g/d/vagrant> vagrant ssh
Last login: Tue Jun 20 13:26:34 2017 from 10.0.2.2
[vagrant@localhost ~]$ ll /vagrant/
total 4
-rw-r--r--. 1 vagrant vagrant 3023 Jun 19 21:00 Vagrantfile
Looks like fix is to upgrade VBoxGuestAdditions within the box to 5.1.22 which you have already done it seems in geerlingguy/centos7 v 1.2.2 but have not released the version.