{"issue":{"created_at":"2011-05-06T16:38:52Z","state":"closed","updated_at":"2011-12-12T15:29:36Z","comments":6,"user":{"gravatar_id":"a283176212c7388353deb0fdbc123e76","id":82220,"url":"https://api.github.com/users/auxbuss","avatar_url":"https://secure.gravatar.com/avatar/a283176212c7388353deb0fdbc123e76?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"auxbuss"},"body":"Hi,\r\n\r\nThe vm appears to mount v-root okay:\r\n<pre>\r\n$ vagrant reload\r\n[default] Attempting graceful shutdown of linux...\r\n[default] Running any VM customizations...\r\n[default] Clearing any previously set forwarded ports...\r\n[default] Forwarding ports...\r\n[default] -- ssh: 22 => 2222 (adapter 1)\r\n[default] Cleaning previously set shared folders...\r\n[default] Creating shared folders metadata...\r\n[default] Booting VM...\r\n[default] Waiting for VM to boot. This can take a few minutes.\r\n[default] VM booted and ready for use!\r\n[default] Mounting shared folders...\r\n[default] -- v-root: /vagrant\r\n$ \r\n</pre>\r\n\r\nBut `/vagrant` is empty on the guest. The shared folder contents were available prior to upgrading the OS, which was created via:\r\n<pre>\r\n$ vagrant box add lucid32 http://files.vagrantup.com/lucid32.box\r\n$ vagrant init lucid32\r\n$ vagrant up\r\n</pre>\r\n\r\nI'm new to vagrant, so not clear how to start debugging.\r\n","assignee":null,"id":859242,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":355,"labels":[],"title":"shared folder not mounting","html_url":"https://github.com/mitchellh/vagrant/issues/355","closed_at":"2011-05-06T17:24:14Z","url":"https://api.github.com/repos/mitchellh/vagrant/issues/355","milestone":null},"action":"created","comment":{"created_at":"2011-12-12T15:29:36Z","updated_at":"2011-12-12T15:29:36Z","user":{"gravatar_id":"0d5dee51068dfd31768b5f3c64bc2d4f","id":180951,"url":"https://api.github.com/users/stallons","avatar_url":"https://secure.gravatar.com/avatar/0d5dee51068dfd31768b5f3c64bc2d4f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"stallons"},"body":"It took me a while to find this issue. \r\n\r\n`vagrant provision` gets screwed up if you update the kernel on the guest machine, and forget to run `/etc/init.d/vboxadd setup` then `vagrant reload`.\r\n\r\nE.g: Chef-solo will fail with error \"Chef::Exceptions::CookbookNotFound: Cookbook * not found\", since the chef.provisioning_path (/tmp/vagrant-chef-1/chef-solo-1) will be an empty directory.","id":3107381,"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/3107381"}}