How to Install VMware Workstation 16 Pro on RHEL 8 or CentOS 8
If you’re hunting for a way to run virtual machines on your enterprise‑grade distro, this guide will walk you through getting VMware Workstation 16 Pro up and running on RHEL 8 or CentOS 8. No fluff, just the bits that work and why they matter.
What You’ll Need Before You Start
- A 64‑bit system with at least a quad‑core CPU and 4 GB RAM (more is better for VMs).
- Root access or sudo privileges—VMware needs to build kernel modules.
- The latest kernel headers, gcc, make, and a working C compiler:
sudo dnf install gcc make kernel-devel kernel-headers
VMware’s installer compiles its own modules against the exact kernel you’re running. Without matching headers or a compiler, you’ll get cryptic “module build failed” errors that are harder to diagnose.
Grab the VMware Workstation 16 Pro Installer
1. Head over to the VMware website and sign in (or create an account).
2. Download the VMware‑Workstation‑16.x.x‑x86_64.bundle file for Linux.
3. Verify its SHA‑256 checksum against the one posted on the download page:
sha256sum VMware-Workstation-16*.bundle
4. Make it executable: chmod +x VMware-Workstation-16*.bundle.
Why verify? I’ve seen this happen after a bad driver update that corrupted the installer, and the checksum fails fast before you waste hours trying to patch a broken binary.
Run the Installer in “Silent” Mode
Running it with --eulas-agreed bypasses the wizard and lets the script do its thing automatically:
sudo ./VMware-Workstation-16*.bundle --eula-text=1 --product-key=YOURKEYHERE
Replace YOURKEYHERE with your license key (or leave it blank for the free trial).
If you forget to agree to the EULA, the installer will abort right away.
Why silent mode? The GUI requires an X server, and many RHEL/CentOS servers run headless. Silent mode is also less likely to trip over missing zenity or gtk.
Fix Common Build Failures
When you see something like:
ERROR: Failed to compile module 'vmmon'
or the installer stops with “Could not install kernel modules,” try these fixes:
| Symptom | Quick Fix |
|---|---|
| Missing GCC or Make | sudo dnf groupinstall "Development Tools" |
| Kernel headers out of sync | Reboot into the same kernel you installed the headers for, or reinstall kernel-devel |
| SELinux blocking installation | Temporarily set to permissive: setenforce 0, then re‑run installer |
The module compilation step is the linchpin. A single mismatch will halt everything else.
Enable VMware Services
After a successful install, you need to start two services:
sudo systemctl enable --now vmware sudo systemctl enable --now vmware-tools-daemon
These keep the vmmon and vmnetd daemons running in the background. If you forget this step, launching VMware will spin up a fresh copy of those binaries every time.
Launching Your First Virtual Machine
1. Open a terminal or SSH session that has access to X forwarding if you want the GUI (ssh -X user@host).
2. Type vmware. The first launch may trigger an additional module build; watch for any error messages.
3. Create a new VM as usual. If you encounter “VMware Workstation needs to install kernel modules,” run:
sudo vmware-modconfig --console --install-all
Why this extra step? RHEL/CentOS’s dynamic kernel updates sometimes leave stale modules. Re‑running vmware-modconfig pulls the latest ones into place.
Troubleshooting Tips
- VMware won’t start after a kernel upgrade:
sudo vmware-modconfig --console --install-all
Then reboot.
- Network issues inside VMs: Ensure vmnet8 is enabled in /etc/vmware/networking. If not, run sudo /usr/bin/vmware-networks start.
- Permission errors on /dev/vmmon:
sudo chmod 666 /dev/vmmon
This is safe because only root installs the device node.
When All Else Fails
If you hit a wall, VMware’s own forum and Stack Overflow are surprisingly helpful. The real kicker? Most issues boil down to “I didn’t install kernel-devel for exactly my running kernel.” Double‑check that you’re not mixing RHEL8 with CentOS7 packages.
That’s it—VMware Workstation 16 Pro should now be ready to spin up VMs on your RHEL 8 or CentOS 8 box. If something still feels wonky, drop a comment and we’ll dig deeper together.
