Vagrant - Error: Failed to mount folders in Linux guest. This is usually beacuse the "vboxsf" file system is not available.

-
I have installed VirtualBox on Mac OSX and was getting this error on the command "vagrant up"

[default] Mounting shared folders...
[default] -- /vagrant
Failed to mount folders in Linux guest. This is usually beacuse
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:
mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` /vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` /vagrant /vagrant


 The fix for this is destroy the VM that was created just now, just us vagrant destroy to destroy this VM. And then give the following command

vagrant plugin install vagrant-vbguest


And now when we create a VM using vagrant up, we get the shared drive created without any issues and we 


Popular posts from this blog

Learning OpenStack - The Easy Way

-
Image
Dear Friends, Our Dream has come true! It takes 9 months for a mother to bring another life. That is the amount of time it has taken me to demystify the otherwise terse and abstract cloud computing concepts. And thanks to Packt Publishing I for helping me impart this knowledge in the most engaging way. The Full video course is out you can get more details about it here . You can get more details about the course here without registering. The Overview video is out for all. It was a tough negotiation with publisher to give out this valuable video for free I hope that it will get you started on your "Infrastructure as Code" journey. Three points I would like to share, which might help you are:- People are watching us! Packt publishing approached me watching the screencasts I had posted on Youtube. (Which until then I was certain that nobody was watching). Good news is Video course royalty is 3 times that of a book! Bad news is because its 3 times the...
Read more

Vagrant on steroids

-
Image
Source This is our life when we are working on automating some really complicated machine building and provisioning procedures. I.e. while developing the playbooks in Ansible, or CookBooks in Chef or manifests in Puppet. It is not easy to fail faster and fix early as the script might have to download all the dependencies again and again. Adding to all the odds, it could be that the dependencies are being downloaded on a low bandwidth. Even though Vagrant makes bringing up VM and their management faster, the provisioning (using Ansible, Chef or Puppet or etc) might take inordinately long times when it involves, and it usually does involve downloading packages on the VMs. And it gets painful when you have to download a full stack of several libraries to test your VM. To help overcome this issue, we can use the following to cache the dependencies and test the configuration scripts or recipes faster, the following should set you up (assuming you have vagrant already installe...
Read more