Install VMware Workstation Player on a Linux Host

Learn how to download, verify, install, configure, and launch VMware Workstation Player on a supported Linux host with the Linux bundle installer.

Purpose and scope

This lesson installs VMware Workstation Player on a Linux host. The host is the physical computer and its Linux operating system. After installation, Player can create, open, and run virtual machines.

A guest operating system is the operating system running inside a virtual machine. Installing Player on Linux is different from installing Linux as a guest inside Player. This procedure prepares the Linux computer to run guests; it does not install Linux inside an existing virtual machine.

The exact prompts and supported systems can vary by Linux distribution, desktop environment, and Player release. Match this procedure to the release-specific compatibility and installation documentation for the version you intend to use.

For background, see the VMware Workstation Player course, what a virtual machine is, and reasons to use VMware Workstation Player.

Compatibility and prerequisites

At a high level, VMware has provided Linux host support across distributions such as Ubuntu, Red Hat Enterprise Linux, CentOS or compatible enterprise distributions, Oracle Linux, openSUSE, and SUSE Linux Enterprise variants. This does not mean that every release of each distribution is supported. Verify the chosen Player release against the vendor's current compatibility documentation, especially when using a new Linux kernel.

Before downloading the installer, prepare the host with a 64-bit CPU, adequate memory, sufficient disk space, a usable desktop session for graphical operation, and hardware virtualization support for the guest workloads you plan to run. Hardware virtualization usually refers to Intel VT-x or AMD-V. It may need to be enabled in firmware. See enabling VT-x for related background.

VMware uses Linux kernel modules to connect its virtualization and networking functions to the running kernel. The host therefore normally needs a supported kernel, matching kernel headers or development files, a compiler toolchain, the make utility, and required system libraries. Package names differ between distributions.

Secure Boot can prevent third-party kernel modules from loading. If Secure Boot is enabled, the modules may need to be signed and their signing key enrolled according to your organization's security policy. Do not disable a security control without understanding the policy and operational consequences.

Item	Why It Is Needed	How to Check	Typical Package or Setting
Supported distribution and release	Player must support the host operating system and kernel combination.	Check the distribution release information and the release-specific VMware compatibility documentation.	Ubuntu, RHEL-compatible, Oracle Linux, openSUSE, or SLE variant at a supported release.
64-bit CPU architecture	Current desktop virtualization workloads generally require a supported 64-bit host.	Run `uname -m` or inspect system information.	Typically `x86_64`.
Running kernel version	Kernel modules must be built for the kernel currently running.	Run `uname -r`.	Use matching headers or development files.
Kernel headers or development package	Provides files needed to compile external VMware modules.	Compare the installed package with `uname -r`.	Distribution-specific kernel header or development package.
Compiler and build tools	Compiles modules such as `vmmon` and `vmnet`.	Check that the compiler and `make` are installed.	Compiler toolchain, `make`, and required libraries.
Available RAM and disk space	The host needs resources for Player, guest memory, virtual disks, and snapshots.	Use the desktop system monitor and `df -h`.	Reserve more resources than the guest's minimum requirement.
Hardware virtualization	Supports efficient execution of many guest operating systems.	Inspect firmware settings and the guest workload requirements.	Intel VT-x or AMD-V enabled where supported.
Secure Boot status	Unsigned VMware modules may be rejected by the kernel.	Check firmware settings or use the distribution's Secure Boot status tool.	Sign and enroll modules when required by policy.

Download and verify the Linux installer

Obtain the appropriate Linux x86_64 bundle installer for the desired Player release from the vendor's official download source. Record the download directory; the commands later in this lesson assume that you can navigate to it.

A Linux bundle installer is a self-contained installer file that normally ends in .bundle. Its filename commonly identifies the product, version, build, architecture, and bundle extension, for example:

VMware-Player-<version>-<build>.x86_64.bundle

Choose the architecture that matches the host. Do not assume that an installer for another operating system or CPU architecture will work on Linux.

When the publisher provides checksum or signature data, verify the downloaded file before running it. A checksum confirms that the file matches the published digest; a signature can also provide evidence that it came from the publisher. Use the verification tool and algorithm specified with the release rather than guessing.

Prepare administrative access

Installation changes system directories and compiles or installs kernel modules, so it requires administrative privileges. root is the Linux administrative account with unrestricted system privileges. sudo runs an individual command with administrative privileges.

Use the method expected by your distribution. A root login shell is one option where direct root access is permitted:

su -

Many distributions instead recommend using sudo and keeping the normal user session active. The examples below use sudo. Replace the path with the directory where the bundle was downloaded.

cd /path/to/download-directory
ls -l VMware-Player-*.bundle

Inspect the exact filename before executing it. Then grant the bundle executable permission:

chmod +x VMware-Player-<version>-<build>.x86_64.bundle

An executable permission allows a file to be launched directly. If the shell reports permission denied even after this change, the filesystem may be mounted with noexec; see the troubleshooting section.

Choose the installation interface

When a bundle is launched inside a suitable graphical desktop session, it may open a graphical installation wizard. On a terminal-only system, a remote SSH session, or a session without the required graphical environment, the installer may use a text interface or fail to open the wizard.

Method	Example Invocation	Best Use Case	Expected Interface
Default bundle launch	`sudo ./VMware-Player-<version>-<build>.x86_64.bundle`	Local Linux workstation with a graphical session.	Graphical wizard when available; otherwise behavior depends on the release and environment.
Explicit console-mode launch	`sudo ./VMware-Player-<version>-<build>.x86_64.bundle --console`	SSH, remote administration, server installation, or no usable desktop.	Text-based prompts in the terminal.
Desktop launcher after installation	Open VMware Workstation Player from the application menu.	Routine use on a graphical workstation.	Graphical Player window as the regular user.
Terminal launch using vmplayer	`vmplayer`	Starting Player from a user's desktop terminal.	Graphical Player window, provided a graphical session is available.

