VMware ESXi and vSphere Cluster Management

Install VMware Workstation Player on Linux

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

This guide installs VMware Workstation Player on an existing Linux computer. The Linux computer is the host. VMware Player is the desktop virtualization application that runs on that host.

A virtual machine (VM) is a software-defined computer with virtual CPU, memory, storage, and network devices. After VMware Player is installed, you can create or open a VM and install a guest operating system inside it. The guest can be Linux, Windows, or another supported operating system. Installing VMware Player is therefore different from installing Linux inside a VM.

Before you begin

Check the current VMware/Broadcom product documentation and installer requirements before downloading. Support can vary by VMware release, Linux distribution, release version, desktop environment, kernel, CPU architecture, and guest operating system. Do not rely on an old compatibility list when a newer product release is available.

Build prerequisites

Install the compiler, make utility, kernel headers, and kernel development packages required by your distribution. Package names differ, so use your distribution's package manager and the current VMware requirements. The important condition is that the development files match the kernel reported by uname -r.

For example, Debian-based systems commonly use a build-essential package plus headers for the running kernel. RPM-based systems commonly use a compiler, make, kernel headers, kernel development files, and the distribution's development tools group. Use your distribution's current package documentation rather than copying package names blindly between distributions.

Secure Boot

Secure Boot is a firmware security feature that can require kernel modules to be signed before Linux loads them. VMware's virtualization and networking modules may therefore fail to load even when compilation succeeds. Decide with your organization's security policy whether to sign the modules and enroll an approved key, or use another approved Secure Boot configuration. Do not disable a security control without understanding its operational requirements.

Download and verify the Linux bundle

Download the Linux bundle installer appropriate to the host architecture from an authorized VMware/Broadcom software source. A bundle installer is a self-extracting Linux installer whose filename normally ends in .bundle.

Save it in a known directory, such as a downloads or temporary installation directory. Then inspect the directory and identify the actual filename:

cd /path/to/downloads
ls -lh
ls -lh VMware-Player-*.bundle

Use the real filename shown by the directory listing. Do not assume that a particular product version or filename is current.

If the provider publishes a SHA-256 checksum or signature, verify it before execution:

sha256sum VMware-Player-*.bundle

Compare the output with the checksum published by the software provider. A matching checksum helps confirm file integrity; a signature verification, when supplied and performed correctly, provides stronger authenticity evidence.

Choose an installation method

The --console option selects the text-based installation interface. Installation requires root privileges, which are administrative permissions needed to install system software and configure kernel components. Routine use normally does not require root privileges.

Install from the bundle

Graphical desktop procedure

1. Open a terminal and change to the directory containing the downloaded bundle.
2. Make the file executable as the user who owns it.
3. Start the installer with administrative privileges.
4. Read and accept the license terms if they are acceptable.
5. Review the installation destination, module-building choices, update-related options, and networking-related prompts.
6. Allow the installer to configure or build the required VMware components.
7. Finish the wizard and launch VMware Player from the desktop application menu.

cd /path/to/downloads
chmod +x VMware-Player-*.bundle
sudo ./VMware-Player-*.bundle

A graphical wizard may appear when a usable desktop display is available. Accept defaults only after checking what they change, particularly networking, update checks, installation locations, and module configuration.

Terminal-only procedure

For a remote shell or terminal-only host, run the console installer. The following uses sudo, which runs one command with elevated privileges:

cd /path/to/downloads
chmod +x VMware-Player-*.bundle
sudo ./VMware-Player-*.bundle --console

Answer each interactive prompt. The installer may ask about the license, destination directories, kernel module compilation, networking components, and update behavior. If your distribution does not provide sudo or policy forbids it, an administrator can use su - and run the installer from a root login shell.

Do not start the desktop application with sudo as a normal practice. Running it as root can create root-owned configuration files and virtual machine files, causing permission problems for your regular account.

What the installer configures

During installation or first launch, VMware may configure services and build kernel modules. A kernel module is code that can be loaded into the Linux kernel to provide functions such as virtualization support and virtual networking.

Expected components include virtualization-related modules and networking-related modules. Exact names and module behavior vary by VMware release and host kernel. If a module cannot be compiled or loaded, the application may open with warnings or refuse to start a VM.

