VMware ESXi and vSphere Cluster Management

VMware Workstation Player Course: Install, Create, and Manage Virtual Machines

Learn VMware Workstation Player fundamentals, installation, VM creation, guest OS setup, storage, networking, integration, migration, appliances, and troubleshooting.

Course overview

VMware Workstation Player is a desktop virtualization application used to run virtual machines (VMs) on a physical computer. This course explains how to prepare the host, install the application, create and configure VMs, install guest operating systems, manage virtual storage and networking, move or back up VMs, and troubleshoot common problems.

You should be comfortable navigating Windows or another desktop operating system, managing files and folders, installing applications, and understanding basic CPU, RAM, disk, IP addressing, gateways, and DNS.

Virtualization fundamentals

Virtualization is the creation of software-defined computing resources that use physical hardware. A virtual machine is a software-defined computer containing virtual processors, memory, storage, network adapters, and other devices. It can run an operating system and applications much like a physical computer.

The physical computer is the host system. Its directly installed operating system is the host operating system. The operating system installed inside a VM is the guest operating system. VMware Workstation Player acts as a desktop hypervisor: software that coordinates VM access to physical CPU, memory, storage, and networking.

Virtual hardware is the hardware presented to the guest, such as a virtual CPU, virtual RAM, a virtual hard disk, a CD/DVD device, and a virtual network adapter. A virtual appliance is a prebuilt VM packaged for a particular purpose, often as an OVF or OVA file.

Desktop virtualization is useful for testing operating systems, learning system administration, isolating untrusted or experimental software, and running several operating systems on one computer. Resources are shared: assigning more RAM or processors to a VM leaves fewer resources for the host and other VMs. A virtual disk also consumes host storage, even when its configured capacity is larger than its current file size.

Requirements and preparation

Check the current VMware product documentation and vendor distribution source for supported host operating systems, installer architecture, licensing, and hardware requirements. Select an installer that matches the host platform and processor architecture. A modern 64-bit host, adequate RAM, available disk space, and a supported processor are typical starting points.

Most processors used for virtualization provide hardware virtualization features such as Intel VT-x or AMD-V. If the application reports that virtualization is unavailable, enter the computer's BIOS or UEFI firmware settings and enable the relevant virtualization option. Firmware menus vary. Host security or virtualization features can also affect compatibility.

Before creating a VM, assess:

• RAM: reserve enough memory for the host and its applications. Do not assign all host RAM to one VM.
• CPU capacity: begin with a modest virtual processor count. More virtual CPUs do not always improve performance.
• Disk space: allow room for the VM files, guest updates, snapshots or state files where applicable, logs, and temporary growth.
• Network access: decide whether the guest needs internet access, access to the physical LAN, or an isolated lab network.
• Installation media: obtain an authorized ISO image or physical media and keep any required product key available.

Store VM folders on reliable storage with sufficient free space. Avoid locations that are routinely synchronized, cleaned, or disconnected while a VM is running. A VM folder may grow over time, so monitor both host free space and guest disk usage.

Downloading and installing VMware Workstation Player

1. Use the vendor's official distribution source and select the installer for the host operating system and architecture.
2. Verify that the download completed and that the file came from a trusted source.
3. Run the installer with the permissions required by the host operating system.
4. Accept the license terms when authorized to do so.
5. Review optional update or product-improvement settings and choose the settings appropriate for your environment.
6. Complete the installation and restart the host if the installer requests it.

Start VMware Workstation Player from the operating system's application menu. The main interface normally includes a library of known VMs and controls for creating, opening, configuring, powering on, suspending, and removing them. Creating a new VM builds a new configuration and usually a new virtual disk. Opening an existing VM registers a VM that already has a configuration file and associated files.

To maintain the application, use its supported update mechanism or the vendor's current installer. A repair option may restore missing application components. Uninstalling the application removes the virtualization software, but it does not necessarily remove every VM folder; confirm what the uninstaller offers before proceeding.

Creating a virtual machine

1. Choose New Virtual Machine.
2. Select an installation source: an ISO image, physical media, or the option to install the guest operating system later. An ISO image is a file containing the contents of optical installation media.
3. Select the guest operating system family and version. This lets VMware apply suitable default virtual hardware and compatibility settings.
4. Enter a descriptive VM name and choose a storage location. Use a location with adequate free space.
5. Set the virtual disk capacity. Choose a disk-file layout appropriate to the workload; a growable disk can conserve space initially, while a preallocated disk reserves capacity earlier and may offer more predictable storage behavior.
6. Review the summary. Confirm the ISO, guest version, name, location, memory, processors, network mode, and disk settings.
7. Finish creation, then adjust settings before the first boot if necessary.

Keep VM names and folder names clear, especially when several test systems exist. Do not assume that changing the label in the library changes every path or guest hostname associated with the VM.

Installing the guest operating system

