Why You Need This
Virtualization allows you to run other operating systems without rebooting, test software in an isolated environment, or set up a home lab. VMware Workstation Pro on Ubuntu offers a stable graphical manager, advanced networking support, and deep integration with the host system. After completing this guide, you will have a fully configured environment for creating, cloning, and managing virtual machines.
Requirements and Preparation
Before you begin, ensure your computer meets the basic requirements:
sudoprivileges on Ubuntu 22.04 or 24.04 LTS- Hardware virtualization enabled in BIOS/UEFI (Intel VT-x or AMD-V)
- Approximately 2 GB of free disk space for installation files
- A stable internet connection for downloading dependencies and future updates
Step 1: Prepare the Environment and Dependencies
Open a terminal (Ctrl+Alt+T) and update the package indexes. Install the compilation tools, headers for your current kernel, and the dkms utility, which automatically rebuilds modules when the kernel is updated:
sudo apt update
sudo apt install build-essential linux-headers-$(uname -r) dkms -y
💡 Tip: The
$(uname -r)construct automatically inserts the version of the running kernel. This ensures the system downloads exactly the headers needed to build the VMware drivers.
Step 2: Download the Installer
Go to the official Broadcom support portal. Log in or create an account, find the VMware Workstation Pro section, and download the latest available version in .bundle format. The file is usually named VMware-Workstation-Full-*.x86_64.bundle. It will be saved in the ~/Downloads directory.
Check if the file is present:
cd ~/Downloads
ls -lh VMware*.bundle
Step 3: Run the Installation
Make the downloaded file executable and launch the graphical installation wizard:
chmod +x VMware-Workstation-Full-*.x86_64.bundle
sudo ./VMware-Workstation-Full-*.x86_64.bundle
Follow the on-screen instructions. When the license selection window appears, check the option for personal, non-commercial use (Personal Use). The installer will ask for your user password to configure polkit policies—enter it to complete this stage.
Step 4: Compile and Configure Kernel Modules
After unpacking the files, the system will automatically offer to build and load the vmmon and vmnet modules. If Secure Boot is enabled on your computer, unsigned modules will be blocked by the kernel.
For a quick check and automatic compilation, run:
sudo vmware-modconfig --console --install-all
If the process completes successfully, the terminal will display the line All modules built and loaded. With Secure Boot active, you will need to generate a MOK key via mokutil and register it upon reboot. If you do not store critical data on the device, disabling Secure Boot in your UEFI settings will significantly speed up the process.
Verify the Result
Open the Ubuntu application menu and find VMware Workstation Pro. On first launch, the program will request your sudo password to access virtualization devices. Enter it and navigate to File → New Virtual Machine. If the creation wizard opens and the guest OS list displays correctly, the installation was successful.
You can verify that the background services are running with the command:
systemctl status vmware.service
A status of active (exited) or running means the system is ready to accept tasks for creating virtual machines.
Potential Issues
Modules fail to compile after an Ubuntu update
Linux kernel developers periodically change internal APIs, breaking compatibility with external modules. Reinstall the kernel headers and force a rebuild:
sudo apt install --reinstall linux-headers-$(uname -r)
sudo vmware-modconfig --console --install-all
Error accessing /dev/vmmon or /dev/vmnet
This occurs if the virtualization service is blocked by AppArmor or is running under a different user. Restart all related services:
sudo systemctl restart vmware
sudo systemctl restart vmware-workstation-server
Conflict with KVM/QEMU
The KVM hypervisor captures CPU extensions, preventing VMware from launching a guest kernel. Before starting VMware, temporarily unload the KVM modules:
sudo modprobe -r kvm_intel # For Intel processors
sudo modprobe -r kvm_amd # For AMD processors
To disable the conflict permanently, add blacklist kvm to the file /etc/modprobe.d/blacklist.conf, save the changes, and update the initramfs with the command sudo update-initramfs -u.