VMware Workstation

What It Does

VMware Workstation creates isolated virtual machines with enterprise-quality virtual hardware emulation. Each VM gets virtual CPUs, RAM, NVMe/SCSI disks, and network adapters. VMware's virtual networking is more robust than VirtualBox -- it includes a built-in virtual switch editor, DHCP configuration, and NAT rules. Linked clones let you spin up multiple VMs from a single base image without duplicating the entire disk.

Workstation supports DirectX 11 and OpenGL 4.3 in guests, handles nested virtualization (running hypervisors inside VMs), and integrates with VMware vSphere for enterprise lab environments.

Why You Need It

VMware is the industry standard in enterprise virtualization. Understanding VMware products (Workstation, ESXi, vSphere, vCenter) is directly relevant to certifications like VCP-DCV, and to any SOC, sysadmin, or infrastructure role. Labs that simulate enterprise environments benefit from VMware's more reliable networking and snapshot trees.

It is the recommended hypervisor for Matrix House infrastructure labs, Forge House enterprise Windows labs, and any lab requiring nested virtualization (e.g., running ESXi inside a VM for vSphere practice). Use VMware when you need performance or enterprise features; use VirtualBox when you need free cross-platform simplicity.

How to Install It

Windows:

1. Go to Broadcom VMware Downloads (requires free Broadcom account)
2. Download VMware Workstation Pro for Windows
3. Run the installer. Select "Install for Personal Use" when prompted for a license -- this is free.
4. Reboot when prompted. VMware installs virtual network adapters (vmnet1, vmnet8).

Linux (Ubuntu/Debian):

1. Download the .bundle installer from the Broadcom downloads page
2. Make it executable and run:

   chmod +x VMware-Workstation-Full-*.bundle
   sudo ./VMware-Workstation-Full-*.bundle

3. If kernel module compilation fails, install headers: sudo apt install linux-headers-$(uname -r)

macOS:

VMware Workstation is not available on macOS. Use VMware Fusion instead (also free for personal use), or use VirtualBox.

Verify installation:

vmrun list

VMware vs VirtualBox

• Performance: VMware generally runs VMs 10-20% faster, especially for disk I/O and graphics. VirtualBox is adequate for most labs.
• Networking: VMware's Virtual Network Editor gives you full control over custom networks, DHCP ranges, and NAT port forwarding. VirtualBox networking works but requires more CLI configuration for advanced setups.
• Snapshots: VMware supports snapshot trees (branch and compare). VirtualBox snapshots are linear.
• Nested virtualization: VMware handles running ESXi/Hyper-V inside a VM. VirtualBox support is experimental.
• Cross-platform: VirtualBox runs on Windows, Linux, macOS. VMware Workstation is Windows/Linux only (Fusion for macOS).
• Cost: Both free for personal use. VirtualBox is open source (GPLv3). VMware is proprietary with free license.

Recommendation: Install both. Use VMware for enterprise and performance-sensitive labs. Use VirtualBox for quick throwaway VMs and when you need macOS host support.

How to Use It

1. Create a new VM. File > New Virtual Machine > Typical. Select the ISO file. VMware auto-detects most OS types and pre-configures optimal settings (Easy Install). For manual control, select "I will install the operating system later."
2. Allocate resources. 2-4 CPU cores, 4-8 GB RAM for Windows/Server, 2-4 GB for Linux. Disk: 60 GB minimum, store as single file for performance (split files only if you need to move the VM to a FAT32 drive).
3. Configure networking. Edit > Virtual Network Editor. Create custom networks (vmnet2, vmnet3, etc.) for isolated lab segments. Assign VMs to the appropriate network in VM Settings > Network Adapter.
4. Install VMware Tools. After the OS is installed, go to VM > Install VMware Tools. This is equivalent to VirtualBox Guest Additions -- enables clipboard sharing, drag-and-drop, auto-resize, and better graphics.
5. Snapshot before experimenting. VM > Snapshot > Take Snapshot. Name it descriptively (e.g., "Post-AD-Install"). You can create snapshot branches to compare different configurations.

vmrun CLI Reference

VMware includes vmrun for scripting VM operations:

# List running VMs
vmrun list

# Start a VM (GUI mode)
vmrun start "/path/to/vm.vmx" gui

# Start headless (no window)
vmrun start "/path/to/vm.vmx" nogui

# Suspend a VM
vmrun suspend "/path/to/vm.vmx"

# Take a snapshot
vmrun snapshot "/path/to/vm.vmx" "Clean-Install"

# Revert to snapshot
vmrun revertToSnapshot "/path/to/vm.vmx" "Clean-Install"

# Run a command inside the guest (requires VMware Tools)
vmrun -gu username -gp password runProgramInGuest "/path/to/vm.vmx" "/bin/hostname"

Common Gotchas

• Broadcom account required. Since the Broadcom acquisition, downloading VMware requires a free Broadcom support account. The registration process is clunky but the software is genuinely free for personal use.
• Hyper-V coexistence. VMware Workstation 15.5+ supports running alongside Hyper-V/WSL2 using Windows Hypervisor Platform (WHP). Performance may be slightly lower in this mode. If you experience issues, use bcdedit /set hypervisorlaunchtype off and reboot.
• Linux kernel module build failures. After a kernel update on Linux hosts, VMware's kernel modules need to be rebuilt. Usually sudo vmware-modconfig --console --install-all fixes this. If not, install the matching linux-headers package.
• VM won't start after host crash. If the host crashes or loses power while a VM is running, VMware may leave a lock file (.lck directory) next to the .vmx file. Delete the .lck directory to unlock the VM.
• Disk space. VMware uses .vmdk disk files that can grow large. Use vmware-vdiskmanager -k disk.vmdk to shrink (compact) a virtual disk after deleting files inside the guest.