vagrant-nfs_guest - 'reverse' NFS support, where the guest provides the nfs daemon and the host is the client.vagrant-gatling-rsync - An rsync watcher for Vagrant 1.5.1+ that uses fewer host resources.vagrant-saltdeps - Pull in all your salt formula dependencies and merge all your test grain and pillar data!.vagrant-reload - 'Reload a VM as a provisioning step.'.

vagrant-kvm (This project is dead, please use vagrant-libvirt instead.).vagrant-cloudsigma (Requires CloudSigma account).vagrant-guests-clearlinux - Vagrant plugin for Clear Linux.vagrant-vyos - VyOS guest support for Vagrant.vagrant-alpine - Vagrant plugin for Alpine Linux Guest.

vagrant-atomic - Adds a Vagrant guest type for Atomic Host.

vagrant-aws-dns - A Vagrant plugin that allows you to set up route53 records for instances created using vagrant-aws provider.

Only the registrar OVH is supported for the moment.

vagrant-dns-updater - A Vagrant plugin that allows you to automatically configure a subdomain with the IP of your vagrant instance using your registrar API.

vagrant-flow - A seamless development to production workflow with Ansible - Published ansible inventory files for multiple hosts, does local domain resolution too.

vagrant-hosts-provisioner - A Vagrant provisioner for managing the /etc/hosts file of the host and guest machines.

landrush works for Guest and Host (using dnsmasq).

Local Domain Resolution /etc/resolver approach

vagrant-r10k /vagrant-r10k/ - Deploys puppet modules using r10k from a Puppetfile.

vagrant-puppet-install /vagrant-puppet-install/.

vagrant-librarian-puppet /vagrant-librarian-puppet/.

vagrant-templated /vagrant-templated/ Init with custom Vagrantfile and Berksfile.

vagrant-librarian-chef-nochef /vagrant-librarian-chef-nochef/.

vagrant-librarian-chef /vagrant-librarian-chef/.

If there is a plugin you wish to add to this list, please open an issue on this repo and a maintainer will gladly add it to the list. Plugins listed on this page are not 'official' or supported in any way. The following list has both names in this order: rubygem name /internal name/ With Vagrant 1.4.2 and later you just need to know the rubygem name of the plugin that will work either for $ vagrant plugin install and for Vagrant.has_plugin?().

internal name (used in Vagrantfile, via Vagrant.has_plugin?('Internal_Plugin_Name') ).

rubygem name (used for installing plugin, via $ vagrant plugin install rubygem-plugin-name).

Disclaimersīefore Vagrant 1.4.2 there are two distinct names for each one of the plugins that you need to know: To browse available plugins, run gem list -remote vagrant.

Vagrant list boxes