Paul, `VAGRANT_HOME` moves the "~/.vagrant.d" directory. This contains, primarily, plugins and boxes. When you change `VAGRANT_HOME`, Vagrant does not migrate the existing state for you, so you'll have to do that on your own (rename your existing folder).
As for VMs, VirtualBox puts them in its own VirtualBox configuration directory, and VMware puts it ".vagrant/machines". With VMware, however, you can specify `VAGRANT_VMWARE_CLONE_DIRECTORY`, documented here: http://docs.vagrantup.com/v2/vmware/configuration.html i hope that helps! On Tue, Jan 21, 2014 at 4:51 AM, Paul C <[email protected]> wrote: > Id like to keep my large vm disks separate from my Vagrantfile directory > > The docs suggest that all global state is kept in ~/vagrant.d, with vms > being in ~/vagrant.d/boxes > But on my macbook global state seems to be in ~/.vagrant, and the vm disks > are in a .vagrant/machines subdirectory off my project dir > > When I set VAGRANT_HOME to ~/vagrant_boxes, vagrant cannot find the vmware > plugin > > Am I dong something wrong, or does this variable only apply to Virtualbox > machines? > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