Kernel modules are tied to the kernel and its interfaces. After a Linux kernel upgrade, modules built for the previous kernel may no longer be usable. Matching headers and development packages may be required, followed by a VMware module rebuild.

Configure virtual networking

Networking mode determines how a guest communicates with the host and external networks. Select the least permissive mode that meets the VM's purpose.

Start with NAT for a general-purpose guest when there is no requirement for a separate physical-network identity. Use bridged mode only when the network permits it, and use host-only mode for isolation. Firewalls, VPNs, wireless restrictions, and enterprise network policies can affect all three modes.

Launch and validate VMware Player

Start VMware Player from the desktop application menu or from a terminal as your regular user:

vmplayer

Confirm that the main window opens without privilege escalation. For a basic validation, open an existing VM or begin the create/open workflow. You do not need to complete guest installation to confirm that the application starts, but the VM workflow should be able to detect the available virtualization and networking features.

Check the application's version information from its help or about interface. For support, collect the product version, Linux distribution and kernel version, installer output, module-configuration output, and relevant VMware application logs. Log locations vary by release and user configuration, so use the product's support documentation or the application's support interface to identify them.

Recover after a Linux kernel update

A common failure pattern is that VMware worked before a kernel upgrade and then reports that a required module cannot load. First confirm the active kernel:

uname -r

1. Install the compiler, make utility, matching kernel headers, and kernel development packages for the active kernel.
2. Check that the installed VMware release supports the current kernel.
3. Reconfigure all available VMware modules:

sudo vmware-modconfig --console --install-all

The command's availability and exact behavior can vary by VMware release. If it is absent or fails, use the supported maintenance procedure for that release. Review the output for the first failing component, then restart VMware Player and test an existing VM.

Troubleshooting

Permission denied when executing the bundle

• Inspect permissions with ls -l.
• Apply execute permission with chmod +x VMware-Player-*.bundle.
• If the filesystem is mounted with noexec, move the bundle to an approved executable local filesystem and run it there.

The installer cannot build kernel modules

• Check the active kernel with uname -r.
• Install the compiler, make utility, matching headers, and kernel development packages.
• Confirm that the VMware release supports the current kernel.
• Review installer and module-configuration output to identify the failing component.

A required module cannot be loaded

• Run sudo vmware-modconfig --console --install-all when supported.
• Confirm that build prerequisites correspond to the active kernel.
• Check whether a kernel update occurred after VMware was installed.
• Review Secure Boot status. If it rejects an unsigned module, follow the approved module-signing or Secure Boot procedure.

The installer has no graphical interface

No graphical interface is expected when no desktop session, display variable, or remote display forwarding is available. Use the console option intentionally:

sudo ./VMware-Player-*.bundle --console

Installation does not inherently require a GUI. Launch the graphical application later from a local desktop session or another supported display setup.

The vmplayer command is not found

• Confirm that installation completed successfully.
• Use the desktop launch shortcut if one was created.
• Locate the installed executable with the system's file-search tools.
• Check whether the executable directory is in the user's PATH, but do not change the path until you know the installed product layout.

The VM has no network access

• Check whether the VM is using NAT, bridged, or host-only networking as intended.
• Test NAT first to separate VMware configuration problems from physical-network restrictions.
• Verify that VMware networking components and modules are available.
• Check the host connection, firewall, VPN, disconnected adapters, and enterprise network restrictions.

Security and maintenance guidance

• Obtain executable bundle installers only from an authorized software source.
• Verify published checksums or signatures before execution whenever they are available.
• Use root privileges only for installation and explicit maintenance tasks. Run VMware Player and normal VM workloads as a regular user.
• Keep the Linux host kernel, VMware product, guest tools, and guest operating systems updated according to compatible release guidance.
• Back up VM files before changing networking, upgrading VMware, upgrading the host kernel, or making other major host changes.
• Protect VM files because they can contain credentials, private data, and complete guest operating systems.

Next steps

After validation, continue with VMware Workstation Player on Linux installation reference when reviewing the command-line workflow again. The next operational tasks are creating or opening a VM, installing a guest operating system, configuring its network mode, and installing suitable guest tools.