You can also use 'lsmod | grep vm' and if it doesn't return the vmhgfs module with a count higher than 0 (or it doesn't show up) then Alvaro is correct and it hasn't loaded the driver/module correctly. This is frequently an issue if you are using newer than 3.13.0-37 of the Linux kernel, they made some minor changes there that broke the VMware Tools installs horribly.
On Wednesday, July 29, 2015 at 6:41:35 PM UTC-5, Alvaro Miranda Aguilera wrote: > > On Thu, Jul 30, 2015 at 5:50 AM, Patrick Bass <[email protected] > <javascript:>> wrote: > > 14.04.2 LTS > > Hello, > > Thanks for the info > > Well, the /vagrant is not mounted, this can be by several reasons. One > of them is in some new kenels are some issues, with vmware tools, and > a long etc. > > So, can you test this box: > > mkdir precise64 > cd precise64 > vagrant init -m hashicorp/precise64 > vagrant up > > Can you share the outlog log in a gist (gist.github.com) and repeat > the same commands? > > If the commands works as I expect, my recommendation will be test > other ubuntu box, or create your very own with packer (packer.io) > > Thanks > Alvaro. > -- 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/efc0459a-5f4c-4d7e-bc2f-9abe94ce1140%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
