Table of Contents
Introduction
In this tutorial, How to fix the error Vagrant No VirtualBox Guest Additions installation is found. I use a laptop and run the command vagrant up for the NFS server then the error “umount: /mnt: not mounted“
ERROR umount: /mnt: not mounted
E:\Vagrant_VMS\NFS_server>vagrant up
Error: Nothing to do
Unmounting Virtualbox Guest Additions ISO from: /mnt
umount: /mnt: not mounted
==> servernfs: Checking for guest additions in VM...
servernfs: No guest additions were detected on the base box for this VM! Guest
servernfs: additions are required for forwarded ports, shared folders, host only
servernfs: networking, and more. If SSH fails on this machine, please install
servernfs: the guest additions and repackage the box to continue.
servernfs:
servernfs: This is not an error message; everything may continue to work properly,
servernfs: in which case you may ignore this message.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
umount /mnt
Stdout from the command:
Stderr from the command:
umount: /mnt: not mounted
Vagrant No VirtualBox Guest Additions installation found fixed
I have uninstalled vagrant-vbguest and installed vagrant-vbguest.
vagrant plugin uninstall vagrant-vbguest
vagrant plugin install vagrant-vbguest --plugin-version 0.21The output uninstall and install vagrant-vbguest as below
E:\Vagrant_VMS\NFS_server>vagrant plugin uninstall vagrant-vbguest
Uninstalling the 'vagrant-vbguest' plugin...
Successfully uninstalled micromachine-3.0.0
Successfully uninstalled vagrant-vbguest-0.27.0
E:\Vagrant_VMS\NFS_server>vagrant plugin install vagrant-vbguest --plugin-version 0.21
Installing the 'vagrant-vbguest --version '0.21'' plugin. This can take a few minutes...
Fetching micromachine-3.0.0.gem
Fetching vagrant-vbguest-0.21.0.gem
Installed the plugin 'vagrant-vbguest (0.21.0)'!As a result, I have to fix it!
E:\Vagrant_VMS\NFS_server>vagrant reload
==> servernfs: Attempting graceful shutdown of VM...
==> servernfs: Checking if box 'centos/7' version '2004.01' is up to date...
==> servernfs: Clearing any previously set forwarded ports...
==> servernfs: Clearing any previously set network interfaces...
==> servernfs: Preparing network interfaces based on configuration...
servernfs: Adapter 1: nat
servernfs: Adapter 2: hostonly
==> servernfs: Forwarding ports...
servernfs: 22 (guest) => 2222 (host) (adapter 1)
==> servernfs: Booting VM...
==> servernfs: Waiting for machine to boot. This may take a few minutes...
servernfs: SSH address: 127.0.0.1:2222
servernfs: SSH username: vagrant
servernfs: SSH auth method: private key
servernfs: Warning: Connection aborted. Retrying...
==> servernfs: Machine booted and ready!
[servernfs] GuestAdditions 6.1.14 running --- OK.
==> servernfs: Checking for guest additions in VM...
==> servernfs: Configuring and enabling network interfaces...
==> servernfs: Rsyncing folder: /cygdrive/e/MyData/Vagrant_VMS/NFS_server/ => /vagrant
==> servernfs: Rsyncing folder: /cygdrive/e/MyData/Vagrant_VMS/NFS_server/NFS_Volumn/ => /home/vagrant/nfs_test
==> servernfs: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> servernfs: flag to force provisioning. Provisioners marked to run always will still run.Youtube Vagrant No VirtualBox Guest Additions installation found [Fixed]
Conclusion
You have fixed Vagrant No VirtualBox. I hope will this your helpful. Thank you for reading the DevopsRoles page!
Thank you Huu. Uninstalling vagrant-vbguest-0.28.0 and installing vagrant-vbguest-0.21.0, also solved my /mnt problem.
Vagrant 2.2.14
centos/7 (virtualbox, 2004.01)
Version 6.1.16 r140961 (Qt5.6.3)
Thanks a lot Huu! Your solution to uninstall vagrant-vbguest-0.28.0 and installing plugin version 0.21 worked for me too.
Or you just can change:
config.vm.box = “centos/7” to –> config.vm.box = “generic/centos7” and uninstall the plugin using this command “vagrant plugin uninstall vagrant-vbguest” after that run command “vagrant up”
Instead of pinning an old version of vbguest .. you could add this to your Vagrantfile
node.vbguest.installer_options = { allow_kernel_upgrade: true }
Thanks HuuPV, it solved my problem that was happening with the vagrant-vbguest-0.30.0 version. I uninstalled this version and installed the vagrant-vbguest-0.21.0 version…..and it worked.
Just had the same issue with the CentOS/7 box and switching to vagrant-vbguest-0.21.0 version worked for me too.
Easy and very helpfull. Thanks