1. Attach the authorized ISO through the VM's CD/DVD device, or insert physical installation media.
2. Power on the new VM and boot from the installation media.
3. Follow the guest operating system's normal installation process.
4. When prompted, select the virtual disk and create the required partitions. The guest sees the virtual disk as its own storage device.
5. Complete regional, account, licensing, network, and other initial configuration steps.
6. After the first successful boot, install VMware Tools, the guest-side utilities and drivers that improve integration, display behavior, pointer handling, and device support.
7. Restart the guest when requested, then verify display resizing, mouse integration, clipboard behavior, time synchronization, and other supported features.

Shut down or restart the guest through its own operating-system controls whenever possible. A graceful shutdown allows applications and filesystems to close cleanly. Use forced power-off only when the guest is unresponsive, because it is similar to removing power from a physical computer.

Virtual machine hardware configuration

Open the VM's settings from the library. Many hardware changes require the VM to be completely powered off, not merely suspended. Configure only the resources the guest needs.

• Memory: assign enough for the guest workload while reserving RAM for the host.
• Processors: start with one or two virtual processors for a basic lab and increase only when testing shows a need.
• Virtualization engine: use the appropriate processor virtualization options for the host and nested-virtualization requirements.
• Hard disks: add, remove, expand, or inspect virtual disks carefully.
• CD/DVD: connect physical media or attach and detach an ISO image. Disconnect installation media after setup to prevent an unwanted reinstall.
• USB: configure the USB controller and choose which connected device belongs to the host or guest.
• Sound, display, printers, and shared folders: enable only what the guest requires and what the product and guest support.
• Network adapter: select the required network mode and ensure the adapter is connected.

Changing virtual hardware can cause the guest to detect new devices, request drivers, change device names, or fail to boot if a critical controller or disk is altered. Record the original configuration before making significant changes.

Virtual disks and VM storage

A virtual disk is a file or set of files that behaves like a hard disk inside the guest. VMDK is a common VMware virtual disk format. The guest partitions and formats the virtual disk; the host stores the resulting data inside the VMDK files.

For a Linux guest, inspect storage before preparing an added disk:

lsblk
df -h

Then initialize, partition, format, and mount the correct device using the guest's normal storage tools. For a Windows guest, use its disk-management utility to bring the disk online, initialize it, create a volume, format it, and assign a drive letter.

Disk expansion has two stages: enlarge the virtual disk in VMware, then extend the guest partition and filesystem. Plan for host-side growth and maintain free space. Never manually rename, move, or delete individual VM files while the VM is running or suspended.

Virtual networking

A virtual network adapter connects the guest to a virtual switch and, depending on its mode, to the host or physical network.

Use DHCP when the virtual network provides automatic addressing. Use a static IP address when predictable addressing is needed, such as a lab. For two isolated guests, an example is VM1 192.168.56.10/24 and VM2 192.168.56.11/24, with no default gateway when the lab must remain isolated.

Test networking in stages. First verify the adapter is connected and inspect the guest configuration:

ipconfig /all

In a Linux guest, use:

ip addr
ip route

Test the local gateway, then an external IP address, and finally DNS:

ping 8.8.8.8
nslookup example.com

Linux example:

ping -c 4 example.com

Bridged networking may be restricted by Wi-Fi adapters, corporate access controls, VPNs, firewalls, or networks that limit multiple device identities. NAT is often the simplest first test for internet access. Host-only is safer for experiments that must not reach the normal LAN.

Operating and managing virtual machines

The VM library helps you organize and open registered machines. Common states are:

• Running: guest code is executing and hardware settings are generally locked.
• Suspended: execution is paused and the VM's current memory state is saved for later resumption.
• Powered off: the guest is not executing and is normally safe for hardware changes, copying, and relocation.

Use the guest's shutdown command for a graceful stop. Use restart when the guest must reload its operating system. Suspend is convenient for short interruptions but creates state files and should not replace a clean shutdown for backups or moves. Forced power-off is a recovery action, not a normal shutdown method.

You can change the library display name and, with care, relocate the VM folder. Power off the VM before moving files or changing hardware. After a move, confirm that all disk paths remain valid.

Moving, copying, and deleting VMs

A typical VM folder contains a VMX configuration file, one or more VMDK virtual disks, log files, and state-related files created during execution or suspension. The VMX describes virtual hardware and points to associated files.

1. Gracefully shut down the guest and confirm the VM is powered off.
2. Copy the complete VM folder to the new drive or computer. Preserve the folder structure and all disk files.
3. Open the VMX file from the new location in VMware Workstation Player.
4. When asked whether the VM was copied or moved, choose the answer that reflects what you did. This can affect virtual hardware identity and networking.
5. Boot the VM and verify the guest OS, applications, disks, and network identity.

A safe backup is a complete copy made after a clean shutdown. If the copy will run alongside the original, use distinct guest hostnames and IP addresses and review the copied-versus-moved choice. Do not run duplicate systems with conflicting identities on the same network.

Removing a VM from the library unregisters it but leaves its files on disk. Permanently deleting the VM removes its files and may be unrecoverable. Confirm the location and backup status before deleting any VMDK.

Virtual appliances and existing VMs

