Vagrant was unable to mount VirtualBox shared folders

gistfile1.txt

11:07 $ vagrant status
Current machine states:

nitro                     poweroff (virtualbox)

The VM is powered off. To restart the VM, simply run `vagrant up`
✔ ~/code/nitro-web [fix/prevent_connect_users_from_seeing_corporate_events_#149559425|⚑ 33]
11:07 $ vagrant up
Bringing machine 'nitro' up with 'virtualbox' provider...
==> nitro: Checking if box 'tbfisher/ubuntu1404puppet4' is up to date...
==> nitro: Clearing any previously set forwarded ports...
==> nitro: Clearing any previously set network interfaces...
==> nitro: Preparing network interfaces based on configuration...
    nitro: Adapter 1: nat
    nitro: Adapter 2: hostonly
==> nitro: Forwarding ports...
    nitro: 22 (guest) => 2222 (host) (adapter 1)
==> nitro: Running 'pre-boot' VM customizations...
==> nitro: Booting VM...
==> nitro: Waiting for machine to boot. This may take a few minutes...
    nitro: SSH address: 127.0.0.1:2222
    nitro: SSH username: vagrant
    nitro: SSH auth method: private key
==> nitro: Machine booted and ready!
==> nitro: Checking for guest additions in VM...
    nitro: The guest additions on this VM do not match the installed version of
    nitro: VirtualBox! In most cases this is fine, but in rare cases it can
    nitro: prevent things such as shared folders from working properly. If you see
    nitro: shared folder errors, please make sure the guest additions within the
    nitro: virtual machine match the version of VirtualBox you have installed on
    nitro: your host and reload your VM.
    nitro:
    nitro: Guest Additions Version: 5.0.0
    nitro: VirtualBox Version: 5.1
==> nitro: Setting hostname...
==> nitro: Configuring and enabling network interfaces...
==> nitro: Mounting shared folders...
    nitro: /opt/talkbox => /Users/greg/code/nitro-talkbox
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 opt_talkbox /opt/talkbox

The error output from the command was:

: No such device