Existing VM
Check host version and guest version:
vagrant vbguest --status
or for a specific virtual machine:
VBoxManage guestproperty get <UUID> /VirtualBox/GuestAdd/Version
where <UUID> can be found through VBoxManage list vms .
Then try updating your guest add-ons:
VBoxManage guestcontrol <uuid/vmname> updatega|updateguestadditions|updateadditions
or by installing it again in VM:
vagrant vbguest --do install
Alternatively, install the version recorded in the VBox using:
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage guestproperty set "new_version" /VirtualBox/GuestAdd/Version
Note: change new_version to right
To remove the guets add-on in VM ( vagrant ssh ), follow these steps:
/opt/VirtualBoxGuestAdditions/uninstall.sh rm -rf /tmp/Virtualbox; sudo reboot;
To install it again:
VAGRANT_LOG=info vagrant vbguest --do install
Finally, repeat the check: vagrant vbguest --status .
Source: Problems uninstalling and updating add-ons using Virtualbox 4.3 # 95 on GitHub
New virtual machines
If the above warning does not help, and this mismatch occurs for all new virtual machines, you need to either update VirtualBox or download the ISO VBoxGuestAdditions file from the VirtualBox website (with the correct version, so they can match) and replace it manually.
On OS X, this is in /Applications/VirtualBox.app/Contents/MacOS , so the command will be:
sudo wget -O /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso http://download.virtualbox.org/virtualbox/5.0.14/VBoxGuestAdditions_5.0.14.iso
where the version of VBoxGuestAdditions should match the installed VirtualBox binaries.
Consider also the Vagrant update, if it was installed via Homebrew, try:
brew cask update brew install Caskroom/cask/vagrant
New virtual machines (with existing Vagrantfile )
If this is the beginning for new virtual machines with an existing Vagrantfile that worked earlier, the problem may be loading metadata for your field (for example, the window was removed from your provider, for example Atlas ), and this may lead to the default settings being rejected, therefore make sure your config.vm.box in your Vagrantfile points to a valid VM box or you have temporary network problems.
For more information and troubleshooting, check out: Microsoft's VMware VirtualBox User Guide.