I’ve been having real difficulties using the vagrant vmware provider. The issues all stem around permissions issues on the vmware files within /var.
Specifically the files within /var/db/vmware, which contains the dhcp lease information for the virtual machines, is not world-readable when the files are initially created, and it does not seem that the vmware sudo-helper is being used to access them. This means that vagrant can never get the IP to ssh into. Secondly and similarly, the symlinks generated in var/run/vmware that point to my user folder are not world readable. This means that `vmrun` has no knowledge of the vm, and neither does vagrant (vagrant halt will not do anything). The second problems goes away when the vm is brought up with .gui = true in the Vagrantfile, but obviously I don't want to have to run every vm in a gui mode. The first problem is only manually fixed. I've tested this multiple times, on multiple machiens, and multiple clean installs of vagrant and vmware fusion. Does anyone else have these problems or know how to fix it? I’ve documented the issues on the vmware site a month ago, because the problems aren't exclusive to using vagrant. Starting a headless vm at all through vmware fusion seems to have this problem. https://communities.vmware.com/thread/473992. -- 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.
