hello, Thats because your script is upgrading kernel, and on next boot the vboxsf driver is not loading.
2 options. a. Do not upgrade kernel. b. recompile the vbox drivers after reboot. for b, you can install plugin vbguest and will take care of that. Alvaro. > On 5/04/2016, at 6:27 AM, [email protected] wrote: > > Hi All, > > I dipped my toes into Vagrant and Puppet a few years ago, but never went much > further than a little experimentation. > > I now want to use Vagrant to provision a couple of VM's on my Office server, > but am having the following problem: > > If I > > vagrant up > > initially, the box boots up and is provisioned according to bootstrap.sh and > I can ssh in to the VM and work as expected. > > If I subsequently > > vagrant reload --provision > > then I get the following error: > > Failed to mount folders in Linux guest. This is usually because > > > 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 error output from the last command was: > > > /sbin/mount.vboxsf: mounting failed with the error: No such device > > > The only way I can seem to resolve this, is to delete the VM files manually > in VirtualBox. > > Surely, I should be able to update the provisioning file, and provision > multiple times? > > I've looked around, and found posts with a similar issue, but nothing seems > to relate to my particular problem. > > I"ve attached my Vagrant file, and also bootstrap.sh and I'm happy to attach > more info, if you tell me what you need. > > My environment is as follow: > > OSX: 10.11.4 > vagrant: 1.8.1 > VirtualBox: 5.0.16 r105871 > > Thanks to anyone who can help, and I'll add any additional info if you tell > me what to supply. > > Thanks > > Paul > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html > <https://www.hashicorp.com/community-guidelines.html>. Behavior in violation > of those guidelines may result in your removal from this mailing list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > <https://github.com/mitchellh/vagrant/issues> > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/73439857-0da9-4661-be1c-ef4c673f812f%40googlegroups.com > > <https://groups.google.com/d/msgid/vagrant-up/73439857-0da9-4661-be1c-ef4c673f812f%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > <Vagrantfile><bootstrap.sh> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/10C6800E-AE52-4CB7-81F5-13B4316A66A6%40gmail.com. For more options, visit https://groups.google.com/d/optout.
