Vagrant + VMware Workstation: The “Killer” Combo for DevOps Lab Environments – ITFROMZERO

Table of Contents

Why I Switched from VirtualBox to VMware

If you are a DevOps or Backend engineer, you are likely familiar with Vagrant. It is an excellent tool for “coding” your virtual machine setups. Most tutorials online use VirtualBox because it is free. However, after managing a cluster of 8 ESXi hosts at my company for a long time, I realized that VMware Workstation is on a completely different level. It excels in I/O speeds and provides incredibly stable resource management.

Using VMware feels much “smoother.” A VM boots in just 15-20 seconds instead of a full minute like on VirtualBox. Common issues when mounting shared folders have also virtually disappeared. Previously, the VMware plugin for Vagrant cost $79, but HashiCorp has now made it free. This is a great opportunity to upgrade your personal Lab infrastructure.

Installing the Necessary Components

First, you need VMware Workstation Pro or Player installed on your machine. Next, we need to install two additional components so Vagrant can control VMware.

1. Install Vagrant VMware Utility

This is a background service that allows Vagrant to interact with VMware APIs. Simply go to the HashiCorp homepage, download the appropriate installer for your OS (Windows/Linux), and install it like any other app.

2. Install the Vagrant VMware Desktop Plugin

Open your terminal and run the plugin installation command. This process is quite fast:

vagrant plugin install vagrant-vmware-desktop

Once installed, run vagrant plugin list to ensure everything is ready.

Standard Vagrantfile Configuration for VMware

When using VMware, the provider declaration in the Vagrantfile is slightly different. I recommend using boxes from Bento. They are perfectly built for both VMware and VirtualBox.

Below is a sample Vagrantfile I typically use to set up an Ubuntu 22.04 Lab:

Vagrant.configure("2") do |config|
  config.vm.box = "bento/ubuntu-22.04"

  config.vm.provider "vmware_desktop" do |v|
    v.gui = false              # Run in background, don't show VMware window
    v.cpus = 2                 # Allocate 2 CPU cores
    v.memory = 4096            # Allocate 4GB RAM
    v.linked_clone = true      # Extremely important feature
  end

  config.vm.network "private_network", ip: "192.168.56.10"
  config.vm.synced_folder ".", "/var/www/html", type: "nfs"
end

Pro tip: The v.linked_clone = true option is a lifesaver for your hard drive. Instead of copying a full 10GB-20GB image, VMware creates a linked clone. This allows the VM to be ready in seconds and consumes only a few hundred MBs initially.

Launch and Experience

To start it up, use the command with the provider flag:

vagrant up --provider vmware_desktop

If you don’t want to type --provider every time, set the environment variable VAGRANT_DEFAULT_PROVIDER=vmware_desktop on your machine. Once the machine is up, SSH into it as usual using the vagrant ssh command.

Open VMware Workstation, and you will see a new VM folder appear. Everything from RAM settings to Snapshots is perfectly synced between Vagrant and the VMware interface.

Troubleshooting Tips

Throughout my experience, I have gathered several important technical details:

IP Conflicts: If the VM doesn’t get an IP, check the Virtual Network Editor. Ensure VMnet1 and VMnet8 do not overlap with your company’s VPN IP range.
CPU Acceleration: If the VM feels sluggish, disable “Side channel mitigations” in the VMware Processors settings. This can boost performance by about 10-15%.
Check Logs: If vagrant up hangs, go to the ~/.vagrant.d/ directory to find the plugin logs. Most errors stem from the VMware Utility not starting correctly.

In practice, when testing a 3-node Kubernetes cluster, the network latency between VMs on VMware was significantly lower than on VirtualBox. This makes microservices testing much more accurate. Give this combo a try—you definitely won’t want to go back to VirtualBox.