An OVF package describes a virtual appliance and its associated files. An OVA is a single-file archive containing an OVF appliance and related contents. Obtain appliances from trusted sources and inspect their documentation and default credentials before use.

Use the available open or import workflow to register an OVF or OVA. Review CPU, memory, disks, network mode, and any security-sensitive settings before the first boot. To use an existing VMware VM, open its VMX configuration file and allow the application to register it. A VM created by another VMware product or version may display a compatibility prompt. Preserve a backup and choose a compatibility level appropriate for the current product and required features.

Integration between host and guest

VMware Tools improves mouse movement, display resizing, clipboard integration, time synchronization, and supported device behavior. Shared folders, drag-and-drop, and other integration features depend on the guest, product version, and configuration.

When shared folders are enabled, the guest accesses designated host directories through the integration mechanism provided by VMware Tools. Share only the folders required for the task. Clipboard sharing and drag-and-drop can transfer sensitive data across the host-guest boundary.

A USB device normally belongs to either the host or the guest at a time. Connect it to the guest through the VM controls when the guest must operate it; disconnect it from the guest before expecting the host to use it. Safely eject removable media from the guest before disconnecting it. Detach an installation ISO after setup when it is no longer needed.

Practical labs

Windows test VM

1. Obtain an authorized Windows ISO and confirm host disk space.
2. Create a VM with modest initial CPU, RAM, and disk allocations.
3. Install Windows and complete initial configuration.
4. Install VMware Tools.
5. Verify display resizing, mouse integration, and internet access, preferably with NAT first.

Linux learning environment

1. Create a Linux VM from an ISO image.
2. Use NAT for ordinary internet access.
3. Add a second virtual disk.
4. In Linux, identify it with lsblk, then partition, format, and mount it.
5. Use the VM for isolated command-line and administration practice.

Two-VM isolated lab

1. Create two guest VMs and set both adapters to host-only networking.
2. Assign compatible static addresses, such as 192.168.56.10/24 and 192.168.56.11/24.
3. Omit a default gateway when the lab must remain isolated.
4. Test guest-to-guest and host-to-guest communication while confirming that normal LAN and internet access are unavailable.

Move a VM to a larger drive

1. Gracefully shut down the guest.
2. Copy the complete VM folder to the larger drive.
3. Open the VMX file from the new folder.
4. Choose the correct copied-versus-moved identity option.
5. Confirm that the VM boots and that its network identity is appropriate.

Run a virtual appliance

1. Obtain a trusted OVF or OVA package.
2. Open or import it using the supported workflow.
3. Review hardware and network settings.
4. Boot it and complete its initial guest configuration.

Maintenance, safety, and troubleshooting

Keep the host application, VMware Tools, guest operating system, and guest applications updated through supported methods. Monitor host free space and guest capacity. Before major changes, shut down the VM and make a verified backup copy.

Hardware virtualization unavailable

Check whether Intel VT-x or AMD-V is enabled in BIOS or UEFI. Confirm processor compatibility and read the exact error. Host virtualization or security features may require a compatible configuration.

No guest internet access

Confirm that the virtual adapter is connected. Try NAT for a basic test. Inspect the guest IP address, gateway, and DNS independently, then compare the result with the host. Check host firewalls, VPN software, Wi-Fi limitations, and enterprise network policies.

Slow VM or unresponsive host

Reduce excessive RAM or virtual processor assignments, close unnecessary host applications, free disk space, and check whether the guest is updating or indexing. Slow or heavily used storage can also reduce performance.

Display or mouse integration failure

Install or update VMware Tools and restart the guest if requested. Then review guest display settings and test resizing and pointer integration again.

Copied VM has a conflict

Give the copied guest a distinct hostname and IP address. Review the copied-versus-moved identity choice before connecting both systems to the same network.

Missing virtual disk after a move

Only moving the VMX file, omitting disk files, renaming files, or moving a running or suspended VM can break disk paths. Restore the complete VM folder from a known-good copy and open the correct VMX file.

When requesting support, record the host operating system, VMware product and version, guest operating system, VM power state, hardware settings, exact error text, recent changes, network mode, and relevant VM log files. Restore from a verified backup when the guest data is important. Rebuild a disposable lab VM when repair would take longer than recreating it; seek product or system-administration support when the problem involves firmware, host security, storage failure, licensing, or enterprise networking.

Exam-relevant notes

• The host OS runs directly on physical hardware; the guest OS runs inside a VM.
• CPU, RAM, disk, and network resources assigned to VMs come from or depend on host resources.
• VT-x or AMD-V may need to be enabled in firmware.
• NAT commonly provides guest outbound access through the host; bridged makes the guest a separate physical-network device; host-only is intended for isolation.
• Installing VMware Tools improves guest integration but does not replace guest operating-system drivers or updates.
• Expanding a virtual disk requires a separate guest-side partition and filesystem expansion.
• Removing a VM from the library is not the same as deleting its files.
• Copy or move a VM only after a clean shutdown and include the complete VM folder.
• A VMDK stores virtual disk data, while a VMX describes VM configuration.

For related study, see the VMware Workstation Player course.