Hi Jeff, you might be running into this: https <https://github.com/mitchellh/vagrant/issues/5199>:// <https://github.com/mitchellh/vagrant/issues/5199>github.com <https://github.com/mitchellh/vagrant/issues/5199>/mitchellh/vagrant/ <https://github.com/mitchellh/vagrant/issues/5199>issues <https://github.com/mitchellh/vagrant/issues/5199>/5199 <https://github.com/mitchellh/vagrant/issues/5199>
Workaround: `rm .vagrant/machines/default/virtualbox/synced_folders` before `vagrant reload` HTH, Torben Have a Vagrantfile with a chef-solo provisioner and a few cookbooks. 'vagrant up' and 'vagrant provision' work fine. However, after 'vagrant reload' the cookbooks appear to have been deleted from the guest. On a Centos guest, /tmp/vagrant-chef/.../cookbooks directory on the guest is empty. On an Ubuntu guest, /tmp/vagrant-chef is empty. In either case provisioning fails. Have never seen this behavior before. Running Vagrant 1.72/VirtualBox 4.3/OSX Yosemite. -- 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]. For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout.