Run the bundle installer

For a graphical workstation, launch the executable bundle with administrative privileges:

sudo ./VMware-Player-<version>-<build>.x86_64.bundle

For a terminal-only or remote installation, explicitly request console mode:

sudo ./VMware-Player-<version>-<build>.x86_64.bundle --console

The normal flow can include accepting the license, selecting update preferences, choosing an installation destination when the release presents that option, and compiling VMware kernel modules. Read prompts that affect licensing, update behavior, networking, or security. For a basic workstation setup, appropriate defaults are usually suitable, but defaults are not universal across releases.

A successful installation places application files on the host, may add desktop launcher integration, and installs or prepares VMware services and host kernel modules. The installer can compile modules immediately or defer module configuration until the first launch.

Configure and check kernel modules

A kernel module is code that can be loaded into the Linux kernel to add functionality. VMware commonly uses vmmon for virtual machine monitor functions and vmnet for virtual networking.

During first launch, Player may display a configuration step that builds modules for the currently running kernel. Complete that step with administrative authentication. The same process may be needed after a kernel update because modules compiled for an older kernel are not automatically valid for the new one.

After configuration, check whether the modules are loaded:

lsmod | grep -E 'vmmon|vmnet'

An empty result can indicate that the modules were not built, were not loaded, or were blocked by Secure Boot. Also confirm that the VMware virtual networking components are available when a guest needs network access. Exact service names and repair commands vary by Player release, so use the installed release's module configuration or repair workflow rather than applying an unrelated command.

Launch Player as a regular user

After installation and module setup, leave the root shell if you used one:

exit

Routine GUI operation should use the ordinary desktop account. Do not normally start Player as root; doing so can create root-owned virtual machine files and confusing permission problems.

Launch Player either from the desktop application menu or from a terminal:

vmplayer

The initial Player screen commonly provides actions to create a virtual machine, open an existing virtual machine, or configure preferences. To continue with guest management, see the Player home screen, starting a virtual machine, or VMware networking configurations.

Validate the installation and clean up

Verify the installed Player version in the graphical interface or with the product's supported command-line version option.
Confirm that Player starts without module, permission, or licensing errors.
Open an existing virtual machine, or begin the new virtual machine workflow far enough to confirm that Player can access the required guest files or installation media.
Run lsmod | grep -E 'vmmon|vmnet' when checking host module loading.
Leave the root shell with exit and continue using the normal user account.
Keep the downloaded bundle only if it is needed for repair or reinstallation. Otherwise remove it according to local retention and software-management policy.

Common problems and resolutions

Symptom	Likely Cause	Diagnostic Check	Resolution
Permission denied when starting the bundle	The file is not executable, or the filesystem is mounted with `noexec`.	Run `ls -l` on the bundle and inspect mount policy.	Use `chmod +x`; move the installer to an executable local directory or change the mount according to policy.
Compiler or header error	Build tools or matching kernel headers are missing.	Run `uname -r` and compare it with installed development files.	Install the compiler toolchain, `make`, required libraries, and matching kernel headers or development packages.
`vmmon` or `vmnet` build failure	The development files do not match the active kernel, or the Player release does not support that kernel.	Review the first compilation error in the module build output or logs.	Install matching development files, use a supported kernel, or use a compatible Player release.
Modules blocked by Secure Boot	Firmware or the kernel rejected unsigned third-party modules.	Check Secure Boot status and kernel messages.	Sign and enroll the modules, or adjust Secure Boot policy only with proper authorization.
Player does not start after a kernel update	Modules were built for the previous kernel.	Run `uname -r` and check loaded modules.	Install matching headers and run the VMware module configuration or repair workflow as administrator.
No graphical installer appears	No active graphical session exists, or the installation is remote.	Check whether the terminal has access to a desktop session.	Use `--console`, or perform the graphical setup from a local workstation.
`vmplayer` is not found	Installation did not complete, the path is not in the shell environment, or the product layout differs.	Confirm installer completion and inspect the application menu or installed files.	Use the desktop launcher, the installed binary's full path, or correct the environment configuration.
Virtual machines cannot use virtualization features	Intel VT-x or AMD-V is disabled, or nested virtualization is unavailable.	Inspect firmware settings and whether the Linux host itself is virtualized.	Enable supported hardware virtualization or expose nested virtualization where appropriate.

Example: Debian or Ubuntu prerequisites

On Debian- or Ubuntu-based systems, a typical prerequisite command is:

sudo apt install build-essential linux-headers-$(uname -r)

Package availability and exact requirements vary by release. On Fedora, RHEL-compatible, Oracle Linux, openSUSE, and SUSE Linux Enterprise systems, install the distribution's compiler toolchain, make, required libraries, and kernel development package matching uname -r with the appropriate package manager.

Maintenance and upgrades

Choose an upgrade that is compatible with both the Linux distribution and the running kernel. Product packaging, supported distributions, licensing terms, and product naming can change between releases, so do not treat an older installation procedure as universal.

Before upgrading, check for legacy VMware installations and conflicts involving old application files, services, or kernel modules. After a kernel change or Player upgrade, expect to rebuild or repair vmmon and vmnet. If a guest fails to start after an upgrade, check the active kernel, matching development files, Secure Boot policy, and the first module compilation error.