#Using vagrant with vmware vs virtualbox install
#Using vagrant with vmware vs virtualbox pro
#Using vagrant with vmware vs virtualbox license

In Vagrant with VMware Fusion, you achieve the same with this:Д¬onfig.vm.provider :vmware_workstation do |v| Some of the configuration has changed, for instance, using Vagrant version 1.0.x and VirtualBox, you would set the memory of the VM like this:Д¬onfig.vm.customize I'm sure that the paucity of VMware compatible base boxes will remedied soon.Д¬onfiguring Vagrant-Managed Virtual Machines There are some listed on Vagrantbox.es and at least one compatible template on the veewee repo should you wish to build your own base box. Since the VMware provider is pretty new, there are only a few compatible base boxes. You'll need a base box set up to use the VMware provider rather than VirtualBox.

Now that the VMware provider plugin is installed, setting up the boxes and provisioning is pretty much the same as using VirtualBox, with a few differences:

#Using vagrant with vmware vs virtualbox license

Vagrant plugin license vagrant-vmware-workstation license.lic

#Using vagrant with vmware vs virtualbox install

Vagrant plugin license vagrant-vmware-fusion license.licДЇor Workstation users: vagrant plugin install vagrant-vmware-workstation With that license in hand, install and license the Vagrant plugin.ДЇor Fusion users: vagrant plugin install vagrant-vmware-fusion Once those are installed, you can purchase your VMware provider license on the Vagrant website. You'll also need Vagrant 1.1 or higher, but grab the latest as Mitchell has been hard at work on both Vagrant and the VMware provider. In my testing, the VMware boxes have run perfectly for up to weeks at a time.ДЇirst, you'll need either VMWare Fusion 5.x or higher (Mac OS X) or VMware Workstation 9.x or higher (Windows or Linux). In a couple of weeks of testing I've not seen a single hiccup. The stability of Vagrant VMware boxes is impressive. Bringing those three boxes up from a suspended state was about 35 percent faster. Creating and provisioning a three-box set from base boxes was about 20 percent faster than using the VirtualBox provider.

#Using vagrant with vmware vs virtualbox pro

Some quick and dirty testing using VMware Fusion boxes on a Late 2011 Macbook Pro with 8GB RAM confirms this. Subjectively, Vagrant tasks seem snappier. It's no secret that VMware has spent a lot of time optimizing for performance, and this work shows when running VMware boxes under Vagrant. VMware Boxes Provide Performance and Stability

If you need to provision and/or configure the virtual machine further, Vagrant can use Puppet manifests to get exactly the environment you require. If your needs are pretty standard, you can have a Vagrant box up and running in a few minutes. Now you can use Vagrant to create and control VMware virtual machines using VMware Workstation and VMware Fusion along with VirtualBox.ДЇollowing the 'configuration as code' pattern, Vagrant allows you to specify a 'base box'-a 'box' is just a VM with a few special configuration conventions-and a configuration file to further customize the settings of the virtual machine. That changed this spring when Vagrant creator Mitchell Hashimoto released a VMware provider for Vagrant. Until recently, the only virtualization provider for Vagrant was for VirtualBox. Vagrant addresses this need by making it easy to create and control virtual machines. Developers need a quick, reproducible method for creating environments to run and test their applications.