Workstation Player 16 Windows User Guide
Workstation Player 16 Windows User Guide
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
©
Copyright 2020 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc. 2
Contents
VMware, Inc. 3
Using VMware Workstation Player for Windows
VMware, Inc. 4
Using VMware Workstation Player for Windows
VMware, Inc. 5
Using VMware Workstation Player for Windows
VMware, Inc. 6
Using VMware Workstation Player for Windows
VMware, Inc. 7
Using VMware Workstation Player for Windows
16 Using vctl Command to Manage Containers and Run Kubernetes Cluster 168
Using the vctl Utility 169
Enabling KIND to Use vctl Container as Nodes to Run Kubernetes Clusters 169
Running vctl Commands 170
Syntax of vctl Commands 170
VMware, Inc. 8
Using VMware Workstation Player for Windows
VMware, Inc. 9
Using VMware Workstation Player for
Windows
Using VMware Workstation Player for Windows describes how to use VMware Workstation
Player™ to create, configure, and manage virtual machines on a Windows host.
Intended Audience
This information is intended for anyone who wants to install, upgrade, or use Workstation Player
on a Windows host.
VMware, Inc. 10
Introduction and System
Requirements 1
Workstation Player is a desktop application that lets you create, configure, and run virtual
machines. You can also use Workstation Player to download and run virtual appliances.
Host computers that run Workstation Player must meet specific hardware and software
requirements. Virtual machines that run in Workstation Player support specific devices and
provide certain features.
Supported Processors
The following host systems are supported.
n Systems using processors launched in 2011 or later except for systems using the following
processors.
n Intel Atom processors based on the 2011 Bonnell micro-architecture. For example, Atom
Z670/Z650 and Atom N570.
n Intel Atom processors based on the 2012 Saltwell micro-architecture. For example, Atom
S1200, Atom D2700/D2500, and Atom N2800/N2600.
VMware, Inc. 11
Using VMware Workstation Player for Windows
n Intel processors based on the 2010 Westmere micro-architecture. For example, Xeon
5600, Xeon 3600, Core i7-970, Core i7-980, and Core i7-990.
If you have an Intel CPU that has VT-x support, you must verify that VT-x support is enabled in
the host system BIOS. The BIOS settings that must be enabled for VT-x support vary depending
on the system vendor. See the VMware knowledge base article at http://kb.vmware.com/kb/
1003944 for information about how to determine if VT-x support is enabled.
When you install a 64-bit operating system, Workstation Player performs checks to make sure
the host system has a supported processor. You cannot install a 64-bit operating system if the
host system does not meet the processor requirements.
To see a list of the supported host operating systems, search the online VMware Compatibility
Guide on the VMware Web site.
Workstation Player is not listed, but the information for Workstation Pro is applicable to
Workstation Player. Operating systems that are not listed are not supported for use in a virtual
machine.
The minimum memory required on the host system is 2 GB. 4 GB and above is recommended.
To support Windows 7 Aero graphics in a virtual machine, at least 3 GB of host system memory
is required.
See your guest operating system and application documentation for more information on
memory requirements.
VMware, Inc. 12
Using VMware Workstation Player for Windows
To support Windows 7 Aero graphics, the host system should have either an NVIDIA GeForce
8800GT or later or an ATI Radeon HD 2600 or later graphics processor.
Important 3D benchmarks, such as 3DMark '06, might not render correctly or at all when
running Windows Vista or Windows 7 virtual machines on some graphics hardware.
Hard disk n IDE, SATA, SCSI and NVMe hard drives are supported.
n At least 1 GB free disk space is recommended for each guest operating
system and the application software used with it. If you use a default setup,
the actual disk space needs are approximately the same as those for installing
and running the guest operating system and applications on a physical
computer.
n For installation, approximately 200 MB free disk space is required on Linux
and 250 MB free disk space is required on Windows. You can delete the
installer after the installation is complete to reclaim disk space.
Optical CD-ROM and DVD n IDE, SATA, and SCSI optical drives are supported.
n CD-ROM and DVD drives are supported.
n ISO disk image files are supported.
Floppy Virtual machines can connect to disk drives on the host computer. Floppy disk
image files are also supported.
Solid-State Drives
If your host machine has a physical solid-state drive (SSD), the host informs guest operating
systems they are running on an SSD.
VMware, Inc. 13
Using VMware Workstation Player for Windows
This allows the guest operating systems to optimize behavior. How the virtual machines
recognize SSD and use this information depends on the guest operating system and the disk
type of the virtual disk (SCSI, SATA, IDE, or NVMe).
n On Windows 8, Windows 10, Ubuntu, and Red Hat Enterprise Linux virtual machines, all drive
types can report their virtual disks as SSD drives.
Note
n NVMe virtual hard disks are natively supported for Windows 8.1 and later.
n Several Linux operating systems support NVMe while others do not. Check with the
operating system vendor.
n On Windows 7 virtual machines, only IDE and SATA virtual disks can report their virtual disks
as SSD. SCSI virtual disks only report as SSD when used as a system drive in a virtual
machine, or as a mechanical drive when used as a data drive inside a virtual machine.
Use the virtual machine operating system to verify your virtual machine is using SSD as its virtual
disk.
Non-Ethernet networks are supported by using built-in network address translation (NAT) or by
using a combination of host-only networking and routing software on the host operating system.
For the most recent list of guest operating systems that VMware products support, see the
VMware Compatibility Guide site: http://www.vmware.com/resources/compatibility/search.php.
Workstation Player is not listed, but the information for Workstation Pro is applicable to
Workstation Player. Operating systems that are not listed are not supported for use in a virtual
machine.
For instructions about how to install the most common guest operating systems, see the VMware
Guest Operating System Installation Guide: http://partnerweb.vmware.com/GOSIG/home.html.
VMware, Inc. 14
Using VMware Workstation Player for Windows
n One virtual processor on a host system that has one or more logical processors.
Note Workstation Player considers multiprocessor hosts that have 2 or more physical CPUs,
single-processor hosts that have a multicore CPU, and single-processor hosts that have
hyperthreading enabled, to have two logical processors.
Workstation Player runs virtual machines that were created by using Workstation 4 and later,
GSX Server 3.x, VMware Server, and ESX Server 2.5 and later. Workstation 4 virtual machines
run in legacy mode. You must use another VMware product to upgrade virtual machines
created in versions earlier than Workstation 4 before you can run them in Workstation Player.
VMware, Inc. 15
Installing and Using Workstation
Player 2
Installing Workstation Player typically involves running a standard GUI wizard.
Prerequisites
n Verify that your Windows machine meets the host system requirements. See Host System
Requirements for Workstation Player.
n Download the Workstation Player installer file to your Windows machine. You can obtain the
Workstation Player installer file from the VMware Web site.
n If you are installing the purchased version of Workstation Player, verify that you have a
license key.
You can use Workstation Player free of charge for non-commercial use. When you use
Workstation Player for the first time, you can enter your email address and use it free of charge,
or you can enter your purchased license key to use Workstation Player and have access to
additional features.
VMware, Inc. 16
Using VMware Workstation Player for Windows
Procedure
3 (Optional) To activate Workstation Player features, start Workstation Player and enter your
license key.
a Double-click the Workstation Player icon or select Start > All Programs VMware Player to
start Workstation Player.
Prerequisites
n Verify that the host system meets the host system requirements.
n Verify that the host computer has version 2.0 or later of the MSI runtime engine. This version
of the installer is available in versions of Windows beginning with Windows XP and is
available from Microsoft. For more information, see the Microsoft Web site.
Procedure
1 Log in to the host system as the Administrator user or as a user who is a member of the local
Administrators group.
If you log in to the host system as the Administrator user or as a user who is a member of the
local Administrators group.
For example, if you enter setup.exe/?, the flag displays a windows message box with the
command line usage for the installer.
VMware, Inc. 17
Using VMware Workstation Player for Windows
You can use the optional INSTALLDIR property to specify a file path for the installation that is
different from the default location.
Note The double quotes around the file path are important. All the MSI arguments are
passed with the /v option. The outer quotes group the MSI arguments and the double quotes
put a quote in that argument.
You can also run an unattended Workstation Player uninstallation on a Windows host. The
following example uninstalls Workstation Player and removes the license from the host.
Installation Properties
When you perform an unattended installation of Workstation Player, you can customize the
installation by specifying installation properties in the installation command.
To specify an installation property in the installation command, use the format property="value".
A value of 1 means true and a value of 0 means false.
INSTALLDIR Install Workstation Player in a directory that is different from C:\Program Files
the default Workstation Player location. (86)\VMware\VMware
Player
VMware, Inc. 18
Using VMware Workstation Player for Windows
SERIALNUMBER Lets you enter the license key when Workstation Player is
installed. Enter the license key with hyphens, for example,
"xxxxx-xxxxx-xxxxx-xxxxx-xxxxx".
SUPPORTURL Set a support URL or email alias specifically for your users to
contact with product issues through the Workstation Player
Help menu.
You might have a desktop shortcut, a quick launch shortcut, or a combination of these options in
addition to a Start menu item.
Procedure
Procedure
u Use the icons on the Home tab to create a new virtual machine, open an existing virtual
machine, download a virtual appliance, or view the Workstation Player help system.
u Select a powered-off virtual machine in the library see the summary view.
The summary view shows a summary of configuration information and the virtual machine
state. You can start the virtual machine and edit virtual machine settings from the summary
view.
u Select a powered-off virtual machine in the library and click Play virtual machine to start the
virtual machine and see the console view.
u Select a virtual machine in the library and use the Virtual Machine menu on the menu bar to
perform all virtual machine operations for the selected virtual machine.
VMware, Inc. 19
Using VMware Workstation Player for Windows
u When a virtual machine is powered on, use the icons on the status bar to perform actions on
virtual devices such as hard disks, CD/DVD drives, floppy drives, and network adapters.
You can click or right-click on a removable device icon to connect or disconnect the device or
edit its settings.
u Use the About VMware Player window to access information about your installation of
Workstation Player, including license key information.
n If you have a version of Workstation Player licensed for multiple users, the Type field
displays Volume and your license key is not displayed.
n If you did not enter a license for Workstation Player, the Type field displays Not
applicable and a license key is not displayed.
n If you have an evaluation license key for Workstation Player, the Type field displays Not
applicable. The date the evaluation license key expires is also displayed.
n File managers, such as Windows Explorer, on the host system and virtual machines.
n Applications, such as zip file managers, which support drag-and-drop extraction of individual
files.
When you drag a file or folder between the host and a virtual machine, Workstation Player
copies the file or folder to the location where you drop it. For example, if you drop a file on the
desktop icon of a word processor, the word processor opens a copy of the original file. The
original file does not include changes that you make to the copy.
VMware, Inc. 20
Using VMware Workstation Player for Windows
Initially, the application opens a copy of the file that is stored in the temp directory. On Windows,
the temp directory is specified in the %TEMP% environment variable. On Linux and Solaris, the temp
directory is /tmp/VMwareDnD. Save the file in a different directory to protect changes that you
make.
n You must install VMware Tools in a virtual machine to use the drag-and-drop feature.
n The drag-and-drop feature requires Linux hosts and guests to run X Windows and Solaris 10
guests to run an Xorg X server and JDS/Gnome.
n You can drag images between applications on Windows hosts and applications on Windows
guests only. Dragging images is not supported for Linux hosts or guests.
n You can drag files and directories, email attachments, plain text, and formatted text between
Linux and Windows hosts and Linux, Windows, and Solaris 10 guests only.
n Dragging plain text and formatted text (including the formatting) is restricted to amounts less
than 4 MB.
n Workstation Player uses the PNG format to encode images that are dragged. Dragging
images is restricted to images smaller than 4 MB after conversion to PNG format.
You can also cut, copy, and paste images, plain text, formatted text, and email attachments
between applications running on the host system and applications running in virtual machines.
Copying and pasting email attachments is especially useful in Unity mode. Use the normal hot
keys or menu choices to cut or copy and paste.
n You must install VMware Tools in a virtual machine to use the copy and paste feature.
n The copy and paste feature works with Linux and Windows hosts and Linux, Windows, and
Solaris 10 guests only.
n The copy and paste feature requires Linux hosts and guests to run X Windows and Solaris 10
guests to run an Xorg X server and JDS/Gnome.
n Copying and pasting email attachments is restricted to images or files smaller than 4 MB.
VMware, Inc. 21
Using VMware Workstation Player for Windows
n Copying and pasting plain text and formatted text (including the formatting) is restricted to
amounts less than 4MB.
n Copying and pasting text is restricted to text in languages that can be represented by
Unicode characters.
n Workstation Player uses the PNG format to encode images that are copied and pasted.
Copying and pasting images is restricted to images smaller than 4 MB after conversion to
PNG format.
Procedure
Results
A Web browser opens to the Virtual Appliance Marketplace page on the VMware Web site. You
can browse to and download virtual appliances from this page.
Removing a virtual machine from the library does not delete the virtual machine or any of its files
from the host file system. The virtual machine is removed only from the library. If you open the
virtual machine again, the virtual machine is added back to the library.
Prerequisites
Procedure
u Select the virtual machine, right-click, and select Remove VM from the Library.
Results
The virtual machine is removed from the library without any confirmation.
VMware, Inc. 22
Using VMware Workstation Player for Windows
Procedure
VMware, Inc. 23
Changing Workstation Player
Preference Settings 3
Workstation Player preference settings are global configuration settings that apply to
Workstation Player and the virtual machines that you run in Workstation Player.
To change Workstation Player preference settings, select Player > File > Preferences.
Suspend the virtual machine The virtual machine is suspended when you close it. The
next time you start Workstation Player, the virtual machine
resumes operation from the point at which it was
suspended.
Power off the virtual machine The virtual machines is powered off when you close it. The
next time you start Workstation Player, the virtual machine
is in a powered off state.
Leave the virtual machine running The virtual machine remains running in the background
when you close it. The next time you start Workstation
Player, the virtual machine is in a powered on state.
VMware, Inc. 24
Using VMware Workstation Player for Windows
Confirm before closing a virtual machine Workstation Player prompts you for confirmation when you
close a virtual machine.
Return to the VM Library after closing a virtual machine Workstation Player returns the virtual machines to the
library after you close it. You can open another virtual
machine or edit virtual machine settings.
To configure software updates settings, select Player > File > Preferences.
Check for product updates on startup Check for new versions of the application and installed components
when you start Workstation Player. This setting is selected by
default.
Check for new software components as needed Check for a new version of a component when a component, such
as VMware Tools, is required. When this setting is selected,
Workstation Player verifies if a new version is available to download
and install.
Download All Components Now Manually download all of the available software components to the
host system. Click this button if you are planning to use a virtual
machine at a later time when you do not have access to the Internet.
Connection Settings Click this button to configure a proxy server to connect to the
VMware Update Server.
To configure proxy connection settings, select Player > File > Preferences and click Connection
Settings.
Windows proxy settings (Windows hosts only) Workstation Player uses the host proxy settings from the
Connections tab in the Internet Options control panel to access the VMware Update
Server.
Click Internet Options to set the guest connection options.
VMware, Inc. 25
Using VMware Workstation Player for Windows
System proxy settings (Linux hosts only) Workstation Player uses the host proxy settings to access the
VMware Update Server.
Manual proxy settings Select an HTTP or SOCKS proxy, specify the proxy server address, and designate a
port number to access the VMware Update Server.
Username and Password The username and password to use for proxy server authentication. On Linux hosts, if
either the Username or Password text box is blank, Workstation Player uses the
username and password set in the gnome settings.
You must restart Workstation Player for proxy setting changes to take effect.
By keeping your software up-to-date, you can take advantage of new product features and
performance improvements, ensure that your system includes the latest patches, and obtain
timely support for new guest operating systems. You can enable the automatic software update
feature when you install Workstation Player or by configuring Workstation Player preference
settings. You can disable the feature at any time.
To determine if software updates are available, the VMware software updates feature securely
sends the following anonymous information to VMware.
n A universal unique identifier (UUID), which it uses to identify each individual system
n The product name, the product version, and the build number
n Your host operating system name, version, and the locale setting
The VMware software updates feature does not collect any personal data, such as your name,
address, telephone number, or mail address. Your product license key and MAC address are not
sent to VMware, and VMware does not store your IP address with the data that it receives from
you.
VMware might use the information it receives from the software update feature for product
planning purposes. VMware limits access to your data and uses industry-standard controls to
protect your information, including physical access controls, Internet firewalls, intrusion detection,
and network monitoring.
The information collected by the VMware software updates feature is handled in accordance
with VMware Privacy Policy.
VMware, Inc. 26
Using VMware Workstation Player for Windows
Workstation Player participates in the VMware CEIP. Information about the data collected
through CEIP and how VMware uses it are in the Trust & Assurance Center at http://
www.vmware.com/trustvmware/ceip.html.
The CEIP appears the first time you start Workstation Player after you install the product. You
must then make a selection. You can change your selection any time afterwards.
Procedure
3 Join or leave the CEIP depending on the participation preference currently selected.
Option Description
Virtual printing is disabled by default. To enable or disable virtual printing, select Player > File >
Preferences and in the Devices section, click Change Settings, then select Enable virtual
printers. You must install the VMware Virtual Printer application on the virtual machine to enable
printing. See Enabling a Virtual Machine to Print to Host Printers. You must have administrator
privileges to enable or disable virtual printers.
The Workstation Player printer feature uses VMware Virtual Printer technology to replicate the
host system printer mapping in the virtual machine. When you enable the virtual machine printer,
Workstation Player configures a virtual serial port to communicate with the host printers.
Note If any virtual printers are powered on when the Enable virtual printers option is selected,
you must reboot the virtual machines, or suspend and resume them, for the setting to take
effect.
VMware, Inc. 27
Using VMware Workstation Player for Windows
n Ask you which machine you want to connect the device to.
To configure USB device connection settings, select Player > File > Preferences. For an overview
of connecting USB devices to virtual machines, see Connecting USB Devices to Virtual Machines.
For specific information about configuring the USB device connection settings, see Configure
USB Device Connection Behavior.
Note The Color Theme setting is only available on Windows 10 1809 or later host systems.
Setting Description
System (use app mode of HOS) The Workstation Player window appears consistent with
Windows 10 host's app mode color settings. This is the
default setting.
VMware, Inc. 28
Creating Virtual Machines in
Workstation Player 4
You use the New Virtual Machine wizard to create virtual machines. The New Virtual Machine
wizard guides you through the steps for setting up a new virtual machine, helping you set
options and parameters.
To start the New Virtual Machine wizard, select Player > File > New Virtual Machine, or click
Create a New Virtual Machine on the welcome page.
A virtual machine has an operating system and virtual resources that you manage in much the
same way that you manage a physical computer. For example, you install an operating system in
a virtual machine in the same way that you install an operating system on a physical computer.
You must have a CD-ROM, DVD, or ISO image that contains the installation files from an
operating system vendor.
VMware, Inc. 29
Using VMware Workstation Player for Windows
n A name for the virtual machine and a location for the virtual machine files.
n The size of the virtual disk and whether to split the disk into multiple virtual disk files.
If you select an installer disc or an ISO image file and the operating system supports Easy Install,
the guest operating system installation is automated and VMware Tools is installed. If the installer
disc or ISO image file contains a product key number and is already set up to perform an
unattended installation, the only benefit of using Easy Install is the automatic installation of
VMware Tools.
If you instruct the New Virtual Machine wizard to create a virtual machine that has a blank hard
disk, the wizard prompts you to specify an operating system and version and you must install the
guest operating system manually after the virtual machine is created. Workstation Player uses
this information to set the appropriate default values, name files associated with the virtual
machine, adjust performance settings, and work around special behaviors and bugs in the guest
operating system. If the operating system you plan to install is not listed in the wizard, select
Other for both the operating system and version.
If you are installing an operating system that supports Easy Install but you do not want to use
Easy Install, you can instruct the wizard to create a virtual machine that has a blank disk and
install the guest operating system manually.
For the most recent list of guest operating systems that VMware products support, see the
VMware Compatibility Guide site: http://www.vmware.com/resources/compatibility/search.php.
Workstation Player is not listed, but the information for Workstation Pro is applicable to
Workstation Player. Operating systems that are not listed are not supported for use in a virtual
machine.
VMware, Inc. 30
Using VMware Workstation Player for Windows
For instructions about how to install the most common guest operating systems, see the VMware
Guest Operating System Installation Guide: http://partnerweb.vmware.com/GOSIG/home.html.
For Windows guest operating systems, you must provide the following Easy Install information.
Windows product key (Optional) Type a product key unless the installation media contains a volume
license product key. If you provide a product key here, you are not prompted to
provide a product key when you install the guest operating system.
Version of Windows to install Select the Windows operating system edition to install.
Full name The name to use to register the guest operating system. Do not use the name
Administrator or Guest. If you use one of these names, you must enter a
different name when you install the guest operating system.
Password (Optional) The password to use for an account with Administrator permissions
on Windows operating systems other than Windows 2000. On Windows 2000,
this is the password for the Administrator account. On Windows XP Home, an
Administrator account without a password is created and you are automatically
logged in to the guest operating system.
Log on automatically (requires a (Optional) Save your login credentials and bypass the login dialog box when you
password) power on the virtual machine. You must enter a name and password to use this
feature.
For Linux guest operating systems, you must provide the following Easy Install information.
Full name The name to use to register the guest operating system, if registration is
required. Workstation Player uses the first name to create the host name for
the virtual machine.
User name Your user name. You can use lowercase letters, numbers, and dashes, but avoid
using user names that begin with a dash. Do not use the name root. Some
operating systems set up sudo access for this user and other operating
systems require this user to use su to obtain root privileges.
Password The password for the User name and the root user.
VMware, Inc. 31
Using VMware Workstation Player for Windows
The name of the default directory for virtual machine files is derived from the name of the guest
operating system, for example, Microsoft Windows 10 x64.
For standard virtual machines, the default directory for virtual machine files is located in the
virtual machine directory. For best performance, do not place the virtual machines directory on a
network drive. If other users need to access the virtual machine, consider placing the virtual
machine files in a location that is accessible to those users.
For shared virtual machines, the default directory for virtual machine files is located in the shared
virtual machines directory. Shared virtual machine files must reside in the shared virtual machines
directory.
The default location of the virtual machines directory depends on the host operating system.
Linux homedir/vmware
homedir is the home directory of the currently logged in
logged in user.
A virtual disk is made up of one or more virtual disk files. Virtual disk files store the contents of
the virtual machine hard disk drive. Almost all of the file content is virtual machine data. A small
portion of the file is allotted to virtual machine overhead. If the virtual machine is connected
directly to a physical disk, the virtual disk file stores information about the partitions that the
virtual machine is allowed to access.
You can set a size between 0.001 GB and 8 TB for a virtual disk file. You can also select whether
to store a virtual disk as a single file or split it into multiple files.
VMware, Inc. 32
Using VMware Workstation Player for Windows
Select Split virtual disk into multiple files if the virtual disk is stored on a file system that has a
file size limitation. When you split a virtual disk less than 950 GB, a series of 2-GB virtual disk files
are created. When you split a virtual disk greater than 950 GB, two virtual disk files are created.
The maximum size of the first virtual disk file is 1.9 TB and the second virtual disk file stores the
rest of the data.
Disk space is not preallocated for the disk. The actual files that the virtual disk uses start small
and expand to their maximum size as needed. The main advantage of this approach is the smaller
file size. Smaller files require less disk space and are easier to move to a new location.
After you create a virtual machine, you can edit virtual disk settings and add additional virtual
disks.
Workstation Hardware Version Bus Type Controller Type Maximum Disk Size
To discover your SCSI controller type, open the virtual machine .vmx file. The value of the setting
scsi0.virtualDev determines your SCSI controller type.
You can change the default hardware settings, including memory allocation, number of virtual
CPUs, CD/DVD and floppy drive settings, and the network connection type.
VMware, Inc. 33
Using VMware Workstation Player for Windows
Disk capacity
Prerequisites
n Verify that you have the information the New Virtual Machine wizard requires to create a
virtual machine. See Preparing to Create a Virtual Machine.
n Verify that the guest operating system you plan to install is supported. See the online
VMware Compatibility Guide, which is available on the VMware Web site.
n See the VMware Guest Operating System Installation Guide for information about the guest
operating system you plan to install.
n If you are installing the guest operating system from an installer disc, insert the installer disc
in the CD-ROM drive in the host system.
n If you are installing the guest operating system from an ISO image file, verify that the ISO
image file is in a directory that is accessible to the host system.
Procedure
VMware, Inc. 34
Using VMware Workstation Player for Windows
Option Description
Use a physical disc Select the physical drive where you inserted the installation disc.
Use an ISO image Type or browse to the location of the ISO image file.
Install the guest operating system Create a virtual machine that has a blank disk. You must install the guest
later operating system manually after the virtual machine is created.
Option Description
You are using Easy Install Type the Easy Install information for the guest operating system.
You are not using Easy Install Select the guest operating system type and version. If the guest operating
system is not listed, select Other.
4 Type a virtual machine name and type or browse to the directory for the virtual machine files.
5 Select the virtual disk size and specify whether the disk should be split into multiple files.
You can also modify virtual hardware settings after you create the virtual machine.
7 (Optional) Select Power on this virtual machine after creation to power on the virtual
machine after it is created.
This option is not available if you are installing the guest operating system manually.
Results
If you are using Easy Install, guest operating system installation begins when the virtual machine
powers on. The guest operating system installation is automated and typically runs without
requiring any input from you. After the guest operating system is installed, Easy Install installs
VMware Tools.
If you are not using Easy Install, the virtual machine appears in the library.
What to do next
If you used Easy Install and the virtual machine did not power on when the installation finished,
power on the virtual machine to start the guest operating system installation. See Use Easy Install
to Install a Guest Operating System .
If you did not use Easy Install, install the guest operating system manually. See Install a Guest
Operating System Manually .
VMware, Inc. 35
Using VMware Workstation Player for Windows
If you did not provide all of the Easy Install information in the New Virtual Machine wizard, you
might be prompted for a product key, username, or password.
Also, if the guest operating system installation consists of multiple discs or ISO image files, the
installer might prompt you for the next disk.
Procedure
u If the installer prompts you for a product key, username, or password, click in the virtual
machine window and type the required information.
u If you are using physical discs and the installer prompts you for the next disk, use the CD-
ROM or DVD drive on the host system.
u If you are using multiple ISO image files and the installer prompts you for the next disk, select
the next ISO image file.
Option Description
Windows host Click Change Disk and browse to the next ISO image file.
Linux host a Select Virtual Machine > Removable Devices > CD/DVD > Settings and
browse to the next ISO image file.
b Select Connected.
c Click Save.
You can install a guest operating system from an installer disc or ISO image file. You can also use
a PXE server to install the guest operating system over a network connection. If the host
configuration does not permit the virtual machine to boot from an installer disc, you can create
an ISO image file from the installer disc.
Prerequisites
n Verify that the operating system is supported. See the online VMware Compatibility Guide on
the VMware Web site.
n See the VMware Guest Operating System Installation Guide for information on the guest
operating system that you are installing.
VMware, Inc. 36
Using VMware Workstation Player for Windows
Procedure
1 If you are installing the guest operating system from an installer disc, configure the virtual
machine to use a physical CD-ROM or DVD drive and configure the drive to connect at power
on.
a Select the virtual machine and select Player > Manage > Virtual Machine Settings.
2 If you are installing the guest operating system from an ISO image file, configure the CD/DVD
drive in the virtual machine to point to the ISO image file and configure the drive to connect
at power on.
a Select the virtual machine and select Player > Manage > Virtual Machine Settings.
d Select Use ISO image file and browse to the location of the ISO image file.
3 If you are installing the guest operating system from an installer disc, insert the disc in the CD-
ROM or DVD drive.
6 If the operating system consists of multiple installer discs and you are prompted to insert the
next disc, insert the next disc in the physical drive.
7 If the operating system consists of multiple ISO image files, select the image file for the next
CD.
a Select Player > Removable Devices > CD/DVD > Disconnect and disconnect from the
current ISO image file..
b Select Player > Removable Devices > CD/DVD > Settings and select the next ISO image
file.
8 Use the standard tools in the operating system to configure its settings.
What to do next
Install VMware Tools. You should install VMware Tools before you activate the license for the
operating system. See Installing VMware Tools.
VMware, Inc. 37
Using VMware Workstation Player for Windows
OVF is a platform-independent, efficient, extensible, and open packaging and distribution format
for virtual machines. For example, you can import OVF virtual machines exported from VMware
Fusion™ or Oracle VM VirtualBox into Workstation Player. You can import OVF 1.x files only.
You can also use the standalone OVF Tool to convert an OVF virtual machine to VMware runtime
format. The standalone version of the OVF Tool is installed in the Workstation Player installation
directory under OVFTool. See the OVF Tool User Guide on the VMware Web site for information
on using the OVF Tool.
Procedure
3 Type a name for the virtual machine, type or browse to the directory for the virtual machine
files, and click Import.
4 If the import fails, click Retry to try again, or click Cancel to cancel the import.
If you retry the import, Workstation Player relaxes the OVF specification conformance and
virtual hardware compliance checks and you might not be able to use the virtual machine in
Workstation Player.
Results
After Workstation Player successfully imports the OVF virtual machine, the virtual machine
appears in the virtual machine library.
Procedure
2 Browse to the vCenter Server Appliance .ovf or .ova file and click Open.
VMware, Inc. 38
Using VMware Workstation Player for Windows
4 Continue through the wizard, responding to prompts and clicking through to the next dialog
box.
5 If the import fails, click Retry to try again, or click Cancel to cancel the import.
If you retry the import, Workstation Player relaxes the OVF specification conformance and
virtual hardware compliance checks and you might not be able to use the virtual machine in
Workstation Player.
Results
After Workstation Player successfully imports the vCenter Server Appliance as a virtual machine,
the virtual machine appears in the virtual machine library. Workstation Player then powers on the
virtual machine and applies the vCenter Server Appliance configuration.
VMware, Inc. 39
Running Workstation on a Hyper-
V Enabled Host 5
The traditional implementation of Workstation Player relies on direct access to specific hardware
features of the x86 microprocessor.
These features, generally called Intel VT or AMD-V, are also used by recent versions of Windows
that support Hyper-V. Also, it is not possible to run traditional Workstation Player on a Windows
host with the Hyper-V capability enabled because some Windows features like the virtualization-
based security (or VBS), are built on top of Hyper-V. Therefore, a VBS-enabled Windows host is
also incompatible with traditional Workstation Player.
System Requirements
Processor Requirements for Host System
Note For all other Windows host versions, Hyper-V must be disabled for Workstation Player to
power on VMs.
VMware, Inc. 40
Using VMware Workstation Player for Windows
In the Host VBS Mode, Workstation Player uses a set of newly introduced Windows 10 features
(Windows Hypervisor Platform) that permits the use of VT/AMD-V features, which enables
Workstation Player and Hyper-V to coexist. And because VBS is built on Hyper-V, Windows
hosts with VBS enabled can now power on VM in Workstation Player successfully.
If Hyper-V is disabled, Workstation Player operates in its traditional mode. And if Hyper-V is
enabled, but the WHP feature is not sufficiently recent or not installed, Workstation Player fails to
start.
Note WHP is not supported on the Windows Server editions. Therefore, Workstation Player
host VBS mode is not available on these editions.
Depending on the workload, a Host VBS Mode VM can run slower when compared to a VM in
traditional mode. The limitations and use overhead introduced by the WHP feature set causes
these issues.
Here is a list of functional limitations of a Workstation Player VM running in Host VBS Mode:
x86 virtualization features (Intel VT / AMD-V) are unavailable to a guest running on a Host
VBS Mode VM. Therefore such VMs cannot themselves run Windows with Hyper-V or VBS
enabled.
Restricted transactional memory and hardware lock elision capabilities are not available.
VMware, Inc. 41
Using VMware Workstation Player for Windows
If features requested during the VM creation are unavailable on the host environment, the VM
resume operation fails. This ensures that a guest does not attempt to use unimplemented
features. Because some CPU features are not supported in Host VBS Mode, attempting to
resume suspended VMs or snapshots that were initially created on previous versions of
Workstation Player may fail.
For example, consider a physical PC that supports the RTM feature. A VM created with RTM
enabled, will power on with RTM available to it, when Workstation Player is running in traditional
mode. However, the same VM running on the same PC will power on with RTM disabled, if
Workstation Player is in Host VBS Mode. This is because, as previously listed in the functional
limitations list, Host VBS Mode does not support RTM.
Now consider a suspended VM which has a particular feature enabled is resumed some time
later. If the particular feature is not available on the host environment of the resumed VM, the
expected behavior is that the resume operation fails.
Note The resume operation can fail on the same physical hardware, when the VM is suspended
while operating in traditional mode and the resumed while in Host VBS Mode.
For example:
2 Start Workstation Player with Hyper-V disabled and power on the VM on a physical hardware
that supports RTM.
4 Enable Hyper-V. (The physical machine must be rebooted and Workstation Player must be
relaunched.)
Even though the physical hardware is the same, the resume operation fails because RTM is no
longer supported in Host VBS Mode.
Note If the VM is launched with Hyper-V enabled, the VM will not have the RTM capability, and
so the suspended image created will also be RTM-free. Regardless of whether Hyper-V is
disabled or left enabled, the resume VM operation will succeed.
VMware, Inc. 42
Installing and Upgrading VMware
Tools 6
Installing VMware Tools is part of the process of creating a new virtual machine. Upgrading
VMware Tools is part of the process of keeping virtual machines up to current standards.
For the best performance and latest updates, install or upgrade VMware Tools to match the
version of Workstation Player that you are using. Other compatibility options are also available.
For more information about using VMware Tools, see Installing and Configuring VMware Tools at
http://www.vmware.com/pdf/vmware-tools-installation-configuration.pdf.
n Starting the VMware User Process Manually If You Do Not Use a Session Manager
For information about creating virtual machines, see the documentation for the applicable
VMware product.
VMware, Inc. 43
Using VMware Workstation Player for Windows
The installers for VMware Tools are ISO image files. The CD-ROM in your guest operating system
detects the ISO image file. Each type of guest operating system, including Windows, Linux, and
Mac OS X, has an ISO image file. When you select the command to install or upgrade VMware
Tools, the virtual machine’s first virtual CD-ROM disk drive temporarily connects to the VMware
Tools ISO file for your guest operating system.
You can use the Windows Easy Install or Linux Easy Install feature to install VMware Tools as
soon as the operating system is finished installing.
The most recent versions of the ISO files are stored on a VMware Web site. When you select the
command to install or upgrade VMware Tools, the VMware product determines whether it has
downloaded the most recent version of the ISO file for the specific operating system. If the latest
version has not been downloaded or if no VMware Tools ISO file for that operating system has
ever been downloaded, you are prompted to download the file.
n VMware Tools installer from windows.iso automatically detects the windows version. It does
not proceed with the installation on guest operating systems earlier than Windows Vista.
n VMware Tools installer from winPreVista.iso does not proceed with the installation on
Windows Vista and later.
n VMware Tools installer from linux.iso does not proceed with installation on Linux guest
operating system versions earlier than RHEL5, SLES 11, Ubuntu 10.04, and other Linux
distributions with glibc version earlier than 2.5.
n VMware Tools installer from darwinPre15.iso does not proceed with installation on MAC OS
X guest operating systems versions 10.11 or later.
n VMware Tools installer from darwin.iso does not proceed with installation on MAC OS X
guest operating systems versions earlier than 10.11.
The installation procedure varies, depending on the operating system. For information about
installing or upgrading VMware Tools on your guest operating systems, see the topic about
upgrading virtual machines in the Virtual Machine Administration Guide. For general instructions
about installing VMware Tools, see the VMware Knowledge base article http://
kb.vmware.com/kb/1014294.
The guest operating system checks the version of VMware Tools when you power on a virtual
machine. The status bar of your virtual machine displays a message when a new version is
available.
VMware, Inc. 44
Using VMware Workstation Player for Windows
In Windows virtual machines, you can set VMware Tools to notify you when an upgrade is
available. If this notification option is enabled, the VMware Tools icon in the Windows taskbar
includes a yellow caution icon when a VMware Tools upgrade is available.
To install a VMware Tools upgrade, you can use the same procedure that you used for installing
VMware Tools the first time. Upgrading VMware Tools means installing a new version.
For Windows and Linux guest operating systems, you can configure the virtual machine to
automatically upgrade VMware Tools. Although the version check is performed when you power
on the virtual machine, on Windows guest operating systems, the automatic upgrade occurs
when you power off or restart the virtual machine. The status bar displays the message
Installing VMware Tools ... when an upgrade is in progress. The procedure is mentioned
below.
Note Upgrading VMware Tools on Windows guest operation systems automatically installs the
WDDM graphics drivers. The WDDM graphics driver allows the sleep mode available in guest OS
power settings to adjust the sleep options. For example, you can use the sleep mode setting
Change when the computer sleeps to configure your guest OS to automatically go to sleep
mode after a certain time or prevent your guest OS from automatically switching to sleep mode
after being idle for some time.
Procedure
VMware, Inc. 45
Using VMware Workstation Player for Windows
You can select one, both, or neither option. If you deselect all of the software update options,
automatic software updates are disabled.
Option Description
Check for product updates on Checks for new versions of Workstation Player available to download and
startup install when you start Workstation Player. This option is enabled by default.
If you do not select this option, your system does not get the latest product
updates.
Check for software components as When a software component is required, for example, when you install
needed VMware Tools, Workstation Player checks for a new version of the
component.
Download All Components Now Immediately download all of the available software components to the host
system. This option is useful if you are planning to use the virtual machine at
a later time when you do not have access to the Internet.
3 If you use a proxy server to connect to the VMware Update Server, click Connection Settings
to configure the proxy settings.
Option Description
No proxy Select this option if you do not use a proxy server. This is the default setting.
Windows proxy settings Workstation Player uses the host proxy settings from the Connections tab in
the Internet Options control panel to access the VMware Update Server.
a Click Internet Options to set the guest connection options.
b Type a user name and password to use for proxy server authentication.
If you leave either the Username or the Password text box blank,
Workstation Player does not use either value.
Manual proxy settings a Select HTTP or SOCKS, specify the proxy server address and designate
a port number to access the VMware Update Sever.
b Type a username and password to use for proxy authentication.
If you leave either the Username or the Password text box blank,
Workstation Player does not use either value (Windows hosts) or it uses the
username and password set in the gnome settings (Linux hosts).
VMware, Inc. 46
Using VMware Workstation Player for Windows
Automatic VMware Tools updates are supported for versions of VMware Tools included in
Workstation 5.5 and later virtual machines only. Automatic updates are not supported for
versions of VMware Tools included in virtual machines created with VMware Server 1.x.
Important If you update VMware Tools in a Windows virtual machine that was created with
Workstation 4 or 5.x, some new components are not installed. To install the new components,
you must uninstall the old version of VMware Tools and install the new version of VMware Tools.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
Update manually (do nothing) You must update VMware Tools manually. The virtual machine status bar
indicates when a new version of VMware Tools is available.
Update automatically VMware Tools is updated automatically. The virtual machine status bar
indicates when an update is in progress. If you are logged in to a Windows
guest, a restart prompt appears after the update is complete. If you are not
logged in, the operating system restarts without prompting. An auto-update
check is performed as part of the boot sequence when you power on the
virtual machine. If the virtual machine was suspended and you resume it or
restore it to a snapshot during the boot sequence before this check, the
automatic update occurs as planned. If you resume the virtual machine or
restore it to a snapshot after the check, the automatic update does not
occur.
Use application default (currently Use the default VMware Tools update behavior. The default behavior is set
update manually) in Workstation Player preferences.
If you are installing VMware Tools in a number of Windows virtual machines, you can automate
its installation by using the VMware Tools setup.exe at a command prompt in the guest
operating system. See Installing and Configuring VMware Tools at http://www.vmware.com/pdf/
vmware-tools-installation-configuration.pdffor more information.
VMware, Inc. 47
Using VMware Workstation Player for Windows
Prerequisites
n If you connected the virtual machine’s virtual CD/DVD drive to an ISO image file when you
installed the operating system, change the setting so that the virtual CD/DVD drive is
configured to autodetect a physical drive.
The autodetect setting enables the virtual machine's first virtual CD/DVD drive to detect and
connect to the VMware Tools ISO file for a VMware Tools installation. This ISO file is detected
as a physical CD by your guest operating system. Use the virtual machine settings editor to
set the CD/DVD drive to autodetect a physical drive.
n Log in as an administrator unless you are using an older Windows operating system. Any user
can install VMware Tools in a Windows 95, Windows 98, or Windows ME guest operating
system. For operating systems later than these, you must log in as an administrator.
n The AppDefense component is not installed by default. You must perform a custom
installation and include that component.
Procedure
1 On the host, from the Workstation Player menu bar, select Player > Manage > Install VMware
Tools.
If an earlier version of VMware Tools is installed, the menu item is Update VMware Tools.
2 If you are installing VMware Tools for the first time, click OK on the Install VMware Tools
information page.
If autorun is enabled for the CD-ROM drive on the guest operating system, the VMware Tools
installation wizard starts.
If autorun is not enabled, to manually launch the wizard, click Start > Run and enter
D:\setup.exe, where D: is your first virtual CD-ROM drive. Use D:\setup64.exe for 64-bit
Windows guest operating system.
4 If the New Hardware wizard appears, follow the prompts and accept the defaults.
Note If you are installing a beta or RC version of VMware Tools and you see a warning that a
package or driver is not signed, click Install Anyway to complete the installation.
Results
VMware, Inc. 48
Using VMware Workstation Player for Windows
What to do next
If a new virtual hardware version is available for the virtual machine, upgrade the virtual
hardware.
For more information about Linux distributions supported by Open VM Tools, see https://
github.com/vmware/open-vm-tools/blob/master/README.md and the VMware Compatibility
Guide at https://www.vmware.com/resources/compatibility/search.php.
VMware Tar Tool for Linux virtual machine is feature-frozen at version 10.3.10, so the tar tools
(linux.iso) included in Workstation Player is 10.3.10 and will not be updated. Due to this change,
the Install/Update/Reinstall VMware Tools menu is disabled for the following Linux virtual
machines:
n Linux kernel version is 4.0 or later, and the version of the installed Open VM Tools is 10.0.0 or
later.
n Linux kernel version is 3.10 or later, and the version of the installed Open VM Tools is 10.3.0 or
later.
For the Linux virtual machines that have Open VM Tools installed but are not in the scope
mentioned in the preceding bullet, Install/Update/Reinstall VMware Tools menu is enabled, so
that you can install bundled tar tools on top of Open VM Tools to get Shared Folder (HGFS)
feature support.
For old Linux virtual machines not supported by Open VM Tools, perform the following steps to
install tar tools.
Prerequisites
n Because the VMware Tools installer is written in Perl, verify that Perl is installed in the guest
operating system.
VMware, Inc. 49
Using VMware Workstation Player for Windows
Procedure
1 On the host, from the Workstation Player menu bar, select Player > Manage > Install VMware
Tools.
If an earlier version of VMware Tools is installed, the menu item is Update VMware Tools.
3 Run the mount command with no arguments to determine whether your Linux distribution
automatically mounted the VMware Tools virtual CD-ROM image.
If the CD-ROM device is mounted, the CD-ROM device and its mount point are listed in a
manner similar to the following output:
4 If the VMware Tools virtual CD-ROM image is not mounted, mount the CD-ROM drive.
mkdir /mnt/cdrom
Some Linux distributions use different mount point names. For example, on some
distributions the mount point is /media/VMware Tools rather than /mnt/cdrom. Modify the
command to reflect the conventions that your distribution uses.
Some Linux distributions use different device names or organize the /dev directory
differently. If your CD-ROM drive is not /dev/cdrom or if the mount point for a CD-ROM is
not /mnt/cdrom, modify the command to reflect the conventions that your distribution
uses.
cd /tmp
6 (Optional) Delete any previous vmware-tools-distrib directory before you install VMware
Tools.
The location of this directory depends on where you placed it during the previous installation.
Often this directory is placed in /tmp/vmware-tools-distrib.
7 List the contents of the mount point directory and note the file name of the VMware Tools tar
installer.
ls mount-point
VMware, Inc. 50
Using VMware Workstation Player for Windows
The value x.x.x is the product version number, and yyyy is the build number of the product
release.
umount /dev/cdrom
If your Linux distribution automatically mounted the CD-ROM, you do not need to unmount
the image.
cd vmware-tools-distrib
sudo ./vmware-install.pl
Usually, the vmware-config-tools.pl configuration file runs after the installer file finishes
running. If you attempt to install a tar installation over an RPM installation, or the reverse, the
installer detects the previous installation and must convert the installer database format
before continuing.
Note For newer Linux distributions, users are prompted to choose the integrated open-vm-
tools.
11 Follow the prompts to accept the default values, if appropriate for your configuration.
Depending on the features you use, these instructions can include restarting the X session,
restarting networking, logging in again, and starting the VMware User process. You can
alternatively reboot the guest operating system to accomplish all these tasks.
What to do next
If a new virtual hardware version is available for the virtual machine, upgrade the virtual
hardware.
Prerequisites
VMware, Inc. 51
Using VMware Workstation Player for Windows
n Because the VMware Tools installer is written in Perl, verify that Perl is installed in the guest
operating system.
Note VMware Tools 10.1.0 does not support the NetWare operating system.
Procedure
1 On the host, from the Workstation Player menu bar, select Player > Manage > Install VMware
Tools.
If an earlier version of VMware Tools is installed, the menu item is Update VMware Tools.
2 Load the CD-ROM driver so that the virtual CD-ROM device mounts the ISO image as a
volume.
When the installation finishes, the message VMware Tools for NetWare are now running
appears in the Logger Screen for NetWare 6.5 and NetWare 6.0 guest operating systems
and in the Console Screen for NetWare 4.2 and 5.1 operating systems.
3 If the VMware Tools virtual disc (netware.iso) is attached to the virtual machine, right-click
the CD-ROM icon in the status bar of the console window and select Disconnect.
What to do next
If a new virtual hardware version is available for the virtual machine, upgrade the virtual
hardware.
Prerequisites
n Because the VMware Tools installer is written in Perl, verify that Perl is installed in the guest
operating system.
VMware, Inc. 52
Using VMware Workstation Player for Windows
Procedure
1 On the host, from the Workstation Player menu bar, select Player > Manage > Install VMware
Tools.
If an earlier version of VMware Tools is installed, the menu item is Update VMware Tools.
2 In the virtual machine, log in to the guest operating system as root and open a terminal
window.
3 If the Solaris volume manager does not mount the CD-ROM under /cdrom/vmwaretools,
restart the volume manager.
/etc/init.d/volmgt stop
/etc/init.d/volmgt start
cd /tmp
cd vmware-tools-distrib
./vmware-install.pl
Usually, the vmware-config-tools.pl configuration file runs after the installer file finishes
running.
7 Follow the prompts to accept the default values, if appropriate for your configuration.
Depending on the features you use, these instructions can include restarting the X session,
restarting networking, logging in again, and starting the VMware User process. You can
alternatively reboot the guest operating system to accomplish all these tasks.
Results
What to do next
If a new virtual hardware version is available for the virtual machine, upgrade the virtual
hardware.
VMware, Inc. 53
Using VMware Workstation Player for Windows
Prerequisites
n Because the VMware Tools installer is written in Perl, verify that Perl is installed in the guest
operating system.
Procedure
1 On the host, from the Workstation Player menu bar, select Player > Manage > Install VMware
Tools.
If an earlier version of VMware Tools is installed, the menu item is Update VMware Tools.
2 In the virtual machine, log in to the guest operating system as root and open a terminal
window.
3 If the distribution does not automatically mount CD-ROMs, mount the VMware Tools virtual
CD-ROM image.
cd /tmp
6 If the distribution does not use automounting, unmount the VMware Tools virtual CD-ROM
image.
umount /cdrom
cd vmware-tools-distrib
./vmware-install.pl
Usually, the vmware-config-tools.pl configuration file runs after the installer file finishes
running.
8 Follow the prompts to accept the default values, if appropriate for your configuration.
Depending on the features you use, these instructions can include restarting the X session,
restarting networking, logging in again, and starting the VMware User process. You can
alternatively reboot the guest operating system to accomplish all these tasks.
Results
VMware, Inc. 54
Using VMware Workstation Player for Windows
What to do next
If a new virtual hardware version is available for the virtual machine, upgrade the virtual
hardware.
Normally, this process starts after you configure VMware Tools, log out of the desktop
environment, and log back in. You can invoke the VMware user process by running the vmtoolsd
-n vmusr command. The startup script that you need to modify depends on your system. You
must start the process manually in the following environments:
n If you run an X session without a session manager. For example, if you use startx to start a
desktop session and do not use xdm, kdm, or gdm.
n If you are using a session manager or environment that does not support the Desktop
Application Autostart Specification, available from http://standards.freedesktop.org.
Procedure
Option Action
Start the VMware User process Add vmtoolsd -n vmusr to the appropriate X startup script, such as
when you start an X session. the .xsession or .xinitrc file.
Start the process after a VMware Open a terminal window and type the vmtoolsd -n vmusr command.
Tools software upgrade, or if certain
features are not working.
Prerequisites
VMware, Inc. 55
Using VMware Workstation Player for Windows
Procedure
Windows 7, 8, 8.1, or Windows 10 In the guest operating system, select Programs > Uninstall a program.
Windows Vista and Windows Server In the guest operating system, select Programs and Features > Uninstall a
2008 program.
Windows XP and earlier In the guest operating system, select Add/Remove Programs.
Mac OS X, OS X, or macOS Use the Uninstall VMware Tools application, found in /Library/
Application Support/VMware Tools.
What to do next
VMware, Inc. 56
Starting and Stopping Virtual
Machines in Workstation Player 7
You can use Workstation Player to start and stop virtual machines on the host system.
When you start a virtual machine, the guest operating system starts and you can interact with
the virtual machine. You can power off, reset, and suspend virtual machines.
Prerequisites
Verify that the virtual machine files are accessible to the host system.
Procedure
1 If the virtual machine does not appear in the library, select Player > File > Open.
2 Browse to and select the virtual machine configuration (.vmx) file, and click Open.
VMware, Inc. 57
Using VMware Workstation Player for Windows
3 Select the virtual machine in the library and select Player > Power > Power On.
4 Click anywhere inside the virtual machine console to give the virtual machine control of the
mouse and keyboard on the host system.
Note You cannot create encrypted virtual machines in Workstation Player. You can only create
encrypted virtual machines using VMware Workstation 7.x and later or VMware Fusion 7.x and
later.
Prerequisites
Procedure
1 Select the virtual machine in the library and select Player > Power > Power On.
Procedure
Results
A Web browser opens to the Virtual Appliance Marketplace page on the VMware Web site. You
can browse to and download virtual appliances from this page.
VMware, Inc. 58
Using VMware Workstation Player for Windows
Procedure
u To shut down the guest operating system, shut down the operating system as you would if
you were using a physical machine.
When the guest operating system shuts down, the virtual machine is powered off and
Workstation Player exits.
u To power off a virtual machine without shutting down the guest operating system, select
Player > Power > Power Off.
If soft power operations are configured for the virtual machine when the virtual machine is
first created, Power Off Guest appears in the menu instead of Power Off.
Removing a virtual machine from the library does not delete the virtual machine or any of its files
from the host file system. The virtual machine is removed only from the library. If you open the
virtual machine again, the virtual machine is added back to the library.
Prerequisites
Procedure
u Select the virtual machine, right-click, and select Remove VM from the Library.
Results
The virtual machine is removed from the library without any confirmation.
Prerequisites
Procedure
u Select the virtual machine and select Player > Send Ctrl+Alt+Delete.
This option is the same as pressing Ctrl+Alt+Delete on your keyboard. On Windows hosts,
using the physical keyboard to press Ctrl+Alt+Delete might send the command to the host
operating system and the virtual machine, even when Workstation Player has control of input.
VMware, Inc. 59
Using VMware Workstation Player for Windows
u If the command is received by both the host operating system and the virtual machine, press
Ctrl+Alt+Ins on the keyboard.
The command is received solely by the virtual machine and shuts down or logs out of the
guest operating system.
How quickly the suspend and resume operations perform depends on how much data changed
after you started the virtual machine. The first suspend typically takes longer than subsequent
suspend operations.
Procedure
u To suspend a virtual machine, select Player > Power > Suspend and click Yes to confirm.
If soft power operations are configured for the virtual machine when the virtual machine is
first created, Suspend Guest appears in the menu instead of Suspend.
Workstation Player returns the virtual machine to the library in the Suspended state.
u To resume a suspended virtual machine, select the virtual machine and select Player > Power
> Power On.
u To set the Workstation Player preferences to suspend the virtual machine when you close
the virtual machine window, select Player > File > Preferences and then select Suspend the
virtual machine.
Prerequisites
n Verify that the virtual machine is in a safe state. Resetting a virtual machine can damage data.
When possible, shut down the virtual machine with its operating system.
Procedure
If soft power operations are configured for the virtual machine in Workstation Player, Reset
Guest appears in the menu instead of Reset.
VMware, Inc. 60
Using VMware Workstation Player for Windows
Use the Autologon feature if you restart the guest operating system frequently and want to
avoid entering your login credentials. You can also use the Autologon feature to grant users
access to the guest operating system without sharing your password.
Prerequisites
n Verify that you have an existing user account to enable Autologon. The account must be a
local machine account, not a domain account.
n Verify that the latest version of VMware Tools is running in the guest operating system.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
If you type an incorrect or expired password, you must type your login credentials when you
power on the virtual machine.
When you enable Autologon or change your login credentials, the Autologon settings are
saved immediately. Clicking Cancel in the Virtual Machine Settings dialog box does not affect
the changes applied to the Autologon settings.
Procedure
VMware, Inc. 61
Using VMware Workstation Player for Windows
2 Select how Workstation Player behaves when you close a virtual machine.
Option Description
Confirm before closing a virtual Confirm whether you intend to exit Workstation Player or click Cancel to
machine continue using Workstation Player
Return to the VM Library after Workstation Player either suspends or powers off the virtual machine and
closing a virtual machine returns it to the virtual machine library. From the library, you can either open
another virtual machine or edit the virtual machine settings.
3 Select whether Workstation Player suspends or powers off a virtual machine when you close
it.
Option Description
Suspend the virtual machine Workstation Player suspends the virtual machine. The next time you start
Workstation Player, the virtual machine resumes operation from the point
where it was suspended.
Power off the virtual machine Workstation Player powers off the virtual machine. The next time you start
Workstation Player, the virtual machine starts from a powered-off state and
the guest operating system starts.
VMware, Inc. 62
Changing the Virtual Machine
Display 8
You can change the way Workstation Player displays virtual machines and virtual machine
applications. You can use full screen mode to make the virtual machine display fill the screen and
use multiple monitors.
You can also use Unity mode to display applications directly on the host system desktop.
For Windows guests, to use DirectX 9 accelerated graphics, the guest operating system must be
Windows XP or later. To use DirectX 10 accelerated graphics, the guest operating system must
be Windows Vista or later. To use DirectX 10.1 or DirectX 11 accelerated graphics, the guest
operating system must be Windows 7 or later.
Prerequisites
n Verify that the latest version of VMware Tools is installed in the guest operating system.
n Verify that the guest operating system in the virtual machine is Windows XP or later, or Linux.
n If you plan to use DirectX 9, DirectX 10, DirectX 10.1, or DirectX 11 accelerated graphics,
prepare the host system. See Prepare the Host System to Use 3D Accelerated Graphics.
n If the guest operating system is Windows 7 or later and you want Workstation Player to
automatically adjust the virtual machine user interface size, update VMware Tools in the
guest to the newest version.
VMware, Inc. 63
Using VMware Workstation Player for Windows
n If you are using Windows 8.1 (Update 2) or Windows 10, Workstation Player detects the DPI
on each monitor and scales the virtual machine to match the DPI on the host.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
3 (Optional) To run applications that use DirectX 9, DirectX 10, DirectX 10.1 or DirectX 11
accelerated graphics, select Accelerate 3D graphics.
Option Description
Use host setting for monitors When you select this setting, the SVGA driver uses a maximum bounding
box width of 7680 and a maximum bounding box height of 4320. The virtual
machine uses the number of monitors on the host system. The guest
monitors cannot exceed the maximum bounding box that the SVGA driver
uses, 7680x4320. You should select this setting in most cases.
Specify monitor settings Set the number of monitors that the virtual machine will see, regardless of
the number of monitors on the host system. This setting is useful if you use a
multimonitor host system and you need to test in a virtual machine that has
only one monitor. It is also useful if you are developing a multimonitor
application in a virtual machine and the host system has only one monitor.
After you power on the virtual machine, the guest operating system sees
the number of monitors that you specified. Select a resolution from the list
or type a setting that has the format width x height, where width and height
are the number of pixels.
5 (Optional) Select the maximum amount of guest memory that can be used for graphics
memory using the drop-down menu. The default value of video memory varies by guest OS.
Note If you manually edited the .vmx file to change the memory size for the virtual machine,
the value you entered in the .vmx file is displayed, labeled Custom.
6 To enable display scaling for a virtual machine with a Windows 7 or later guest, select
Automatically adjust user interface size in the virtual machine.
VMware, Inc. 64
Using VMware Workstation Player for Windows
Prerequisites
n Verify that the guest operating system display mode is larger than the host system display
mode. If the guest operating system display mode is smaller than the host system display
mode, you might not be able to enter full screen mode. If you cannot enter full screen mode,
add the line mks.maxRefreshRate=1000 to the virtual machine configuration (.vmx) file.
n Verify that the latest version of VMware Tools is installed in the guest operating system.
n If you are running the virtual machine in full screen mode on a laptop, configure the guest
operating system to report battery information. See Report Battery Information in the Guest.
Procedure
u To enter full screen mode, select the virtual machine and select Player > Full Screen.
u To hide the full screen toolbar and menus while you are using full screen mode, click the push
pin icon and move the pointer off of the toolbar.
This action unpins the toolbar. The toolbar slides up to the top of the monitor and disappears.
To display the toolbar again, point to the top of the screen until the toolbar appears.
u To exit full screen mode and return to windowed mode, select Player > Full Screen from the
full screen toolbar. The check mark next to Full Screen is removed.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
VMware, Inc. 65
Using VMware Workstation Player for Windows
In Unity mode, virtual machine applications appear on the host system desktop, you can use the
virtual machine Start or Applications menu from the host system, and the virtual machine
console view is hidden. Items for open virtual machine applications appear on the host system
taskbar in the same way as open host applications.
On host system and virtual machine applications that are displayed in Unity mode, you can use
keyboard shortcuts to copy, cut, and paste images, plain text, formatted text, and email
attachments between applications. You can also drag and drop and copy and paste files
between the host system and the guest operating system.
If you save a file or attempt to open a file from an application in Unity mode, the file system you
see is the file system inside the virtual machine. You cannot open a file from the host operating
system or save a file to the host operating system.
For some guest operating systems, application windows in Unity mode can appear only on the
monitor that is set as the primary display when you have multiple monitors. If the host and guest
operating systems are Windows XP or later, the application windows can appear on additional
monitors.
Prerequisites
n Verify that the latest version of VMware Tools is installed in the guest operating system.
n If you are entering Unity mode, open applications in the virtual machine to use in Unity mode.
Procedure
The console view in the Workstation Player window is hidden, and open applications appear
in application windows on the host system desktop. A check mark appears next to Unity in
the menu.
u To display the virtual machine Start menu on a Windows host system, point to the Start
menu on a Windows host system.
u To navigate between multiple Start or Applications menus when multiple virtual machines
are in Unity mode, press the arrow keys, Tab, or Shift+Tab to cycle through the virtual
machine menus and press Enter and the spacebar to select a virtual machine.
u To exit Unity mode, display the Workstation Player window and click Exit Unity in the virtual
machine console view.
VMware, Inc. 66
Using VMware Workstation Player for Windows
When you use the virtual machine Start or Applications menu from the host system desktop,
you can start applications in the virtual machine that are not open in Unity mode. If you do not
enable this feature, you must exit Unity mode to display the virtual machine Start or Applications
menu in the console view.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
Show borders Set a window border that identifies the application as belonging to the
virtual machine rather than to the host computer.
Use a custom color in window To help distinguish between the application windows that belong to various
borders virtual machines, use a custom color in window borders. For example, you
can set the applications for one virtual machine to have a blue border and
set the applications for another virtual machine to have a yellow border. On
Windows hosts, click Choose color to use the color chooser.
4 To control whether the virtual machine Start or Applications menu is available on the host
system desktop, select or deselect Enable applications menu.
You open the application in the same way that you open an application on the host system. You
can open a virtual machine application shortcut from the host system even when the virtual
machine is powered off or suspended.
Prerequisites
n Verify that the virtual machine is configured to display the virtual machine Start or
Application menu on the host system desktop. See Set Preferences for Unity Mode.
n Verify that the latest version of VMware Tools is running in the guest operating system.
VMware, Inc. 67
Using VMware Workstation Player for Windows
Procedure
The console view in the Workstation Player window is hidden, and open applications appear
in application windows on the host system desktop. A check mark appears next to Unity in
the menu.
2 Point to the Start button to display the virtual machine Start menu on the host system
desktop, click the Start menu, and select the application.
3 Right-click the application and select Create Shortcut on Desktop, or drag the application to
the host system.
Prerequisites
n Configure multiple monitors for one virtual machine. See Configure Display Settings for a
Virtual Machine.
n Verify that the latest version of VMware Tools is installed in the guest operating system.
n Verify that the guest operating system is Windows XP, Windows Vista, Windows 7, Windows
8, Windows 8.1, Windows 10, or Linux.
n On the host system, verify that the left-most monitor is not placed lower than any other
monitor in the display topology. When you enter full screen mode, the monitor that contains
the window cannot be lower than another monitor.
Procedure
2 On the full screen toolbar, click the Cycle multiple monitors button.
On a Windows host, you can mouse over a button on the toolbar to see its name.
If your virtual machine supports more than two monitors, use the Cycle multiple monitors
button to select a configuration with more than two monitors. The monitor in which the virtual
machine entered full screen mode is marked with an asterisk.
The guest operating system desktop extends to the additional monitor or monitors.
VMware, Inc. 68
Using VMware Workstation Player for Windows
3 If the host system has more than two monitors and you want the virtual machine to use all of
the monitors, click the Cycle multiple monitors button again.
The order in which the monitors are used depends on the order in which the monitors were
added to the host operating system. If you continue to click the button, you return to fewer
monitors.
n If you attempt to use more than two monitors with a virtual machine, your virtual machine
must support more than two monitors for this feature to function.
n More than two monitors is supported on Windows and Linux host and guest operating
systems.
n Windows XP guests support more than three monitors. However, only three monitors can be
in use by a Windows XP guest at one time. If more than three monitors are connected to a
Windows XP guest, use the Cycle multiple monitors button to cycle through the monitors to
the configuration you want to use.
VMware, Inc. 69
Using Removable Devices and
Printers in Virtual Machines 9
You can connect and disconnect removable devices in a virtual machine. You can also print from
a virtual machine to any printer available to the host computer without having to install additional
drivers in the virtual machine.
Prerequisites
n If you are connecting or disconnecting a USB device, familiarize yourself with the way
Workstation Player handles USB devices. See Connecting USB Devices to Virtual Machines.
Procedure
u To connect a removable device, select the virtual machine, select Player > Removable
Devices, select the device, and select Connect.
If the device is connected to the host system through a USB hub, the virtual machine sees
only the USB device, not the hub.
A check mark appears next to the name of the device when the device is connected to the
virtual machine and a device icon appears on the virtual machine taskbar.
u To change the settings for a removable device, select Player > Removable Devices, select
the device, and select Settings.
VMware, Inc. 70
Using VMware Workstation Player for Windows
u To disconnect a removable device, select the virtual machine, select Player > Removable
Devices, select the device, and select Disconnect.
You can also disconnect the device by clicking or right-clicking the device icon on the virtual
machine taskbar. Using the taskbar icon is especially useful if you run the virtual machine in
full screen mode.
If Workstation Player cannot reconnect to the device, for example, because you disconnected
the device, the device is removed and Workstation Player displays a message to indicate that it
cannot connect to the device. If the device is still available, you can connect to it manually. To
connect a USB device to the virtual machine manually, select Player > Removable Devices >
Device Name > Connect (Disconnect from host).
Follow the device manufacturer's procedures for unplugging the device from the host computer
when you physically unplug the device, move the device from the host system to a virtual
machine, or move the device from a virtual machine to the host computer. Following these
procedures is especially important for data storage devices, such as zip drives. If you move a
data storage device too soon after saving a file and the operating system did not actually write
the data to the disk, you can lose data.
The Windows operating system prompts you to run the Microsoft Windows Found New
Hardware wizard. Select the default action to install the software automatically. After the
software is installed, the guest operating system detects the USB device and searches for a
suitable driver.
The default setting for the USB Connections setting is Ask me what to do. You can change the
setting to suit your needs.
VMware, Inc. 71
Using VMware Workstation Player for Windows
Procedure
n Ask me what to do
Results
Selected Option Result When You Plug a New USB Device into the Host
Ask me what to do If Workstation Player is open and one or more virtual machines is powered on, a dialog box
appears that prompts you to choose which machine to connect the device to. You can choose
the host or one of the powered-on virtual machines.
Connect the device Workstation Player always connects new USB devices to the host machine regardless of whether
to the host a virtual machine is running.
Connect the device If Workstation Player is open and one or more virtual machines is powered on, Workstation
to the foreground Player connects the device to the powered-on virtual machine in the foreground.
virtual machine
What to do next
Plug a USB device into the Windows host machine. If the Ask me what to do option is configured,
when you plug in a device, you must respond to the New USB Device Detected dialog box. See
Select the Machine a USB Device Connects To. Access the USB device from the machine you
selected.
You can manually connect a USB device to the virtual machine by selecting Player > Removable
Devices > Device Name > Connect (Disconnect from host)
A USB device is treated as new when Workstation Player does not have a remembered
connection rule for the USB device. A connection rule is remembered when you select
Remember my choice and do not ask again, and stays remembered until you configure
Workstation Player to forget the rule.
Prerequisites
1 Set the USB Connections setting to Ask me what to do. See Configure USB Device
Connection Behavior.
VMware, Inc. 72
Using VMware Workstation Player for Windows
Procedure
Option Description
Connect to a virtual machine The device connects to the powered-on virtual machine of your choice.
Select a virtual machine in the list.
2 (Optional) If you want Workstation Player to remember your machine selection, select
Remember my choice and do not ask again.
This option creates a connection rule between the specific USB device and the specific
machine.
3 Click OK.
Results
Workstation Player connects the USB device to the machine you selected. If you selected
Remember my choice and do not ask again, in the future, when you connect the USB device to
the Windows host machine, Workstation Player implements the connection rule and connects the
device to the machine you configured without prompting. However, if the target virtual machine
of the connection rule is powered off or deleted at the time the device is plugged into the host,
the USB device automatically connects to the host. Anytime in the future, you can delete the
connection rule. After which, Workstation Player treats the USB device as new again. See Delete
the Connection Rule for a Specific USB Device.
What to do next
Selecting Remember my choice and do not ask again in the New USB Device Detected dialog
box creates a connection rule. See Select the Machine a USB Device Connects To. If you no
longer want a specified USB device to connect to a specified machine, delete the connection rule
by configuring Workstation Player to forget the rule.
Procedure
n Select the virtual machine and select Player > Removable Devices > Device Name >
Forget Connection Rule.
n Right-click the icon of the USB device in the Workstation Player status bar and select
Forget Connection Rule.
VMware, Inc. 73
Using VMware Workstation Player for Windows
Results
Workstation Player is no longer configured to remember the rule. When you plug a USB device
into the Windows host, the device no longer automatically connects to the virtual machine.
Instead, the New USB Device Detected dialog box appears.
By default, USB HIDs, such as USB 1.1 and 2.0 mouse and keyboard devices, do not appear in the
Removable Devices menu in a virtual machine, even though they are plugged in to USB ports on
the host system.
An HID that is connected to a virtual machine is not available to the host system.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
This option allows users to use special USB HIDs inside the virtual machine.
Procedure
1 Connect the PDA to the host system and synchronize it with the host system.
VMware, Inc. 74
Using VMware Workstation Player for Windows
4 If the PDA disconnects from the host system before the virtual machine can synchronize with
it, synchronize the PDA with the host system again.
The total time required to load the VMware USB device driver in the host system and install
the PDA driver in the virtual machine might exceed the device connection timeout value. A
second synchronization attempt usually succeeds.
When you connect a device to a virtual machine, it is disconnected from the host system or from
the virtual machine that previously had control of the device. When you disconnect a device from
a virtual machine, it is returned to the host system.
Under some circumstances, if a USB storage device is in use on the host system, for example,
one or more files stored on the device are open on the host, an error appears in the virtual
machine when you try to connect to the device. You must let the host system complete its
operation or close any application connected to the device on the host system and connect to
the device in the virtual machine again.
Starting with version 15 of Workstation Player, the version of VMware Tools downloaded from
the VMware software update server no longer delivers VMware Virtual Printer functionality. You
must install the VMware Virtual Printer application separately in the guest operating system to
make the printers on the host visible in the virtual machine.
Before you install VMware Virtual Printer on a virtual machine, you must add a virtual printer
device to the virtual machine.
Prerequisites
VMware, Inc. 75
Using VMware Workstation Player for Windows
n The virtual machine must be powered on or off. You cannot add a printer to a virtual machine
in a powered on or suspended state.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
The default device setting is to connect the virtual machine printer when the virtual machine
is powered on.
What to do next
Install the VMware Virtual Printer application in the virtual machine. See Install VMware Virtual
Printer
The VMware Virtual Printer application is packaged as an image that you can mount in the
CD/DVD drive of the guest operating system for installation.
Prerequisites
To install VMware Virtual Printer application in the guest operating system, perform the following
prerequisites.
n Upgrade to or install VMware Tools 10.3.x or later, if not already installed. See Chapter 6
Installing and Upgrading VMware Tools
n On Windows host machines, enable virtual printing globally, if not already enabled. This
prerequisite does not apply to Linux hosts, on which VMware Virtual Printer is always
enabled. See Configuring Virtual Printers.
n Add a virtual printer device to the virtual machine, if one is not present already. See Add a
Virtual Printer to a Virtual Machine .
n Add a CD/DVD drive to the virtual machine, if one is not present already installed. See Add a
DVD or CD-ROM Drive to a Virtual Machine
Procedure
VMware, Inc. 76
Using VMware Workstation Player for Windows
2 To mount the VMware Virtual Printer application in the CD/DVD drive of the guest, select
Player > Manage > Install Virtual Printer.
3 Install VMware Virtual Printer using the method appropriate for the guest.
n Windows Guest
n Linux Guest
On Linux guests, install VMware Virtual Printer on the virtual machine using a .deb or .rpm
installer package.
The .deb packages are for Debian-based Linux distributions, such as Debian and Ubuntu,
and are in the top directory in the CD/DVD drive.
The .rpm packages are for RPM-based Linux distributions, such as Red Hat, SUSE, and
Fedora, and are divided into folders on the CD/DVD drive. Each folder is specific to a
Linux-distribution type and bitness combination. The .x86_64.rpm package is for 64-bit
Linux guests. The .i386.rpm package is for 32-bit Linux guests.
a Open a terminal window and change directories to the CD/DVD drive for a .deb
package or continue to a specific folder for a .rpm package.
c To verify that VMware Virtual Printer installed successfully, run the appropriate
commands. If the Thinprint service is listed as active, VMware Virtual Printer is
installed and running.
DEB package commands for 32-bit and 64-bit Command to check the status of VMware Virtual Printer.
guests service thinprint status
Command to list the installed package.
dpkg -l thinprint
RPM package commands for 32-bit and 64-bit Command to check the status of VMware Virtual Printer.
guests service thinprint status
Command for information about the installed package.
rpm -q --info thinprint
Results
VMware, Inc. 77
Using VMware Workstation Player for Windows
What to do next
n In the guest, print a test page to a printer you just configured to confirm that VMware Virtual
Printer works as expected.
n When you upgrade Workstation Player in the future, to ensure that a guest has the latest
version of VMware Virtual Printer, uninstall and reinstall VMware Virtual Printer. See Uninstall
VMware Virtual Printer
Procedure
u Use the appropriate uninstallation method based on the operating system of the guest.
n Windows guest
Use the Windows uninstall feature to uninstall the VMware Virtual Printer application. For
example, for Windows 10, perform the following steps.
d Click Uninstall.
n rpm -e thinprint
Results
What to do next
Install VMware Virtual Printer again. See Install VMware Virtual Printer.
VMware, Inc. 78
Using VMware Workstation Player for Windows
A smart card is a plastic card that has an embedded computer chip. Many government agencies
and large enterprises use smart cards to send secure communication, digitally sign documents,
and authenticate users who access their computer networks. Users plug a smart card reader into
their computer and insert their smart card in the reader. They are then prompted for their PIN to
log in.
You can select a smart card reader from the Removable Devices menu in a virtual machine. A
smart card can be shared between virtual machines, or between the host system and one or
more virtual machines. Sharing is enabled by default.
When you plug a smart card reader into the host system, the reader appears as two separate
USB devices in Workstation Player. This is because you can use smart cards in one of two
mutually exclusive modes.
Shared mode
You can use smart cards with Windows operating systems and most Linux distributions. VMware
provides full smart card support for Windows virtual machines running on Linux hosts. Using
smart cards in Linux typically requires third-party software to effectively authenticate to a
domain or enable secure communications.
Note Although smart cards should work with common Linux browsers, email applications, and
directory services, these products have not been tested or certified by VMware.
VMware, Inc. 79
Using VMware Workstation Player for Windows
Prerequisites
n Verify that the virtual machine has a USB controller. A USB controller is required, regardless
of whether the smart card reader is a USB device. A USB controller is added by default when
you create a virtual machine.
Procedure
u To connect the smart card reader to the virtual machine, select the virtual machine and select
Player > Removable Devices > Shared <smart_card_reader_model> > Connect.
If the smart card reader is a USB device, two items appear for it in the menu. Both items use
the model name of the reader, but one item name begins with Virtual.
u To disconnect the smart card reader from the virtual machine, select Player > Removable
Devices > Shared <smart_card_reader_model> > Disconnect.
u To remove the smart card from the virtual machine, select Player > Removable Devices >
Shared <smart_card_reader_model> > Remove Smart Card.
The smart card is removed from the virtual machine, but it remains connected on the host
system. If the smart card is physically removed from the smart card reader, this option is
disabled.
u To insert the smart card to the virtual machine, select Player > Removable Devices > Shared
<smart_card_reader_model> > Insert Smart Card.
If the smart card is physically inserted in the smart card reader, the smart card is also inserted
in the virtual machine.
The setting that controls smart card sharing is located in the Workstation Player global
configuration file.
VMware, Inc. 80
Using VMware Workstation Player for Windows
Procedure
2 If the global configuration file does not yet exist on the host system, select Player > File >
Preferences and change at least one Workstation Player preference setting.
Workstation Player creates the global configuration file when you change Workstation Player
preference settings.
3 Open the global configuration file in a text editor and set the usb.ccid.useSharedMode
property to FALSE.
5 Set permissions on the global configuration file so that other users cannot change it.
VMware, Inc. 81
Setting Up Shared Folders for a
Virtual Machine 10
You can set up shared folders for a virtual machine. Shared folders provide an easy way to share
files among virtual machines and between virtual machines and the host system.
The directories that you add as shared folders can be located on the host system, or they can be
located on network directories that are accessible from the host system. Access to shared
folders is governed by permission settings on the host system. For example, if you are running
Workstation Player as a user named User, the virtual machine can read and write files in the
shared folder only if User has permission to read and write the files.
To use shared folders, the guest operating system must have the current version of VMware
Tools and must support shared folders.
Important Shared folders expose your files to programs in the virtual machine and might put
your data at risk. Only enable shared folders if you trust the virtual machine with your data.
VMware, Inc. 82
Using VMware Workstation Player for Windows
Important You cannot open a file in a shared folder from more than one application at a time.
For example, do not open the same file in an application on the host operating system and in
another application in the guest operating system. If one of the applications writes to the file,
data might be corrupted.
n Windows Vista
n Windows 7
n Windows 8
n Windows 10
n Solaris x86 10
On a Linux host, if you create files that you want to share with a Linux guest operating system,
the file permissions shown on the guest operating system are the same as the permissions on the
host system. You can use the fmask and dmask commands to mask permissions bits for files and
directories.
If you create files on a Windows host system that you want to share with a Linux guest operating
system, read-only files are displayed as having read and execute permission for everyone and
other files are shown as fully writable by everyone.
VMware, Inc. 83
Using VMware Workstation Player for Windows
If you use a Linux guest operating system to create files for which you want to restrict
permissions, use the mount program with the following options in the guest operating system.
n uid
n gid
n fmask
n dmask
n ro (read only)
n rw (read-write)
rw is the default.
If you are using a virtual machine that was created with the Windows version of Workstation
Player, or a previous release of the Linux version of Workstation Player, you can change the
owner permissions only.
Prerequisites
n Verify that the virtual machines use a guest operating system that supports shared folders.
See Guest Operating Systems That Support Shared Folders.
n Verify that the latest version of VMware Tools is installed in the guest operating system.
n Verify that permission settings on the host system allow access to files in the shared folders.
For example, if you are running Workstation Player as a user named User, the virtual machine
can read and write files in the shared folder only if User has permission to read and write
them.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
VMware, Inc. 84
Using VMware Workstation Player for Windows
Option Description
Always enabled Keep folder sharing enabled, even when the virtual machine is shut down,
suspended, or powered off.
Enabled until next power off or Enable folder sharing temporarily, until you power off, suspend, or shut
suspend down the virtual machine. If you restart the virtual machine, shared folders
remain enabled. This setting is available only when the virtual machine is
powered on.
4 (Optional) To map a drive to the Shared Folders directory, select Map as a network drive in
Windows guests.
This directory contains all of the shared folders that you enable. Workstation Player selects
the drive letter.
6 Browse to, or type, the path on the host system to the directory to share.
If you specify a directory on a network share, such as D:\share, Workstation Player always
attempts to use that path. If the directory is later connected to the host on a different drive
letter, Workstation Player cannot locate the shared folder.
7 Specify the name of the shared folder as it should appear inside the virtual machine and click
Next.
Characters that the guest operating system considers illegal in a share name appear
differently when viewed inside the guest. For example, if you use an asterisk in a share name,
you see %002A instead of * in the share name on the guest. Illegal characters are converted
to their ASCII hexadecimal value.
Option Description
Enable this share Enable the shared folder. Deselect this option to disable a shared folder
without deleting it from the virtual machine configuration.
Read-only Make the shared folder read-only. When this property is selected, the virtual
machine can view and copy files from the shared folder, but it cannot add,
change, or remove files. Access to files in the shared folder is also governed
by permission settings on the host computer.
The shared folder appears in the Folders list. The check box next to folder name indicates
that the folder is being shared. You can deselect this check box to disable sharing for the
folder.
VMware, Inc. 85
Using VMware Workstation Player for Windows
What to do next
View the shared folder. On Linux guests, shared folders appear under /mnt/hgfs. On Solaris
guests, shared folders appear under /hgfs. To view shared folders on a Windows guest, see
View Shared Folders in a Windows Guest.
Note If the guest operating system has VMware Tools from Workstation 4.0, shared folders
appear as folders on a designated drive letter.
Procedure
u Depending on the Windows operating system version, look for VMware Shared Folders in
My Network Places, Network Neighborhood, or Network.
u If you mapped the shared folder as a network drive, open My Computer and look for Shared
Folders on 'vmware-host' under Network Drives.
u To view a specific shared folder, go directly to the folder by using the UNC path \\vmware-
host\Shared Folders\shared_folder_name.
Depending on the kernel version of the Linux guest operating system, VMware Tools uses
different components to provide shared-folder functionality. In Linux kernels prior to version 4.0,
the VMware Tools services script loads a driver that performs the mount. Linux kernels 4.0 and
later use a FUSE file system component.
You can use different mount commands to mount all shares, one share, or a subdirectory within a
share to any location in the file system. The commands also vary depending on the Linux-kernel
version of the guest.
VMware, Inc. 86
Using VMware Workstation Player for Windows
mount -t vmhgfs .host:/ /home/user1/ /usr/bin/vmhgfs-fuse .host:/ /home/ Mounts all shares to /home/
shares user1/shares -o subtype=vmhgfs- user1/shares
fuse,allow_other
mount -t vmhgfs .host:/foo /tmp/foo /usr/bin/vmhgfs-fuse .host:/ Mounts the share named foo
foo /tmp/foo -o subtype=vmhgfs- to /tmp/foo
fuse,allow_other
For Linux kernel prior to version 4.0, you can use VMware-specific options in addition to the
standard mount syntax. Enter the command /sbin/mount.vmhgfs -h to list the options.
For Linux kernel version 4.0 or later, enter the command /usr/bin/vmhgfs-fuse -h to list the
available options.
Note The mount can fail if shared folders are disabled or if the share does not exist. You are not
prompted to run the VMware Tools vmware-config-tools.pl configuration program again.
Prerequisites
Create a shared folder. See Enable a Shared Folder for a Virtual Machine.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
3 Select the shared folder in the folders list and click Properties.
4 To change the name of the shared folder as it appears inside the virtual machine, type the
new name in the Name text box.
Characters that the guest operating system considers illegal in a share name appear
differently when viewed inside the guest. For example, if you use an asterisk in a share name,
you see %002A instead of * in the share name on the guest. Illegal characters are converted
to their ASCII hexadecimal value.
VMware, Inc. 87
Using VMware Workstation Player for Windows
5 To change the host path for the shared folder, browse to or type the new path in the Host
path text box.
If you specify a directory on a network share, such as D:\share, Workstation Player always
attempts to use that path. If the directory is later connected to the host on a different drive
letter, Workstation Player cannot locate the shared folder.
6 To change an attribute for the shared folder, select or deselect the attribute.
Option Description
Enabled Enable the shared folder. Deselect this option to disable a shared folder
without deleting it from the virtual machine configuration.
Read-only Make the shared folder read-only. When this property is selected, the virtual
machine can view and copy files from the shared folder, but it cannot add,
change, or remove files. Access to files in the shared folder is also governed
by permission settings on the host computer.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
3 In the folders list, select the check boxes next to the folders to share and deselect the check
boxes next to the folders to disable.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
VMware, Inc. 88
Using VMware Workstation Player for Windows
After you map the virtual disk to a drive on the host system, you cannot power on any virtual
machine that uses the disk until you disconnect the disk from the host system.
Important If you mount a virtual disk that has a snapshot and then write to the disk, you can
irreparably damage a snapshot or linked clone created from the virtual machine. Note that
Workstation Player does not support taking snapshots or deleting them.
Mapping a virtual disk to a host system is not supported in the standalone version of Workstation
Player. Virtual disk mapping is supported in the Workstation Player version included with
Workstation Pro.
Prerequisites
n Power off all virtual machines that use the virtual disk.
n Verify that the virtual disk (.vmdk) files on the virtual disk are not compressed and do not
have read-only permissions.
n On a Windows host, verify that the volume is formatted with FAT (12/16/32) or NTFS. Only
FAT (12/16/32) and NTFS formatting is supported. If the virtual disk has mixed partitions, for
example, one partition is formatted with a Linux operating system and another partition is
formatted with a Windows operating system, you can map the Windows partition only.
n Verify that the virtual disk is unencrypted. You cannot map or mount encrypted disks.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
2 On the Hardware tab, select Hard Disk, click Utilities, and select Map.
3 On a Windows host, leave the check box Open file in read-only mode selected in the Map
Virtual Disk dialog box.
This setting prevents you from accidentally writing data to a virtual disk that might be the
parent of a snapshot or linked clone. Writing to such a disk might make the snapshot or
linked clone unusable.
4 Browse to a virtual disk (.vmdk) file, select it, and click Open.
VMware, Inc. 89
Using VMware Workstation Player for Windows
5 Select the volume to map or mount and select an unused drive letter on the host system.
6 (Optional) On a Windows host, if you do not want the drive to open in Windows Explorer
after it is mapped, deselect the Open drive in Windows Explorer after mapping check box.
7 Click OK or Mount.
The drive appears on the host system. You can read from or write to files on the mapped
virtual disk on the host system.
On Windows hosts, you must use Workstation Player to disconnect the drive from the host
system. The mapped drive letter does not appear in the list of network drives when you use the
Windows Disconnect Network Drive command.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
2 On the Hardware tab, select Hard Disk, click Utilities, and select Disconnect.
Results
You can now power on any virtual machine that uses this disk.
VMware, Inc. 90
Configuring and Managing Virtual
Machines 11
You can change virtual machine options, configure video and sound card settings, and move
virtual machines to another host system or to a different location on the same host system.
Changing the name of a virtual machine does not change the name of the virtual machine
directory or rename the virtual machine files on the host system.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
VMware, Inc. 91
Using VMware Workstation Player for Windows
What to do next
When you restart the virtual machine the new name appears in the library.
When you change the operating system type, the virtual machine configuration (.vmx) file
changes. The guest operating system itself does not change. To upgrade the guest operating
system, obtain the appropriate software from the operating system vendor.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
The working directory is where Workstation Player stores suspended state (.vmss), snapshot
(.vmsn), virtual machine paging (.vmem), and redo log files for a virtual machine.
Changing the working directory does not change the directory where the virtual machine
configuration (.vmx) file or the log files are stored.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
VMware, Inc. 92
Using VMware Workstation Player for Windows
Prerequisites
Procedure
1 In the host file system, rename the directory where the .vmx file is stored.
3 Browse to the new location of the .vmx file and click Open.
On 64-bit hosts, the maximum amount of memory for each virtual machine is 32GB. On 32-bit
hosts, the maximum amount of memory for each virtual machine is 8GB. The total amount of
memory that you can assign to all virtual machines running on a single host system is limited only
by the amount of RAM on the host system.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
The Memory panel includes information to help you select the appropriate amount of
memory for the virtual machine. The high end of the range is determined by the amount of
memory that is allocated to all running virtual machines.
3 Align the slider with the corresponding icon to change the amount of memory.
The color-coded icons indicate the maximum recommended memory, the recommended
memory, and the guest operating system minimum memory amounts.
VMware, Inc. 93
Using VMware Workstation Player for Windows
Workstation Player usually installs the necessary drivers for sound support, but you must
manually install a driver on some of the oldest and newest guest operating systems.
n Configuring Sound
Workstation Player provides a sound device compatible with the Sound Blaster AudioPCI
and supports sound in Windows and Linux guest operating systems. The Workstation Player
sound device is enabled by default.
n 8-bit pseudocolor
If the host operating system is in 15-bit color mode, the guest operating system color setting
controls offer 15-bit mode in place of 16-bit mode. If the host operating system is in 24-bit color
mode, the guest operating system color setting controls offer 24-bit mode in place of 32-bit
mode.
If you run a guest operating system set for a greater number of colors than the host operating
system, the colors in the guest operating system might not be correct or the guest operating
system might not be able to use a graphical interface. If these problems occur, you can either
increase the number of colors in the host operating system or decrease the number of colors in
the guest operating system.
To change color settings on the host operating system, power off all virtual machines and close
Workstation Player and then follow standard procedures for changing color settings.
VMware, Inc. 94
Using VMware Workstation Player for Windows
How you change color settings in a guest operating system depends on the type of guest
operating system. In a Windows guest, the Display Properties control panel offers only those
settings that are supported. In a Linux or FreeBSD guest, you must change the color depth
before you start the X server, or you must restart the X server after making the changes.
For best performance, use the same number of colors in the host and guest operating systems.
Support for applications that use DirectX 9 accelerated graphics applies only to Windows XP,
Windows Vista, and Windows 7 guests on hosts running Windows 7 or later, or Linux. OpenGL
applications run in software emulation mode.
Support for applications that use DirectX 10 accelerated graphics applies only to Windows 10.
Prerequisites
n Verify that the host has a video card that supports DirectX 9, DirectX 10, DirectX 10.1, or
DirectX 11 and the latest DirectX Runtime required for the DirectX version being used.
The VMware guest operating system OpenGL driver for Windows and Linux supports the
OpenGL 3.3 and OpenGL 4.1 core profile only. The compatibility profile is not supported.
Procedure
1 Upgrade the video drivers on the host system to the latest versions.
ATI Graphics drivers are available from the AMD Web site. NVIDIA drivers are available from
the NVIDIA Web site. Intel drivers are available from the Intel Web site.
Option Description
Windows 7, Windows 8, and Right-click the desktop and select Personalize > Screen resolution >
Windows 10 Advanced Settings > Troubleshoot > Change settings.
The accelerated 3D graphics feature is enabled by default on Player 3.x and later virtual
machines.
VMware, Inc. 95
Using VMware Workstation Player for Windows
Prerequisites
n Prepare the host system to use accelerated 3D graphics. See Prepare the Host System to
Use 3D Accelerated Graphics.
n If using DirectX 9, verify that the guest operating system is Windows XP or later. DirectX 9 is
supported on virtual machines running hardware version 11 or earlier.
n If using DirectX 10, verify that the guest operating system is Windows 7 or later. DirectX 10 is
supported on virtual machines running hardware version 12 or later.
n If using DirectX 10.1, verify that the guest operating system is Windows 7 or later. DirectX 10.1
is supported on virtual machines running hardware version 16 or later.
n If using DirectX 11, verify that the guest operating system is Windows 7 or later. DirectX 11 is
supported on virtual machines running hardware version 18 or later.
n Verify that the latest version of VMware Tools is installed in the guest operating system.
n Power off the virtual machine. The virtual machine must not be suspended.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
6 Power on the virtual machine and install the required DirectX EndRuntime version.
Configuring Sound
Workstation Player provides a sound device compatible with the Sound Blaster AudioPCI and
supports sound in Windows and Linux guest operating systems. The Workstation Player sound
device is enabled by default.
Sound support includes pulse code modulation (PCM) output and input. For example, you can
play .wav files, MP3 audio, and Real Media audio. MIDI output from Windows guests is supported
through the Windows software synthesizer. MIDI input is not supported, and no MIDI support is
available for Linux guests.
Windows and most recent Linux distributions detect the sound device and install appropriate
drivers for it.
A sound driver is installed when you install VMware Tools in a 64-bit Windows Vista or Windows
7 guest operating system. For 32-bit Windows Vista, Windows 7, Windows 2003 Server, and
Windows Server 2008 guests, you must use Windows Update to install a 32-bit driver.
VMware, Inc. 96
Using VMware Workstation Player for Windows
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
Connected Connects or disconnects the sound device while the virtual machine is
running. You can also use the Devices menu and select the drive to connect
or disconnect.
Connect at power on Automatically connects the sound device to the virtual machine when you
power on the virtual machine.
Use default host sound card The virtual machine uses the default sound card in the host system.
Specify host sound card Selects which sound card to use if you have more than one physical sound
card on the host system.
Enable echo cancellation Enables echo cancellation for the sound card.
VMware, Inc. 97
Using VMware Workstation Player for Windows
Moving a virtual machine typically involves moving the files that make up the virtual machine. The
pathnames for all files associated with a Workstation Player virtual machine are relative to the
virtual machine directory.
When you move a virtual machine, Workstation Player generates a new MAC address for the
virtual network adapter. Workstation Player also generates a new MAC address when you
rename a directory in the path to the virtual machine configuration (.vmx) file.
Prerequisites
n Familiarize yourself with how Workstation Player generates UUIDs for moved virtual
machines. See Using the Virtual Machine UUID.
n If you are moving the virtual machine to a different host system, familiarize yourself with the
limitations of moving a virtual machine to a new host. See Limitations of Moving a Virtual
Machine to a Different Host.
n If you configured the working directory to reside in a different location on the host system,
move files from the working directory into the virtual machine directory and change the
working directory to this location.
n Verify that virtual machine devices and any associated files point to locations that you can
access from the new location.
n Verify that all virtual machine files are stored in the virtual machine directory. Some files might
reside outside of the virtual machine directory.
Procedure
1 Shut down the guest operating system and power off the virtual machine.
3 Verify that you copied all of the virtual machine files to the new location.
Option Description
If you moved the virtual machine to Remove the virtual machine from the library, select File > Open a Virtual
a different location on the same host Machine, and browse to the .vmx file in its new location.
system
If you moved the virtual machine to Start Workstation Player on the new host system, select File > Open a
a different host system Virtual Machine, and browse to the .vmx file.
5 When you are certain that the virtual machine in the new location works correctly, delete the
virtual machine files from the original location.
VMware, Inc. 98
Using VMware Workstation Player for Windows
n The guest operating system might not work correctly if you move a virtual machine to a host
system that has significantly different hardware, for example, if you move a virtual machine
from a multiprocessor host to a uniprocessor host.
n Player 3.x and later virtual machines support up to eight-way virtual symmetric
multiprocessing (SMP) on multiprocessor host systems. Player 6.x and later virtual machines
support up to sixteen-way multiprocessing on multiprocessor host systems. You can assign
up to 8 or 16 virtual processors to virtual machines running on host systems that have at least
two logical processors. If you attempt to assign two processors to a virtual machine that is
running on a uniprocessor host system, a warning message appears. You can disregard this
message and assign two processors to the virtual machine, but you must move it to a host
that has at least two logical processors before you can power it on.
Procedure
VMware Tools significantly improves the user’s experience working with the virtual machine.
u Determine which virtual devices are actually required, and do not include any that are not
needed or useful for the software you are distributing with the virtual machine.
u To connect a physical device to a virtual device, use the Auto detect options when you
configure the virtual machine.
The Auto detect options allow the virtual machine to adapt to the user’s system, and they
work whether the host operating system is Windows or Linux. Users who have no physical
device receive a warning message.
u To connect a CD-ROM or floppy to an image file that you ship with the virtual machine, make
sure the image file is in the same directory as the virtual machine.
u For both a physical CD-ROM and an image, provide two virtual CD-ROM devices in the virtual
machine.
VMware, Inc. 99
Using VMware Workstation Player for Windows
For example, if the host system does not have enough physical memory to support the
memory allocation, the user cannot power on the virtual machine.
A user is likely to find it easier to increase the resolution manually than to deal with a display
that exceeds the user’s physical screen size.
You can use the UUID of a virtual machine for system management in the same way that you use
the UUID of a physical computer. The UUID is stored in the SMBIOS system information
descriptor, and you can access it by using standard SMBIOS scanning software, including
SiSoftware Sandra or IBM smbios2.
If you do not move or copy the virtual machine to another location, the UUID remains constant.
When you power on a virtual machine that was moved or copied to a new location, you are
prompted to specify whether you moved or copied the virtual machine. If you indicate that you
copied the virtual machine, the virtual machine receives a new UUID.
Suspending and resuming a virtual machine does not trigger the process that generates a UUID.
The UUID in use at the time the virtual machine was suspended remains in use when the virtual
machine is resumed, even if it was copied or moved. You are not prompted to specify whether
you moved or copied the virtual machine until the next time you reboot the virtual machine.
Prerequisites
Procedure
Prerequisites
Procedure
1 Right-click the virtual machine in the library and select Delete VM from Disk.
Results
The virtual machine and all of its files are removed from the host file system.
Procedure
3 Select a message in the message log to a see a detailed description of the message.
Prerequisites
n Verify that VMware Tools is installed in the guest operating system. Installing VMware Tools
before installing the software minimizes the likelihood that you will have to reactivate the
software if the virtual machine configuration changes.
n Verify that the virtual machine has access to the CD-ROM drive, ISO image file, or floppy drive
where the installation software is located.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
2 On the Hardware tab, select Memory, set the final memory size for the virtual machine, and
click OK.
Some applications use a product activation feature that creates a key based on the virtual
hardware in the virtual machine where it is installed. Changes in the configuration of the
virtual machine might require you to reactivate the software. Setting the memory size
minimizes the number of significant changes.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
What to do next
After you pass the point where the program encountered problems, re-enable acceleration.
Because disabling acceleration slows down virtual machine performance, you should use it only
for getting past the problem with running the program
A virtual machine can read data from a DVD disc. Workstation Player does not support playing
DVD movies in a virtual machine. If you use a DVD player application that does not require video
overlay support in the video card, you might be able to play a movie.
You can configure the virtual DVD or CD-ROM drive as an IDE, SCSI, or SATA device, regardless
of the type of physical drive that you connect it to. For example, if the host has an IDE CD-ROM
drive, you can set up the virtual machine drive as either SCSI or IDE and connect it to the host
drive.
Do not configure legacy emulation mode unless you experience problems with normal mode. See
Configure Legacy Emulation Mode for a DVD or CD-ROM Drive for more information.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
5 (Optional) To change which SCSI, IDE, or SATA device identifier to use for the drive, select
the drive and click Advanced.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
Use a physical floppy drive The virtual machine uses a physical floppy drive.
Use a floppy image The drive connects to an floppy image (.flp) file.
Create a blank floppy image The drive connects to a blank floppy image (.flp) file that you create.
6 If you selected the physical floppy drive media type, select a specific floppy drive or select
Auto detect to allow Workstation Player to auto-detect the drive to use.
7 If you selected the floppy image or blank floppy image media type, type the name or browse
to the location of a floppy image (.flp) file.
8 To connect the drive or floppy image file to the virtual machine when the virtual machine
powers on, select Connect at power on.
In legacy emulation mode, you can read only from data discs in the DVD or CD-ROM drive.
Legacy emulation mode does not provide the other capabilities of normal mode. In normal mode,
the guest operating system communicates directly with the CD-ROM or DVD drive. This direct
communication enables you to read multisession CDs, perform digital audio extraction, view
videos, and use CD and DVD writers to burn discs.
If you run more than one virtual machine at a time, and if their CD-ROM drives are in legacy
emulation mode, you must start the virtual machines with their CD-ROM drives disconnected. By
disconnecting the CD-ROM drives in the virtual machines, you prevent multiple virtual machines
from being connected to the CD-ROM drive at the same time.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Workstation Player provides a USB controller to support the following types of USB devices.
n USB 1.1 UHCI (Universal Host Controller Interface) is supported for all virtual machine
hardware versions.
n USB 2.0 EHCI (Enhanced Host Controller Interface) controllers are supported if the virtual
machine hardware is compatible with Workstation 6 and later virtual machines.
n USB 3.0 xHCI (Extensible Host Controller Interface) support is available for Linux guests
running kernel version 2.6.35 or later and for Windows 8 guests. The virtual machine
hardware must be compatible with Workstation 8 or later virtual machines.
For USB 2.0 or 3.0 support, you must select USB 2.0 or 3.0 compatibility by configuring virtual
machine settings for the USB controller. USB 2.0 and 3.0 devices are high-speed devices that
include the latest models of USB flash drives, USB hard drives, iPods, and iPhone.
If you select USB 2.0 compatibility, when a USB 2.0 device connects to a USB port on the host
system, the device connects to the EHCI controller and operates in USB 2.0 mode. A USB 1.1
device connects to the UHCI controller and operates in USB 1.1 mode. If you enable USB 3.0, the
xHCI controller can support all USB devices, including USB 1.1, 2.0, and 3.0 devices.
Although the host operating system must support USB, you do not need to install device-specific
drivers for USB devices in the host operating system to use those devices only in the virtual
machine. Linux kernels earlier than 2.2.17 do not support USB.
VMware has tested a variety of USB devices. If the guest operating system has the appropriate
drivers, you can use many different USB devices, including PDAs, Smart phones, printers, storage
devices, scanners, MP3 players, digital cameras, memory card readers, and isochronous transfer
devices, such as webcams, speakers, and microphones.
You can connect USB human interface devices (HIDs), such as the keyboard and mouse, to a
virtual machine by enabling the Show all USB input devices option. If you do not select this
option, these devices do not appear in the Removable Devices menu and are not available to
connect to the virtual machine, even though they are plugged in to USB ports on the host
system.
See Connect USB HIDs to a Virtual Machine for information on connecting HIDs.
When you create a virtual machine in Workstation Player, a USB controller is added by default. If
you remove the USB controller, you can add it back.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
USB Compatibility Selecting USB 2.0 or 3.0 enables support for isochronous USB devices, including Web
cams, speakers, and microphones.
Show all USB input devices Human interface devices (HIDs), such as USB 1.1 and 2.0 mouse and keyboard
devices, appear in the Removable Devices menu. Icons for HIDs appear in the status
bar. An HID that is connected to the guest operating system is not available to the
host system. The virtual machine must be powered off when you change this setting.
Prerequisites
n Verify that the guest operating system supports USB 2.0 devices or 3.0 devices.
n On a Windows XP guest operating system, verify that the latest service pack is installed. If
you use Windows XP with no service packs, the driver for the EHCI controller cannot be
loaded.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
3 From the USB Compatibility list, select USB 2.0 or USB 3.0.
Option Description
USB 2.0 Available if the virtual machine hardware is compatible with Workstation 6
and later virtual machines.
USB 3.0 Available for Linux guests running kernel version 2.6.35 or later and for
Windows 8 guests. The virtual machine hardware must be compatible with
Workstation 8 and later virtual machines.
A virtual disk is a file or set of files that appears as a physical disk drive to a guest operating
system. The files can be on the host system or on a remote computer. When you configure a
virtual machine to use a virtual disk, you can install a new operating system onto the virtual disk
without repartitioning a physical disk or rebooting the host.
The New Virtual Machine wizard creates a virtual machine that has one disk drive. You can
modify virtual machine settings to add more disk drives to a virtual machine, remove disk drives
from a virtual machine, and change certain settings for the existing disk drives.
The files that make up an IDE, SATA, SCSI, or NVMe virtual hard disk can be stored on a hard disk
of any type. They can also be stored on other types of fast-access storage media.
To use SCSI hard disks in a 32-bit Windows XP virtual machine, you must download a special SCSI
driver from the VMware Web site. Follow the instructions on the Web site to use the driver with a
fresh installation of Windows XP.
Virtual hard disk files include information such as the operating system, program files, and data
files. Virtual disk files have a .vmdk extension.
By default, the actual files that the virtual hard disk uses start small and grow to their maximum
size as needed. The main advantage of this approach is the smaller file size. Smaller files require
less storage space and are easier to move to a new location, but it takes slightly longer to write
data to a disk configured in this way.
You can also configure virtual hard disks so that all of the disk space is allocated when the virtual
disk is created. This approach provides enhanced performance and is useful if you are running
performance-sensitive applications in the virtual machine.
Regardless of whether you allocate all disk space in advance, you can configure the virtual hard
disk to split into multiple files on the host disk. The split is not visible to the virtual machine, but is
necessary if you move the virtual machine or its disks to a file system that does not support files
larger than 4GB, such as a USB thumb drive formatted with the FAT32 file system.
Virtual hard disks are stored as files on the host computer or on a network file server. A virtual
IDE drive or SCSI drive can be stored on a physical IDE drive or on a physical SCSI drive.
As an alternative to adding a new virtual hard disk, you can expand the existing virtual hard disk.
See Expand a Virtual Hard Disk.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
IDE Create an IDE device. You can add up to four IDE devices to a virtual
machine.
SCSI Create a SCSI device. You can add up to 60 SCSI devices to a virtual
machine.
SATA Create a SATA device. You can add up to 120 SATA devices, four
controllers, and 30 devices per controller.
NVMe Create an NVMe device. You can add up to 60 NVMe devices, four
controllers, and 15 devices per controller.
You can set a size between 0.001 GB and 8 TB for a virtual disk.
Option Description
Allocate all disk space now Allocating all of the disk space when you create the virtual hard disk can
enhance performance, but it requires all of the physical disk space to be
available now. If you do not select this setting, the virtual disk starts small
and grows as you add data to it.
Store virtual disk as a single file Select this option if the virtual disk is stored on a file system that does not
have a file size limitation.
Split virtual disk into multiple files Select this option if the virtual disk is stored on a file system that has a file
size limitation. When you split a virtual disk less than 950 GB, a series of 2
GB virtual disk files are created. When you split a virtual disk greater than
950 GB, two virtual disk files are created. The maximum size of the first
virtual disk file is 1.9 TB and the second virtual disk file stores the rest of the
data.
8 Accept the default filename and location, or browse to and select a different location.
The wizard creates the new virtual hard disk. The disk appears to the guest operating system
as a new, blank hard disk.
11 Use the guest operating system tools (such as the Windows Disk Management tool or the
fdisk command in Linux) to partition and format the new drive.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
5 Specify the path name and filename for the existing disk file.
Prerequisites
n Verify that the virtual disk is not mapped or mounted. You cannot compact a virtual disk while
it is mapped or mounted.
n Verify that the disk space is not preallocated for the virtual hard disk. If the disk space was
preallocated, you cannot compact the disk.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
When you expand a virtual hard disk, the added space is not immediately available to the virtual
machine. To make the added space available, you must use a disk management tool to increase
the size of the existing partition on the virtual hard disk to match the expanded size.
The disk management tool that you use depends on the virtual machine guest operating system.
Many operating systems, including Windows Vista, Windows 7, and Windows 8 and some
versions of Linux, provide built-in disk management tools that can resize partitions. Third-party
disk management tools are also available, such as EASEUS Partition Master, Acronis Disk
Director, and the open-source tool GParted.
When you expand the size of a virtual hard disk, the sizes of partitions and file systems are not
affected.
As an alternative to expanding a virtual hard disk, you can add a new virtual hard disk to the
virtual machine. See Add a New Virtual Hard Disk to a Virtual Machine.
Prerequisites
n Verify that the virtual disk is not mapped or mounted. You cannot expand a virtual disk while
it is mapped or mounted.
Note Workstation Player does not support taking snapshots or deleting them.
n Verify that the virtual machine is not a linked clone or the parent of a linked clone.
You can determine whether a virtual machine is a linked clone by the virtual machine name
string on the summary page. If the string includes "Clone of: virtual machine name", the
virtual machine is a linked clone. If the string includes "Snapshot: Snapshot for virtual machine
name", the virtual machine is a parent of a linked clone.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
You can set a size between 0.001 GB and 8192 GB for a virtual disk.
5 Select Expand.
What to do next
Use a disk management tool to increase the disk partition size to match the expanded virtual disk
size.
Prerequisites
n Verify that there is adequate free working space on the host system. For example, if the
virtual hard disk is contained in a single file, there must be free space equal to the size of the
virtual disk file. Other virtual hard disk configurations require less free space.
n Verify that the virtual disk is not mapped or mounted. You cannot defragment a virtual disk
while it is mapped or mounted.
Procedure
2 If disk space is not preallocated for the virtual hard disk, use the Workstation Player
defragmentation tool to defragment it.
b Select the virtual machine and select Player > Manage > Virtual Machine Settings.
After you remove a virtual hard disk from a virtual machine, you can map or mount the disk to
the host system and copy data from the guest operating system to the host without powering on
the virtual machine or starting Workstation Player. You can also add the disk to another virtual
machine.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
2 On the Hardware tab, select the virtual hard disk and click Remove.
Lock files have a .lck suffix and are created in subdirectories in the same directory as the virtual
disk (.vmdk) files. A locking subdirectory and lock file are created for .vmdk files, .vmx files,
and .vmem files.
A unified locking method is used on all host operating systems so that files shared between them
are fully protected. For example, if one user on a Linux host tries to power on a virtual machine
that is already powered on by another user with a Windows host, the lock files prevent the
second user from powering on the virtual machine.
When a virtual machine powers off, it removes the locking subdirectories and the lock files. If the
virtual machine cannot remove these locking controls, one or more stale lock files might remain.
For example, if the host system fails before the virtual machine removes its locking controls, stale
lock files remain.
When the virtual machine restarts, it scans any locking subdirectories for stale lock files and,
when possible, removes them. A lock file is considered stale if the lock file was created on the
same host system that is now running the virtual machine and the process that created the lock is
no longer running. If either of these conditions is not true, a dialog box warns you that the virtual
machine cannot be powered on. You can delete the locking directories and their lock files
manually.
Locks also protect physical disk partitions. Because the host operating system is not aware of
this locking convention, it does not recognize the lock. For this reason, you should install the
physical disk for a virtual machine on the same physical disk as the host operating system.
For example, you can use Workstation Player on a Windows host system to create virtual hard
disks, move the disks to a Linux computer, and use the disks with Workstation Player on a Linux
host system.
Parallel ports are used for a variety of devices, including printers, scanners, dongles, and disk
drives. Although these devices can connect to the host system, only printers can reliably connect
to virtual machines by using parallel ports.
Workstation Player provides only partial emulation of PS/2 hardware. Interrupts that a device
connected to a physical port requests are not passed to the virtual machine. The guest operating
system cannot use direct memory access (DMA) to move data to or from the port. For this
reason, not all devices that attach to a parallel port work correctly. Do not use virtual parallel
ports to connect parallel port storage devices or other types of parallel port devices to a virtual
machine.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
4 Click Finish to add the virtual parallel port to the virtual machine.
Option Description
Use a physical parallel port Select a parallel port on the host system.
Use output file Send output from the virtual parallel port to a file on the host system. Either
locate an existing output file or browse to a directory and type a filename to
create a new output file.
6 To connect the virtual parallel port to the virtual machine when the virtual machine powers
on, select Connect at power on.
Results
When a parallel port is configured for a virtual machine, most guest operating systems detect the
port at installation time and install the required drivers. Some operating systems, including Linux,
detect the ports at boot time.
Problem
When you power on a virtual machine after adding a parallel port, an error messages states that
the parallel port on the host system does not have an ECR.
Cause
This problem can occur when the hardware supports ECR, but ECR has been disabled in the
BIOS.
Solution
2 Early in the boot process, press and hold down the Delete key to enter the BIOS
configuration editor.
3 Find the parallel port field and enable Extended Capability Port (ECP) mode or a combination
of modes that includes ECP.
You might want to add a virtual serial port to a virtual machine to make devices such as modems
and printers available to the virtual machine. You can also use virtual ports to send debugging
data from a virtual machine to the host system or to another virtual machine.
Note The virtual printer feature configures a serial port to make host printers available to the
guest. You do not need to install additional drivers in the virtual machine.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
4 Click Finish to add the virtual serial port to the virtual machine.
Option Description
Use a physical parallel port Send output to a physical serial port on the host system.
Use output file Send output to a file on the host system. Either locate an existing output file
or browse to a directory and type a filename to create a new output file.
Output to named pipe Set up a direct connection between two virtual machines, or a connection
between a virtual machine and an application on the host system.
The pipe name must begin with \\.\pipe\ and must be the same on both the server and
the client.
For example: \\.\pipe\namedpipe
b To send debugging information to an application on the host system, select This end is
the server from the first drop-down menu and select The other end is an application
from the second drop-down menu.
c To send debugging information to another virtual machine, select This end is the server
from the first drop-down menu and The other end is a virtual machine from the second
drop-down menu.
7 To connect the port to the virtual machine when the virtual machine powers on, select
Connect at power on.
8 (Optional) On the Hardware tab, select the new serial port, select Yield CPU on poll, and click
OK.
This option is useful if you are using debugging tools that communicate over a serial
connection. If the serial port in the guest operating system is being used in polled mode
rather than interrupt mode, you might notice performance issues. This option forces the
virtual machine to yield processor time if the only task it is trying to do is poll the virtual serial
port.
What to do next
If you set up a connection between two virtual machines, the first virtual machine is set up as the
server. Repeat this procedure for the second virtual machine, but set it up as the client by
selecting This end is the client when you configure the named pipe.
In principle, the output speed, which is the speed at which the virtual machine sends data
through the virtual serial port, is unlimited. In practice, the output speed depends on how fast the
application at the other end of the pipe reads inbound data.
Prerequisites
n Use the guest operating system to configure the serial port for the highest setting supported
by the application that you are running in the virtual machine.
Procedure
1 In a text editor, add the following line to the virtual machine configuration (.vmx) file.
serialport_number.pipe.charTimePercent = "time"
port_number is the number of the serial port, starting from 0. The first serial port is serial0.
time is a positive integer that specifies the time taken to transmit a character, expressed as a
percentage of the default speed set for the serial port in the guest operating system. For
example, a setting of 200 forces the port to take twice as long for each character, or send
data at half the default speed. A setting of 50 forces the port to take only half as long for
each character, or send data at twice the default speed.
2 Assuming that the serial port speed is set appropriately in the guest operating system,
experiment with this setting by starting with a value of 100 and gradually decreasing it until
you find the highest speed at which the connection works reliably.
To use SCSI devices in a virtual machine running on a Windows host system, you must run
Workstation Player as a user who has administrator access.
Although generic SCSI is device independent, it can be sensitive to the guest operating system,
device class, and specific SCSI hardware.
Prerequisites
n On a Windows host system, run Workstation Player as a user who has administrator access.
n On a 32-bit Windows XP virtual machine, install the special SCSI driver that VMware provides.
You can download the driver from the VMware Web site.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
5 Select the physical SCSI device to map to the virtual SCSI device.
6 To connect the device when the virtual machine powers on, select Connect at power on.
7 On the Hardware tab, select the SCSI device identifier to use for the device from the Virtual
device node drop-down menu and click OK.
For example, if you select SCSI 0:2, the guest operating system sees the drive as ID 2 on
controller 0.
Problem
The SCSI device does not appear in the list of available SCSI devices after you add it to a virtual
machine.
Cause
A driver for that device is not installed on the host system, a driver on the host system prevents
the device from being detected, or the virtual machine uses a device for which there are no
drivers available to the host operating system.
Solution
1 Determine the SCSI bus number that the device uses on the host system.
The SCSI bus is assigned a number by the host operating system after all IDE buses are
assigned numbers. For example, if you have two IDE buses, they are numbered 0 and 1. The
first SCSI bus is assigned bus number 2. You can use a third-party tool, such as winobj, to
determine the SCSI bus number.
2 Determine the target ID that the device uses in the virtual machine and on the host system.
3 Determine whether the device driver for the device is installed on the host system.
If the device driver is not installed, install it and see if the device appears. To avoid a device-
in-use conflict between the host and guest, you might not want to install the driver on the
host system.
4 If an original SCSI device driver is already installed on the host system, disable it.
Some Windows operating systems do not process the send command from the adapter if the
device driver owns the device.
5 Power off the virtual machine and open the virtual machine configuration (.vmx) file in a text
editor.
6 Add or change the following line in the virtual machine configuration (.vmx) file.
scsiZ:Y.fileName = "deviceName"
Z is the SCSI bus number the device uses in the virtual machine. For deviceName, use
scsiX:Y, where X is the SCSI bus number that the device uses on the host system and Y is the
target ID that the device uses in both the virtual machine and on the host system.
For example, if the problematic device is a CD-ROM drive, the existing entry is
scsi0:4.fileName = "CdRom0" and the device on the host system is located on bus 2 with
target ID 4, change the line to scsi0:4.fileName = "scsi2:4".
7 If the virtual machine does not contain any SCSI devices, to add a generic SCSI device to a
new virtual SCSI adapter, or to use an existing SCSI device as a generic SCSI device, add the
following line to the virtual machine configuration (.vmx) file.
scsiZ:Y.deviceType = "scsi-passthru"
8 If the virtual machine does not contain any SCSI devices, or to add a generic SCSI device to a
new virtual SCSI adapter, add the following lines to the virtual machine configuration (.vmx)
file.
scsiZ:Y.present = "true"
scsiZ.present = "true"
Workstation Player considers multiprocessor hosts that have two or more physical CPUs, single-
processor hosts that have a multicore CPU, and single-processor hosts that have hyperthreading
enabled, to have two logical processors.
Note On hyperthreaded uniprocessor hosts, performance of virtual machines that have virtual
SMP might be below normal. Even on multiprocessor hosts, performance is affected if you
overcommit by running multiple workloads that require more total CPU resources than are
physically available.
You can power on and run multiple dual-processor virtual machines concurrently. The number of
processors for a given virtual machine appears in the summary view of the virtual machine.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
You can see the number of processors in the virtual machine summary view or by viewing the
virtual machine hardware settings.
Prerequisites
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Note that Number of processors is set to Other (x), where x is the number of processors
originally assigned to it. Workstation Player preserves this original configuration setting for
the number of processors, even though eight is the maximum number of processors
supported.
After you commit a change to this setting, the original setting for the number of processors is
discarded and no longer appears as an option.
Because it processes raw keyboard input as soon as possible, the enhanced virtual keyboard
feature also offers security improvements by bypassing Windows keystroke processing and any
malware that is not already at a lower layer. When you use the enhanced virtual keyboard
feature, only the guest operating system acts when you press Ctrl+Alt+Delete.
Prerequisites
n If you recently installed or upgraded Workstation Player, but did not restart the host system,
restart the host system.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
Off The virtual machine does not use the enhanced virtual keyboard feature.
This is the default value.
Use if available (recommended) The virtual machine uses the enhanced virtual keyboard feature, but only if
the enhanced virtual keyboard driver is installed on the host system.
Required The virtual machine must use the enhanced the virtual keyboard feature. If
you select this option and the enhanced keyboard driver is not installed on
the host system, Workstation Player returns an error message.
Prerequisites
Procedure
1 Log in to the Windows host system as the Administrator user or as a user who is a member
of the local Administrators group.
If you log in to a domain, the domain account must also be a local administrator.
3 Select Modify/Change.
What to do next
Enable the enhanced virtual keyboard feature for the virtual machine. See Use the Enhanced
Virtual Keyboard Feature in a Virtual Machine.
Procedure
1 Press Ctrl+Alt+spacebar.
3 Press the third key of the key combination to send to the guest operating system.
For local X servers, Workstation Player maps X key codes to PC scan codes to correctly identify
a key. Because it cannot tell whether a remote X server is running on a PC or on some other kind
of computer, Workstation Player uses this key code map only for local X servers. You can set a
property to tell Workstation Player to use key code mapping. See Understanding X-Key Codes
and Keysyms for more information.
To configure a keyboard mapping for a remote X server, you add the appropriate property to
the virtual machine configuration (.vmx) file or to ~/.vmware/config.
Prerequisites
Note If the keyboard does not work correctly on an XFree86 server running locally, report the
problem to VMware technical support.
Procedure
u If you use an XFree86-based server that Workstation Player does not recognize as an
XFree86 server, add the xkeymap.usekeycodeMap property and set it to TRUE.
This property tells Workstation Player to always use key code mapping regardless of server
type.
For example: xkeymap.usekeycodeMap = "TRUE"
u If Workstation Player does not recognize the remote server as an XFree86 server, add the
xkeymap.usekeycodeMapIfXFree86 property and set it to TRUE.
This property tells Workstation Player to use key code mapping if you are using an XFree86
server, even if it is remote.
For example: usekeycodeMapIfXFree86 = "TRUE"
Internally, Workstation Player uses a simplified version of the PC scan code that is a single nine-
bit numeric value, called a v-scan code. A v-scan code is written as a three-digit hexadecimal
number. The first digit is 0 or 1. For example, the Ctrl key on the left side of the keyboard has a
one-byte scan code (0x1d) and its v-scan code is 0x01d. The Ctrl key scan code on the right side
of the keyboard is two bytes (0xe0, 0x1d) and its v-scan code is 0x11d.
An XFree86 server on a PC has a one-to-one mapping from X key codes to PC scan codes, or v-
scan codes, which is what Workstation Player uses. When Workstation Player is hosted on an
XFree86 server and runs a local virtual machine, it uses the built-in mapping from X key codes to
v-scan codes. This mapping is keyboard independent and should be correct for most languages.
In other cases (not an XFree86 server or not a local server), Workstation Player must map
keysyms to v-scan codes by using a set of keyboard-specific tables.
An X server uses a two-level encoding of keys, which includes the X key code and the keysym.
An X key code is a one-byte value. The assignment of key codes to keys depends on the X
server implementation and the physical keyboard. As a result, an X application normally cannot
use key codes directly. Instead, the key codes are mapped into keysyms that have names like
space, escape, x and 2. You can use an X application to control the mapping by using the
function XChangeKeyboardMapping() or by the program xmodmap. To explore keyboard mappings,
you can use the xev command, which shows the key codes and keysyms for keys typed into its
window.
A key code corresponds roughly to a physical key, while a keysym corresponds to the symbol on
the key top. For example, with an XFree86 server running on a PC, the Z key on the German
keyboard has the same key code as the Y key on an English keyboard. The German Z keysym,
however, is the same as the English Z keysym, and different from the English Y keysym.
Prerequisites
n Verify that the X server is an XFree86 server running on a PC. If the X server is remote,
configure it to use key code mapping. See Configure Keyboard Mapping for a Remote X
Server.
n Determine the X key code and the corresponding v-scan code for the key. To find the X key
code for a key, run xev or xmodmap -pk. See V-Scan Code Table for most v-scan codes.
Procedure
code must be a decimal number and the v-scan code must be a C-syntax hexadecimal
number, such as 0x001.
In this example, the properties swap left Ctrl and Caps Lock.
Workstation Player determines which table to use by examining the current X keymap. However,
its decision-making process can sometimes fail. In addition, each mapping is fixed and might not
be completely correct for any given keyboard and X key code-to-keysym mapping. For example,
if a user uses xmodmap to swap Ctrl and Caps Lock by, the keys are swapped in the virtual
machine when using a remote server (keysym mapping), but are unswapped when using a local
server (key code mapping). To correct this situation, you must remap the keys in Workstation
Player.
To configure how keysyms are mapped, you add one or more properties to the virtual machine
configuration (.vmx) file or to ~/.vmware/config.
Prerequisites
n To change the mapping of a few keys, determine the keysym name for each key. To find a
keysym name, use the xev or xmodmap -pk command. The X header file /usr/include/X11/
keysymdef.h also has a complete list of keysyms. The name of a keysym is the same as its C
constant, but without the XK_ prefix.
n To use a different keysym table, determine which mapping table to use. The tables are
located in the xkeymap directory in the Workstation Player installation directory, which is
usually /usr/lib/vmware. The table you must use depends on the keyboard layout. The
normal distribution includes tables for PC keyboards for the United States and a number of
European countries and languages. For most of these, both the 101-key (or 102-key) and the
104-key (or 105-key) variants are available.
If none of the mapping tables is completely correct, find one that works best, copy it to a new
location, and change the individual keysym mappings.
n Familiarize yourself with the v-scan codes. See V-Scan Code Table.
Procedure
u To disable X key code mapping to map keysyms rather than key codes to v-scan codes, add
the xkeymap.nokeycodeMap property and set it to TRUE.
u If Workstation Player has a table in the xkeymap directory for your keyboard but cannot
detect it, add the xkeymap.language property and set it to one of the tables in the xkeymap
directory.
u To use a different keysym mapping table that is not in the xkeymap directory, add the
xkeymap.fileName property and set it to the path to the table.
Note Because compiling a complete keysym mapping is difficult, you should usually edit an
existing table and make small changes.
u To change the keysym mapping of a few keys, type the xkeymap.keysym property for each
key, on separate lines.
Following are the v-scan codes for the 104-key U.S. keyboard.
Esc 0x001
1 ! 0x002
2 @ 0x003
3 # 0x004
4 $ 0x005
5 % 0x006
6 ^ 0x007
7 & 0x008
8 * 0x009
9 ( 0x00a
0 ) 0x00b
- _ 0x00c
= + 0x00d
Backspace 0x00e
Tab 0x00f
Q 0x010
W 0x011
E 0x012
R 0x013
T 0x014
Y 0x015
U 0x016
I 0x017
O 0x018
P 0x019
Table 12-1. V-Scan Codes for the 104-Key U.S. Keyboard (continued)
Symbol Shifted Symbol Location V-Scan Code
[ { 0x01a
] } 0x01b
Enter 0x01c
A 0x01e
S 0x01f
D 0x020
F 0x021
G 0x022
H 0x023
J 0x024
K 0x025
L 0x026
; 0x027
' 0x028
` 0x029
\ | 0x02b
Z 0x02c
X 0x02d
C 0x02e
V 0x02f
B 0x030
N 0x031
M 0x032
, < 0x033
. > 0x034
/ ? 0x035
F1 0x03b
Table 12-1. V-Scan Codes for the 104-Key U.S. Keyboard (continued)
Symbol Shifted Symbol Location V-Scan Code
F2 0x03c
F3 0x03d
F4 0x03e
F5 0x03f
F6 0x040
F7 0x041
F8 0x042
F9 0x043
F10 0x044
F11 0x057
F12 0x058
Table 12-1. V-Scan Codes for the 104-Key U.S. Keyboard (continued)
Symbol Shifted Symbol Location V-Scan Code
Menu 0x15d
The 84-key keyboard has a Sys Req key on the numeric pad. Its v-scan code is 0x054.
Keyboards outside the U.S. usually have an extra key (often < > or < > |) next to the left Shift key.
The v-scan code for this key is 0x056.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
4 Click Help for information about how to modify the hardware setting.
You must power off a virtual machine before you change certain hardware settings.
Virtual Switches
Like a physical switch, a virtual switch connects networking components together. Virtual
switches, which are also referred to as virtual networks, are named VMnet0, VMnet1, VMnet2,
and so on. A few virtual switches are mapped to specific networks by default.
Bridged VMnet0
NAT VMnet8
Host-only VMnet1
Note On Linux host systems, the virtual switch names are in all lowercase letters, for example,
vmnet0.
Player 3.x and later virtual machines can have up to 10 virtual network adapters.
NAT Device
In a NAT configuration, the NAT device passes network data between one or more virtual
machines and the external network, identifies incoming data packets intended for each virtual
machine, and sends them to the correct destination.
Creating custom networks is available only on virtual machines that are created in Workstation
Player. Although you cannot configure custom networking in Workstation Player, you can run a
virtual machine that has custom networking in Workstation Player.
Bridged Networking
Bridged networking connects a virtual machine to a network by using the network adapter on the
host system. If the host system is on a network, bridged networking is often the easiest way to
give the virtual machine access to that network.
When you install Workstation Player on a Windows or Linux host system, a bridged network
(VMnet0) is set up for you. See Configuring Bridged Networking.
NAT Networking
With NAT, a virtual machine does not have its own IP address on the external network. Instead, a
separate private network is set up on the host system. In the default configuration, a virtual
machine gets an address on this private network from the virtual DHCP server. The virtual
machine and the host system share a single network identity that is not visible on the external
network.
When you install Workstation Player on a Windows or Linux host system, a NAT network
(VMnet8) is set up for you. When you use the New Virtual Machine wizard to create a new
virtual machine and select the typical configuration type, the wizard configures the virtual
machine to use the default NAT network.
You can have only one NAT network. See Configuring Network Address Translation.
Host-Only Networking
Host-only networking creates a network that is completely contained within the host computer.
Host-only networking provides a network connection between the virtual machine and the host
system by using a virtual network adapter that is visible on the host operating system.
When you install Workstation Player on a Windows or Linux host system, a host-only network
(VMnet1) is set up for you. See Configuring Host-Only Networking.
With bridged networking, the virtual network adapter in the virtual machine connects to a
physical network adapter in the host system. The host network adapter enables the virtual
machine to connect to the LAN that the host system uses. Bridged networking works with both
wired and wireless host network adapters.
Bridged networking configures the virtual machine as a unique identity on the network, separate
from and unrelated to the host system. The virtual machine is a full participant in the network. It
has access to other machines on the network, and other machines on the network can contact it
as if it were a physical computer on the network.
You can view and change the settings for bridged networking on the host system, determine
which network adapters to use for bridged networking, and map specific host network adapters
to specific virtual switches.
Typically, the guest operating system can acquire an IP address and other network details from a
DHCP server, but you might need to set the IP address and other details manually in the guest
operating system.
Users who boot multiple operating systems often assign the same address to all systems
because they assume that only one operating system will be running at a time. If the host system
is set up to boot multiple operating systems, and you run one or more operating systems in
virtual machines, you must configure each operating system to have a unique network address.
To configure bridged networking for a new virtual machine, select Customize Hardware when
you run the New Virtual Machine wizard.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
4 If you use the virtual machine on a laptop or other mobile device, select Replicate physical
network connection state.
This setting causes the IP address to be renewed when you move from one wired or wireless
network to another.
With NAT, a virtual machine does not have its own IP address on the external network. Instead, a
separate private network is set up on the host system. In the default configuration, virtual
machines get an address on this private network from the virtual DHCP server.
NAT network
device
The virtual machine and the host system share a single network identity that is not visible on the
external network. NAT works by translating the IP addresses of virtual machines in the private
network to the IP address of the host system. When a virtual machine sends a request to access
a network resource, it appears to the network resource as if the request is coming from the host
system.
The host system has a virtual network adapter on the NAT network. This adapter enables the
host system and virtual machines to communicate with each other. The NAT device passes
network data between one or more virtual machines and the external network, identifies
incoming data packets intended for each virtual machine, and sends them to the correct
destination.
connected to a private Ethernet network. The network is completely contained within the host
system.
The network connection between the virtual machine and the host system is provided by a
virtual network adapter that is visible on the host operating system. The virtual DHCP server
provides IP addresses on the host-only network.
In the default configuration, a virtual machine in a host-only network cannot connect to the
Internet. If you install the proper routing or proxy software on the host system, you can establish
a connection between the host virtual network adapter and a physical network adapter on the
host system to connect the virtual machine to a Token Ring or other non-Ethernet network.
On a Windows host computer, you can use host-only networking in combination with the Internet
Connection Sharing feature in Windows to allow a virtual machine to use the dial-up networking
adapter or other connection to the Internet on the host system. See Microsoft documentation for
information on configuring Internet Connection Sharing.
To configure host-only networking for a new virtual machine, select Customize Hardware when
you run the New Virtual Machine wizard.
Prerequisites
To connect the virtual machine to two host-only networks, add a second virtual network adapter
to the virtual machine. See Add a Virtual Network Adapter to a Virtual Machine.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Action
Use the default host-only network Select Host-only: A private network shared with the host.
(VMnet1)
Use a custom host-only network Select Custom and select the custom host-only network from the drop-
down menu.
4 To connect the virtual machine to a second host-only network, select another virtual network
adapter and select the second host-only network.
What to do next
Assign IP addresses to the virtual network adapters. To see the IP address that a host-only
network is using, use the ipconfig /all command on the Windows host.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Prerequisites
Familiarize yourself with the network configuration types. See Understanding Common
Networking Configurations.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
3 To add the virtual network adapter to the virtual machine, select Network Adapter and click
Finish.
Option Description
Bridged The virtual machine is connected to the network by using the network
adapter on the host system. The virtual machine has a unique identity on the
network, separate from and unrelated to the host system.
NAT The virtual machine and the host system share a single network identity that
is not visible on the external network. When the virtual machine sends a
request to access a network resource, it appears to the network resource as
if the request is coming from the host system.
Host-only The virtual machine and the host virtual network adapter are connected to a
private Ethernet network. The network is completely contained within the
host system.
6 Click Finish to add the virtual network adapter to the virtual machine.
8 Verify that the guest operating system is configured to use an appropriate IP address on the
new network.
a If the virtual machine is using DHCP, release and renew the lease.
b If the IP address is set statically, verify that the guest operating system has an address on
the correct virtual network.
Prerequisites
Familiarize yourself with the network configuration types. See Understanding Common
Networking Configurations.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
Bridged The virtual machine is connected to the network by using the network
adapter on the host system. The virtual machine has a unique identity on the
network, separate from and unrelated to the host system.
NAT The virtual machine and the host system share a single network identity that
is not visible on the external network. When the virtual machine sends a
request to access a network resource, it appears to the network resource as
if the request is coming from the host system.
Host-only The virtual machine and the host virtual network adapter are connected to a
private Ethernet network. The network is completely contained within the
host system.
Custom Select a custom network from the drop-down menu. Although VMnet0,
VMnet1, and VMnet8 might be available in this list, these networks are
usually used for bridged, host-only, and NAT networks.
LAN segment Select a LAN segment from the drop-down menu. A LAN segment is a
private network that is shared by other virtual machines.
5 Verify that the guest operating system is configured to use an appropriate IP address on the
new network.
a If the virtual machine is using DHCP, release and renew the lease.
b If the IP address is set statically, verify that the guest operating system has an address on
the correct virtual network.
Jumbo frames let you send larger frames out onto the physical network or between virtual
machines on the same host.
Procedure
1 Navigate to Control Panel > Network and Internet > Network Connections.
2 In the Network Connections window, right-click a VMware network adapter and select
Properties. Click Configure on the Networking tab.
3 In the new window that appears, select the Advanced tab and select Jumbo Packet.
4 In the Value drop-down menu, select the packet size and click Ok.
Results
To configure virtual machine option settings for a selected virtual machine, select Player >
Manage > Virtual Machine Settings and click the Options tab.
To configure general option settings for a selected virtual machine, select Player > Manage >
Virtual Machine Settings, click the Options tab, and select General.
To specify a new name for a selected virtual machine, select Player > Manage > Virtual Machine
Settings, click the Options tab, and select General.
To select a new guest operating system or operating system version for a selected virtual
machine, select Player > Manage > Virtual Machine Settings, click the Options tab, and select
General.
When you change the operating system type, the virtual machine configuration file is changed
but the guest operating system is not changed. To change the guest operating system, you must
obtain the operating system software and upgrade the guest operating system.
The virtual machine must be powered off when you change these settings.
To specify a new working directory for a selected virtual machine, select Player > Manage >
Virtual Machine Settings, click the Options tab, and select General.
You might want to change the working directory in the following situations.
n To run a virtual machine that is stored on a network share or iPod, which might slow
performance, you can change the working directory to your local hard disk.
n To create a paging file on a fast disk with a lot of disk space but leave the virtual disk and
configuration file on a different disk, you can change the working directory so that it is
located on the fast disk.
Changing the working directory does not change the directory where Workstation Player stores
the virtual machine configuration (.vmx) file and log files.
The virtual machine must be powered off when you change this setting.
Because it processes raw keyboard input as soon as possible, the enhanced virtual keyboard
feature also offers security improvements by bypassing Windows keystroke processing and any
malware that is not already at a lower layer. When you use the enhanced virtual keyboard
feature, only the guest operating system acts when you press Ctrl+Alt+Delete.
Prerequisites
n If you recently installed or upgraded Workstation Player, but did not restart the host system,
restart the host system.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
Option Description
Off The virtual machine does not use the enhanced virtual keyboard feature.
This is the default value.
Use if available (recommended) The virtual machine uses the enhanced virtual keyboard feature, but only if
the enhanced virtual keyboard driver is installed on the host system.
Required The virtual machine must use the enhanced the virtual keyboard feature. If
you select this option and the enhanced keyboard driver is not installed on
the host system, Workstation Player returns an error message.
To configure power options for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Options tab, and select Power.
Enter full screen mode after powering on The virtual machine window enters full screen mode after it is powered on.
Report battery information to guest Battery information is reported to the guest operating system. If you run
the virtual machine on a laptop in full screen mode, this option enables you
to determine when the battery is running low. This option is available only
for Workstation 6.x and later virtual machines.
To configure VMware Tools updates for a selected virtual machine, select Player > Manage >
Virtual Machine Settings, click the Options tab, and select VMware Tools.
Note Automatic updates are not supported for versions of VMware Tools included in virtual
machines created with older versions of VMware products, such as Workstation 5.5 and earlier or
VMware Server 1.x.
Update manually (do nothing) You must update VMware Tools manually. A message appears
on the status bar of the guest operating system when a new
version of VMware Tools is available.
Use application default (currently update Use the default VMware Tools update behavior.
automatically)
To install a VMware Tools update, use the same procedure that you used for installing VMware
Tools the first time.
Time Synchronization
If you turn on the VMware Tools time synchronization feature, VMware Tools checks once every
minute to determine whether the clocks on the guest and host operating systems still match. If
not, the clock on the guest operating system is synchronized to match the clock on the host.
Native time synchronization software, such as Network Time Protocol (NTP) for Linux and the
Mac OS X, or Microsoft Windows Time Service (Win32Time) for Windows, is typically more
accurate than VMware Tools periodic time synchronization and is therefore preferred.
To configure Unity mode settings for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Options tab, and select Unity.
Show borders Set a window border that identifies the application as belonging to the
virtual machine rather than to the host computer.
Use a custom color in window borders To help distinguish between the application windows that belong to
various virtual machines, use a custom color in window borders. For
example, you can set the applications for one virtual machine to have a
blue border and set the applications for another virtual machine to have
a yellow border. On Windows hosts, click Choose color to use the color
chooser.
Enable applications menu The virtual machine Start or Applications menu appears on the host
system desktop.
When you can access the virtual machine Start or Applications menu
from the host machine desktop, you can start applications in the virtual
machine that are not open in Unity mode. If you do not enable this
setting, you must exit Unity mode to display the virtual machine Start or
Applications menu in the console view.
To configure Autologin for a selected virtual machine, select Player > Manage > Virtual Machine
Settings, click the Options tab, and select Autologin.
When you enable Autologin, you must type your login credentials. If you type an incorrect or
expired password, you must type your login credentials when you power on the virtual machine.
To change your login credentials, select Change User.
Note When you enable Autologin or change your login credentials, Autologin settings are saved
immediately. If you click Cancel in the Virtual Machine Settings dialog box, the changes applied to
the Autologin settings are not affected.
To configure hardware settings for a selected virtual machine, select Player > Manage > Virtual
Machine Settings and click the Hardware tab. When you select a device in the left pane, the
configuration options for that device appear in the right pane.
To add hardware to a selected virtual machine, select Player > Manage > Virtual Machine
Settings, click the Hardware tab, and click Add.
Note You cannot add hardware to a virtual machine while it is in a suspended state.
The Add Hardware wizard prompts you to select the type of device that you want to add and to
specify device-specific configuration settings. You can modify many of the configuration settings
after the device is created by changing virtual machine hardware settings.
A virtual hard disk is a set of files that appears as a physical disk drive to the guest operating
system. You can configure a virtual hard disk as an IDE, SCSI, SATA, or NVMe device. You can
add up to 4 IDE devices, up to 60 SCSI devices, up to 120 SATA devices (4 controllers and 30
devices per controller), and up to 60 NVMe devices (4 controllers and 15 devices per
controller) to a virtual machine. You can also give a virtual machine direct access to a physical
disk.
You can configure a virtual CD-ROM or DVD drive as an IDE, SCSI, or SATA device. You can
add up to 4 IDE devices, up to 60 SCSI devices, and up to 120 SATA devices (4 controllers
and 30 devices per controller). You can connect virtual CD-ROM and DVD drives to a physical
drive on the host system or to an ISO image file.
Floppy drives
You can add up to two floppy drives. A virtual floppy drive can connect to a physical drive on
the host system, to an existing floppy image file, or to a blank floppy image file.
Network adapters
USB controller
You can add one USB controller to a virtual machine. A virtual machine must have a USB
controller to use USB devices or smart card readers. For smart card readers, a virtual
machine must have a USB controller regardless of whether the smart card reader is actually a
USB device.
Sound card
If the host system is configured for sound and has a sound card installed, you can enable
sound for virtual machines.
You can attach up to three bidirectional parallel ports to a virtual machine. Virtual parallel
ports can output to parallel ports or to files on the host operating system.
You can add up to four serials ports to a virtual machine. Virtual serial ports can output to
physical serial ports, files on the host operating system, or named pipes.
Printers
You can print from a virtual machine to any printer available to the host system without
installing additional drivers in the virtual machine. Workstation Player uses ThinPrint
technology to replicate the host machine printer mapping in the virtual machine. When you
enable the virtual machine printer, Workstation Player configures a virtual serial port to
communicate with the host printers.
You can add up to 60 SCSI devices to a virtual machine. A generic SCSI device gives the
guest operating system direct access to a SCSI device connected to the host system. Generic
SCSI devices can include scanners, tape drives, CD-ROM drives, and DVD drives.
To remove hardware from a selected virtual machine, select Player > Manage > Virtual Machine
Settings, click the Hardware tab, and click Remove.
Note You cannot remove hardware from a virtual machine while it is in suspended state.
You can remove the following types of devices from a virtual machine.
n Floppy drives
n USB controllers
n Sound cards
n Printers
You cannot remove the Memory, Processors, and Display device types.
You must power off a virtual machine before you remove a virtual network adapter, sound card,
parallel port, serial port, or generic SCSI device. You must also power off Workstation 5 virtual
machines before you remove a USB controller.
To adjust the memory allocation for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Hardware tab, and click Memory.
The Memory panel includes information to help you select the appropriate amount of memory for
the virtual machine. The high end of the range is determined by the amount of memory that is
allocated to all running virtual machines. If you allow virtual machine memory to be swapped, this
value changes to reflect the specified amount of swapping.
The color-coded icons on the Memory panel indicate the maximum recommended memory, the
recommended memory, and the guest operating system recommended minimum memory
amounts. To adjust the memory, move the slider along the range of values, or type a value in the
Memory for this virtual machine text box.
Note Allocating more than the maximum memory to a virtual machine might cause memory
swapping. It can also negatively affect host system performance, including the ability to run
Workstation Player.
To configure processor settings for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Hardware tab, and select Processors.
Number of cores per processor Select the number of cores per processor.
Workstation Player supports up to 16-way virtual Symmetric
Multiprocessing (SMP) for guest operating systems running on
multiprocessor host machines. You can assign processors and cores per
processor to a virtual machine on any host machine that has at least two
logical processors.
Virtualize Intel VT-x/EPT or AMD-V/RVI Workstation Player forces the virtual machine execution mode to VT-
x/EPT or AMD-RVI. Physical Address Extension (PAE) mode must be
enabled to use virtualized AMD-V/RVI.
If the execution mode is not supported by the host system, virtualized
VT-x/EPT or AMD/RVI is not available. If you migrate the virtual machine
to another VMware product, virtualized VT-x/EPT or AMD-V/RVI might
not be available.
Virtualize CPU performance counters Turn on this feature if you plan to use performance monitoring
applications such as VTune or OProfile to optimize or debug software
that runs inside the virtual machine.
This feature is available only if the virtual machine compatibility is
Workstation 9 or later.
To perform actions on a virtual hard disk for a selected virtual machine, select Player > Manage >
Virtual Machine Settings, click the Hardware tab, and select the virtual hard disk.
There must be adequate free working space on the host system to defragment a virtual hard
disk. If the disk is contained in a single file, for example, you need free space equal to the size of
the disk file. Other virtual hard disk configurations require less free space. You cannot
defragment a virtual hard disk while it is mapped or mounted.
To defragment a virtual hard disk for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Hardware tab, select the virtual hard disk, and select Defragment
from the Utilities menu.
When you expand a virtual hard disk, the added space is not immediately available to the virtual
machine. To make the added space available, you must use a disk management tool to increase
the size of the existing partition on the virtual hard disk to match the expanded size.
The disk management tool that you use depends on the virtual machine guest operating system.
Many operating systems, including Windows 7 and later, and many versions of Linux, provide
built-in disk management tools that can resize partitions. Third-party disk management tools are
also available, such as Symantec/Norton PartitionMagic, EASEUS Partition Master, Acronis Disk
Director, and the open-source tool GParted.
When you expand the size of a virtual hard disk, partition and file-system size are not affected.
To expand a virtual hard disk for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, select the virtual hard disk, and select Expand from the Utilities menu.
Note As an alternative to expanding a virtual hard disk, you can add a new virtual hard disk to
the virtual machine.
You cannot compact a virtual hard disk if disk space is preallocated or if the virtual hard disk is
mapped or mounted.
To compact a virtual hard disk for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Hardware tab, select the virtual hard disk, and select Compact from
the Utilities menu.
After you map the virtual disk to a drive on the host system, you cannot power on any virtual
machine that uses the disk until you disconnect the disk from the host system.
Important If you mount a virtual disk that has a snapshot and then write to the disk, you can
irreparably damage a snapshot or linked clone created from the virtual machine. Note that
Workstation Player does not support taking snapshots or deleting them.
Mapping a virtual disk to a host system is not supported in the standalone version of Workstation
Player. Virtual disk mapping is supported in the Workstation Player version included with
Workstation Pro.
Prerequisites
n Power off all virtual machines that use the virtual disk.
n Verify that the virtual disk (.vmdk) files on the virtual disk are not compressed and do not
have read-only permissions.
n On a Windows host, verify that the volume is formatted with FAT (12/16/32) or NTFS. Only
FAT (12/16/32) and NTFS formatting is supported. If the virtual disk has mixed partitions, for
example, one partition is formatted with a Linux operating system and another partition is
formatted with a Windows operating system, you can map the Windows partition only.
n Verify that the virtual disk is unencrypted. You cannot map or mount encrypted disks.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
2 On the Hardware tab, select Hard Disk, click Utilities, and select Map.
3 On a Windows host, leave the check box Open file in read-only mode selected in the Map
Virtual Disk dialog box.
This setting prevents you from accidentally writing data to a virtual disk that might be the
parent of a snapshot or linked clone. Writing to such a disk might make the snapshot or
linked clone unusable.
4 Browse to a virtual disk (.vmdk) file, select it, and click Open.
5 Select the volume to map or mount and select an unused drive letter on the host system.
6 (Optional) On a Windows host, if you do not want the drive to open in Windows Explorer
after it is mapped, deselect the Open drive in Windows Explorer after mapping check box.
7 Click OK or Mount.
The drive appears on the host system. You can read from or write to files on the mapped
virtual disk on the host system.
On Windows hosts, you must use Workstation Player to disconnect the drive from the host
system. The mapped drive letter does not appear in the list of network drives when you use the
Windows Disconnect Network Drive command.
Procedure
1 Select the virtual machine and select Player > Manage > Virtual Machine Settings.
2 On the Hardware tab, select Hard Disk, click Utilities, and select Disconnect.
Results
You can now power on any virtual machine that uses this disk.
To change the node and mode settings for a virtual hard disk on a selected virtual machine,
select Player > Manage > Virtual Machine Settings, click the Hardware tab, select the virtual
hard disk, and click Advanced. By default, changes are immediately written to the disk.
Virtual device node Select the SCSI, IDE, SATA, or NVMe device identifier to use for the drive. For
example, if you select SCSI 0:2, the guest operating system detects the drive as ID 2
on controller 0. You determine whether the virtual disk is seen as a SCSI, IDE, SATA,
or NVMe device at the time that you create it.
To configure CD-ROM and DVD drive settings for a selected virtual machine, select Player >
Manage > Virtual Machine Settings, click the Hardware tab, and select the drive.
To configure device status and connection settings for a selected virtual machine, select Player >
Manage > Virtual Machine Settings, click the Hardware tab, and select the drive.
Connected Connect the drive or ISO image file while the virtual machine is running.
Connect at power on Connect the drive or ISO image path when you power on the virtual machine.
Use physical drive Select a specific drive or select Auto detect to allow Workstation Player to
detect a drive to use.
Use ISO image file Specify or select an ISO image file for the virtual machine to use.
To disable or enable access to a CD-ROM or DVD drive while a virtual machine is running, select
the virtual machine, select Player > Removable Devices > CD/DVD, and select Disconnect or
Connect.
To configure virtual device and legacy emulation settings for a selected virtual machine, select
Player > Manage > Virtual Machine Settings, click the Hardware tab, select the drive, and click
Advanced.
Use the settings to select which SCSI, IDE, SATA, or NVMe device identifier to use for the drive.
For example, if you select SCSI 0:2, the guest operating system detects the drive as ID 2 on
controller 0. You can select the IDE, SCSI, SATA, or NVMe node options regardless of the
physical device type. For example, if the physical drive is an IDE device, you can select a SCSI
node. In this case, the virtual machine detects the drive as a SCSI device.
If you select the Legacy emulation setting, the virtual hardware works as it did in an earlier
release of Workstation Player. By default, Workstation Player attempts to make the advanced
features of your drive available, but sometimes this setting might cause the drive to not work
with the virtual machine. Selecting the Legacy emulation setting reverts Workstation Player to
the previous emulation mode for the drive. Legacy emulation is helpful for troubleshooting
purposes.
To configure floppy drive settings for a selected virtual machine, select Player > Manage >
Virtual Machine Settings, click the Hardware tab, and select the floppy drive.
Connected Connect the drive or floppy image file while the virtual machine is running.
Connect at power on Connect the floppy drive when you power on the virtual machine.
Use a physical drive Select a specific floppy drive or select Auto detect to allow Workstation Player
to detect a drive to use.
Use a floppy image file Create or browse to a floppy image (.img or .flp) file. Select Read only to
prevent changes from being made to the file.
To disable or enable access to a floppy drive while a virtual machine is running, select the virtual
machine, select Player > Removable Devices > Floppy, and select Disconnect or Connect.
To configure virtual network adapter settings for a selected virtual machine, select Player >
Manage > Virtual Machine Settings, click the Hardware tab, and select the virtual network
adapter.
To configure virtual network adapter device status settings for a selected virtual machine, select
Player > Manage > Virtual Machine Settings, click the Hardware tab, and select the virtual
network adapter.
Connected Connect the virtual network adapter while the virtual machine is running.
Connect at power on Connect the virtual network adapter when you power on the virtual machine.
If the host system is on a network, bridged networking is often the easiest way to give a virtual
machine access to that network.
With bridged networking, the virtual machine appears as an additional computer on the same
physical Ethernet network as the host system. The virtual machine can transparently use the
services available on the network, including file servers, printers, and gateways. Physical hosts
and other virtual machines configured with bridged networking can also use the resources of the
virtual machine.
When you use bridged networking, the virtual machine must have its own identity on the
network. For example, on a TCP/IP network, the virtual machine must have its own IP address.
Virtual machines typically acquire an IP address and other network details from a DHCP server. In
some configurations, you might need to set the IP address and other details manually.
Users who boot multiple operating systems often assign the same address to all systems
because they assume that only one operating system will be running at the same time. If the host
system is set up to boot multiple operating systems and you run one or more of them in virtual
machines, configure each operating system with a unique network address.
When the Replicate physical connection state option is selected, the IP address is automatically
renewed when you move from one wired or wireless network to another. This setting is useful for
virtual machines than run on laptops or other mobile devices.
To change automatic bridging settings, select Player > Virtual Machine Settings > Network
Adapter > Configure Adapters, select the host network adapter(s) to automatically bridge, and
click OK.
By default, a virtual switch bridges to all active network adapters on the host system when it is
configured for automatic bridging. The choice of which adapter to use is arbitrary.
To prevent a virtual switch from bridging to a particular physical network adapter, deselect the
check box for that host network adapter.
The virtual machine and the host system share the a single identity that is not visible outside the
network. The virtual machine does not have its own IP address. Instead, a separate private
network is set up on the host system and the virtual machine obtains an address on that network
from the VMware virtual DHCP server. The VMware NAT device passes network data between
one or more virtual machines and the external network. The VMware NAT device identifies
incoming data packets that are intended for each virtual machine and sends them to the correct
destination.
With NAT, a virtual machine can use many standard protocols to connect to other machines on
the external network. For example, you can use HTTP to browse Web sites, FTP to transfer files,
and Telnet to log in to other systems. You can also connect to a TCP/IP network by using a
Token Ring adapter on the host system.
In the default configuration, systems on the external network cannot initiate connections to the
virtual machine. For example, the default configuration does not let you use the virtual machine
as a Web server to send Web pages to systems on the external network. This limitation protects
the guest operating system from being compromised before you can install security software.
By default, NAT is used when you use the New Virtual Machine wizard to create a virtual
machine.
The virtual machine uses NAT to connect to the Internet or other TCP/IP network by using the
networking connection on the host system. NAT works with Ethernet, DSL, and phone modems.
A separate private network is set up on the host system. The virtual machine obtains an address
on that network from the VMware virtual DHCP server.
A VPN is typically not visible outside the host system. Multiple virtual machines configured with
host-only networking on the same host system are on the same network. The VMware DHCP
server provides addresses on the network.
If you install the proper routing or proxy software on the host system, you can establish a
connection between the host virtual network adapter and a physical network adapter on the host
system. With this configuration, you can connect the virtual machine to a Token Ring or other
non-Ethernet network.
On Windows host systems, you can use host-only networking in combination with the Internet
Connection Sharing feature in Windows. With this combination, the virtual machine can use the
dial-up networking adapter on the host system or another connection to the Internet. See the
Windows documentation for more information on Internet Connection Sharing.
If you add an existing virtual machine to a LAN segment, the virtual machine might be configured
to expect an IP address from a DHCP server. Unlike host-only and NAT networking, Workstation
Player does not provide a DHCP server for LAN segments. You must manually configure IP
addressing for virtual machines on a LAN segment. You can either configure a DHCP server on
the LAN segment to allocate IP addresses, or you can configure a fixed IP address for each
virtual machine on the LAN segment.
You can click LAN Segments to create new LAN segments or delete and rename existing LAN
segments. Deleting a LAN segment disconnects all virtual network adapters that are configured
for that LAN segment. When you delete a LAN segment, you must manually configure its
disconnected virtual network adapter to reconnect the virtual machine to the network.
The advanced virtual network adapter settings allow you to simulate a network environment that
differs from your own.
To configure advanced virtual network adapter settings for a selected virtual machine, select
Player > Manage > Virtual Machine Settings, click the Hardware tab, select the virtual network
adapter, and click Advanced.
Bandwidth and Kbps To limit incoming or outgoing data transfers to the data transfer rate for a
specific network connection type, select the network connection type from the
Bandwidth drop-down menu. The value in the Kbps text box changes to the
data transfer rate, in kilobits per second, of the network connection type that
you select. For example, if you select Leased Line T1 (1.544 Mbps), the value in
the Kbps text box changes to 1544.
To limit incoming or outgoing data transfers to a specific data transfer rate,
select Custom and type the data transfer rate in kilobits per second in the Kbps
text box.
The default bandwidth setting for both incoming and outgoing data transfers is
Unlimited.
Packet Loss (%) The acceptable packet loss percentage for incoming or outgoing data transfers.
The default setting is 0.0%.
Latency (ms) To simulate network latency for incoming and outgoing data transfers, set the
number of milliseconds (ms) of latency. The latency range is 0 to 2,000 ms.
MAC Address To assign a new MAC address to the network adapter, either type a new
address in this text box or click Generate to have Workstation Player generate a
new address.
To configure USB controller settings for a selected virtual machine, select Player > Manage >
Virtual Machine Settings, click the Hardware tab, and click USB Controller.
USB Compatibility Selecting USB 2.0 or 3.0 enables support for isochronous USB
devices, including Web cams, speakers, and microphones.
Show all USB input devices Human interface devices (HIDs), such as USB 1.1 and 2.0 mouse
and keyboard devices, appear in the Removable Devices menu.
Icons for HIDs appear in the status bar. An HID that is connected to
the guest operating system is not available to the host system. The
virtual machine must be powered off when you change this
setting.
Share Bluetooth devices with the virtual machine Enable support for Bluetooth devices.
To connect or disconnect USB devices while a virtual machine is running, select the virtual
machine and select Player > Removable Devices. With the two-port USB controller, you can
connect to both USB 1.1 and USB 2.0 devices.
Important Before you unplug a USB device or select a removable device to disconnect a USB
device from a virtual machine, follow the device manufacturer's procedures for safely unplugging
the device from a physical computer.
To configure sound card settings for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Hardware tab, and click Sound Card.
Connected Connect the sound device while the virtual machine is running.
Connect at power on Connect the sound device when you power on the virtual machine.
Use default host sound card Make the virtual machine use the default sound card in the host system.
Specify host sound card (Windows hosts only) Select a specific host sound card for the virtual machine
to use.
Use physical sound card (Linux hosts only) Select a specific host sound card to for the virtual machine to
use.
Enable Echo Cancellation Enable echo cancellation for the sound card.
To configure parallel port settings for a selected virtual machine, select Player > Manage >
Virtual Machine Settings, click the Hardware tab, and select the parallel port.
Connect at power on Connect the port when you power on the virtual machine.
If the guest operating system cannot access the parallel port device
when you power on the virtual machine, deselect this setting. You can
use the Removable Devices menu to enable access to the parallel port
after the virtual machine is powered on.
Use a physical parallel port Select a host parallel port for the virtual machine to use.
Use output file Send output from the virtual parallel port to a file on the host system.
Either locate an existing output file or browse to a directory and type a
filename to create a new output file.
To configure serial port settings for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Hardware tab, and select the serial port.
Connect at power on Connect the port when you power on the virtual machine.
Use output file Send output from the virtual serial port to a file on the host system.
Either locate an existing output file or navigate to the desired
directory and type a filename for the file to create.
Use named pipe or Use socket (named pipe) Set up a direct connection between two virtual machines or a
connection between a virtual machine and an application on the host
system.
(Windows hosts) Use the default pipe name, or enter another pipe
name. The pipe name must begin with \\.\pipe\ and must be the
same on both the server and the client. For example:
\\.\pipe\\ namedpipe
Yield CPU on poll The guest operating system uses the port in polled mode rather than
interrupt mode. It yields processor time if its only task is to poll the
virtual serial port.
If the guest operating system uses the serial port in interrupt mode,
do not select this setting.
Note This setting is useful for developers who are using debugging
tools that communicate over a serial connection. Selecting this
setting can improve performance when the guest operating system
uses the serial port in polled mode.
To configure generic SCSI device settings for a selected virtual machine, select Player > Manage
> Virtual Machine Settings, click the Hardware tab, and select the generic SCSI device.
Connect at power on Connect the device when you power on the virtual machine.
Specify the physical SCSI device to connect to Select a host SCSI device.
(Windows hosts) Select a device. The menu shows the SCSI
devices that are available on the host system.
(Linux hosts) Type the name of the /dev/sg entry for the device
to install in the virtual machine. For example, if the device is
named sga, type /dev/sga.
Virtual device node Select the SCSI device identifier to use for the drive. For
example, if you select SCSI 0:2, the guest operating system
sees the drive as ID 2 on controller 0.
The virtual machine must be powered off when you change this
setting.
Note For specific Windows guest operating systems, you might need to perform additional
configuration steps to use a generic SCSI device.
To configure printer settings for a selected virtual machine, select Player > Manage > Virtual
Machine Settings, click the Hardware tab, and select Printer.
Connect at power on Connect the printer when you power on the virtual machine.
To configure display settings for a virtual machine, select the virtual machine, select Player >
Manage > Virtual Machine Settings, click the Hardware tab, and select Display.
Accelerate 3D graphics Select this setting if you run applications that use DirectX 9 or DirectX 10
accelerated graphics. Accelerated graphics capabilities apply to Windows
XP or later guests on hosts running Windows or Linux.
The virtual machine must be a Player 3.x or later virtual machine and must
have the latest VMware Tools installed.
Use host setting for monitors When you select this setting, the SVGA driver uses two monitors, a
maximum bounding box width of 3840, and a maximum bounding box
height of 1920. The virtual machine is configured to have a minimum of
two 1920x1200 monitors, in a side-by-side topology, in both normal and
rotated orientations. If the host system has more than two monitors, the
virtual machine uses the number of monitors on the host system instead. If
the host system's bounding box is wider or taller than the defaults, the
virtual machine uses the larger size. You should select this setting in most
cases.
Specify monitor settings Set the number of monitors that the virtual machine will see, regardless of
the number of monitors on the host system. This setting is useful if you
use a multimonitor host system and you need to test in a virtual machine
that has only one monitor. It is also useful if you are developing a
multimonitor application in a virtual machine and the host system has only
one monitor. After you power on the virtual machine, the guest operating
system sees the number of monitors that you specified. Select a
resolution from the list or type a setting that has the format width x
height, where width and height are the number of pixels.
Graphics memory Select the maximum amount of guest memory that can be used for
graphics memory using the drop down menu. The default value of video
memory varies by guest OS.
Display Scaling Enables display scaling for the virtual machine display. The user interface
is automatically adjusted when the display changes.
A physical disk directly accesses an existing local disk or partition. You can use physical disks to
run one or more guest operating systems from existing disk partitions.
Running an operating system natively on the host system and switching to running it inside a
virtual machine is similar to pulling the hard drive out of one computer and installing it in a second
computer that has a different motherboard and hardware. The steps you take depend on the
guest operating system in the virtual machine. In most cases, a guest operating system that is
installed on a physical disk or unused partition cannot boot outside of the virtual machine, even
though the data is available to the host system. See the Dual-Boot Computers and Virtual
Machines technical note on the VMware Web site for information about using an operating
system that can also boot outside of a virtual machine.
After you configure a virtual machine to use one or more partitions on a physical disk, do not
modify the partition tables by running fdisk or a similar utility in the guest operating system. If
you use fdisk or a similar utility on the host operating system to modify the partition table of the
physical disk, you must recreate the virtual machine physical disk. All files that were on the
physical disk are lost when you modify the partition table.
Important You cannot use a physical disk to share files between the host system and a guest
operating system. Making the same partition visible to both the host system and a guest
operating system can cause data corruption. Instead, use shared folder to share files between
the host system and a guest operating system.
The vctl is a command-line utility bundled inside the Workstation Player application, it is
supported only on Windows 10 1809 or later. Workstation Player on hosts with Linux OS or
Windows OS earlier than Windows 10 1809 don't support the vctl CLI.
Related executables come bundled in the Workstation Player application and are available in
C:\Program Files (x86)\VMware\VMware Player folder by default.
The three executables of the vctl command-line utility are summarized in the following section.
containerd.exe
This is a runtime daemon that runs in the background. The containerd daemon must be started
first before you can run any container related operation. To start it, use the vctl system start
command and to stop it use the vctl system stop command.
containerd-shim-crx-v2.exe
When a new container is started, a new containerd-shim-crx-v2 process is launched and works
as an adapter between the container in CRX VM and the containerd daemon.
bin/vctl.exe
It is a command-line utility that runs in the foreground and relays the user input to the containerd
daemon.
Note The vctl CLI runs every container inside a lightweight virtual machine, called CRX VM. By
default, a CRX VM is created and starts up when a container starts. It shuts down and is removed
when the container stops. The name of the CRX VM is same as the container.
Prerequisites
n VMware recommends the use of modern solid-state drive (SSD) as system disk.
n Before using vctl to run any operation on a container image or container, the container
runtime must be started first. The container runtime doesn't start automatically when
Workstation Player application launches, and does not stop automatically when Workstation
Player application quits. You must manually run the vctl system start command to start it
and run vctl system stop command to stop it.
Procedure
2 Run the vctl system info command to check the status of the container runtime.
If the command output displays Container runtime is stopped, run vctl system start
command to start the container runtime.
If the command output shows Container runtime is running, you can start using vctl to
manage containers and container images.
Prerequisites
By default, vctl assigns 2 GB memory for every CRX VM that hosts the vctl container node.
Ensure that your physical machine has 2 GB free memory when running single-node cluster, 4 GB
free memory when running two-node cluster. The more nodes configured in your cluster, the
more free memory is needed.
Procedure
2 Run the vctl system start command to start the vctl container runtime.
b Downloads kubectl.exe, kind.exe and crx.vmdk files, and saves them to the bin folder.
4 The vctl-based KIND context will be lost if you close the window.
Next time you want to interact with the Kubernetes clusters, run the vctl kind command.
Note
n vctl does not support kind build and kind export logs kind subcommands.
n By default, vctl assigns 2 GB memory and 2 CPU cores for the CRX VM that hosts the
node container, you can use the --k8s-cpus and --k8s-mem options of vctl system
config command to customize the configurations.
The following tables list vctl commands and their function. Options enclosed in square brackets
are optional. The vertical bar indicates a keyword choice.
vctl system config [OPTIONS] Configures and initializes the host OS environment for the container engine.
The command performs the following tasks:
n Creates a <Home_Folder_of_Your_Account>\.vctl folder if it doesn't exist.
n Updates the config.yaml file in the .vctl folder with the customized configurations
specified by the command options.
n Prepares the storage.
Note The vctl system config command doesn't start containerd daemon.
vctl images [OPTIONS] [IMAGE...] Lists container images and displays basic information
about the container images.
vctl push [OPTIONS] IMAGE [REMOTE_URL] Pushes the container image to the registry.
vctl tag [OPTIONS] SOURCE_IMAGE TARGET_IMAGE [TARGET_IMAGE...] Tags container images. It creates an image alias with
the TARGET_IMAGE.
vctl pull [OPTIONS] IMAGE Pulls a container image from the registry.
vctl create [OPTIONS] IMAGE [COMMAND] [ARGUMENTS...] Creates a new container from a container image.
Note Ensure the following when you use the --volume option:
n Specify paths to the folder. The --volume doesn't support
path to files.
n Use absolute path. Relative paths are not supported.
n Only anonymous volumes can be mounted, mounting named
volumes is not supported.
Note Ensure the following when you use the --publish option:
n The vctl utility doesn't have a subnet or a link feature to
connect multiple containers to a subnet.
vctl exec [OPTIONS] CONTAINER COMMAND [ARGUMENTS...] Runs a command inside a running container.
vctl ps [OPTIONS][CONTAINER...] Lists the containers and displays basic information about the
container.
vctl run [OPTIONS] IMAGE [COMMAND] [ARGUMENTS...] Runs a new container from a container image.
Note Ensure the following when you use the --volume option:
n Specify paths to the folder. The --volume doesn't support
path to files.
n Use absolute path. Relative paths are not supported.
n Only anonymous volumes can be mounted, mounting named
volumes is not supported.
Note Ensure the following when you use the --publish option:
n The vctl utility doesn't have a subnet or a link feature to
connect multiple containers to a subnet.
vctl execvm [OPTIONS] (vmx|-c=CONTAINER) COMMAND [ARGUMENTS...] Runs commands from inside a running virtual
machine that hosts the container.
Note
n On macOS, the credentials are saved in the Keychain. On Windows, the credentials are saved
in the Credential Manager.
n Once the login is successful, future Pull, Push and Build requests will leverage the saved
credential.
n Logout request deletes the corresponding credential from the Keychain or the Credential
Manager.
a Encode your Docker registry username and password in base64 with the following
command:
b Create a config.json file with your Docker registry URL and the base64 encoded string
generated in step 1.
{
"auths": {
"https://index.docker.io/v2/": {
"auth": "xxxxxxxxxxxxxxx"
}
}
}
c Build the new image whose base image is in a private Docker registry, by passing the
JSON file to vctl build command:
vctl ps
n List all containers, including the running containers and stopped containers.
vctl ps --all
n Run a container in detached mode using the nginx image, which is the same as docker.io/
library/nginx:latest.
n Run a container using the --publish option and the fluentd image, here fluentd is
equivalent to docker.io/library/fluentd:latest.
n Run multiple containers and enable discovery and communication with each other.
n The vctl utility doesn't have a subnet or a link feature to connect multiple containers to a
subnet.
To enable communication between multiple containers, start the container with the --
publish option. This binds the container port to the host port so that the service provided
by the container is accessible from the outside.
n Run a container using the --volume option and the bonita image, here bonita is equivalent to
docker.io/library/bonita:latest.
Note To get the vmx path, run the vctl describe myContainer command and refer to
the Host virtual machine value in the output.
Note To get the vmx path, run the vctl describe myContainer command and refer to
the Host virtual machine value in the output.
Procedure
1 Run the vctl system stop -f command to stop all running containers and stop container
runtime.
2 Run the vctl system info command to check if container runtime has stopped.
n The Workstation Player REST API service depends on the vmrest process.
n The vmrest service runs as the user who starts it. For example, as administrator, you can use
a terminal window to start the vmrest service.
Note To view the Workstation Player API online, search VMware API Explorer for the
appropriate version of the Workstation Player API.
Procedure
2 Before you start the REST API service the first time, set up your credentials.
a In a terminal window, change directories to the Workstation Player installation folder and
run the vmrest.exe -C command.
You do not need to set up credentials when you start the REST API on subsequent
occasions.
The user name and password are saved to the %USERPROFILE%\vmrest.cfg file.
3 Configure the REST API service for HTTP and HTTPS access.
You can configure the REST API service to provide HTTP access locally and HTTPS access
locally.
n Provide HTTP service.
The command returns the IP address and port number from which you can access the
HTTP service. The default IP address is 127.0.0.1:8697.
c Click Authorize in the top-right corner of the Workstation Player API Explorer page.
You can configure the REST API service to provide HTTPS service. In this situation, when
you use the vmrest command to start the REST API service, you must use the -c and -k
options together to specify the certificate and private key.
b To start the Workstation Player REST API service, run the command that follows.
Replace the placeholders with the full path to the certificate file and the full path to
the private key file.
The command returns the IP address and port number from which you can access the
HTTPS service.
d Click Authorize in the top-right corner of the Workstation Player API Explorer page.