VMware Workstation - 10.0 Instruction Manual
Using VMware Workstation
VMware Workstation 10
This document supports the version of each product listed and
supports all subsequent versions until the document is
replaced by a new edition. To check for more recent editions
of this document, see http://www.vmware.com/support/pubs.
EN-001200-00
Using VMware Workstation
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and
intellectual property laws. VMware products are covered by one or more patents listed at
http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
Using VMware Workstation 5
Creating Virtual Machines 7
1
Understanding Virtual Machines 7
Preparing to Create a New Virtual Machine 8
Create a New Virtual Machine on the Local Host 18
Cloning Virtual Machines 22
Virtualize a Physical Machine 25
Importing Virtual Machines 27
Installing and Upgrading VMware Tools 29
Virtual Machine Files 40
Using Virtual Machines 43
2
Starting Virtual Machines 43
Stopping Virtual Machines 47
Transferring Files and Text 51
Add a Host Printer to a Virtual Machine 60
Using Removable Devices in Virtual Machines 61
Changing the Virtual Machine Display 68
Using Folders to Manage Virtual Machines 75
Taking Snapshots of Virtual Machines 77
Install New Software in a Virtual Machine 84
Share Tablet Sensor Data with Windows 8 Guests 85
Take a Screenshot of a Virtual Machine 85
Create a Movie of a Virtual Machine 86
Delete a Virtual Machine 87
VMware, Inc.
Configuring and Managing Virtual Machines 89
3
Configure Power Options and Power Control Settings 89
Set Workstation Display Preferences 91
Configure Display Settings for a Virtual Machine 92
Set Preferences for Unity Mode 94
Setting Screen Color Depth 94
Using Advanced Linux Sound Architecture 95
Encrypting and Restricting Virtual Machines 96
Moving Virtual Machines 100
Configure a Virtual Machine as a VNC Server 105
Change the Hardware Compatibility of a Virtual Machine 108
Clean Up a Virtual Hard Disk on Windows Hosts 109
Export a Virtual Machine to OVF Format 110
Writing and Debugging Applications That Run In Virtual Machines 111
3
Using VMware Workstation
Configuring and Managing Devices 113
4
Configuring DVD, CD-ROM, and Floppy Drives 113
Configuring a USB Controller 115
Configuring and Maintaining Virtual Hard Disks 118
Adding a Physical Disk to a Virtual Machine 124
Configuring Virtual Ports 127
Configuring Generic SCSI Devices 131
Configuring Eight-Way Virtual Symmetric Multiprocessing 135
Configuring Keyboard Features 136
Modify Hardware Settings for a Virtual Machine 145
Configuring Network Connections 147
5
Understanding Virtual Networking Components 147
Understanding Common Networking Configurations 148
Changing the Default Networking Configuration 149
Configuring Bridged Networking 153
Configuring Network Address Translation 156
Configuring Host-Only Networking 165
Assigning IP Addresses in Host-Only Networks and NAT Configurations 171
Configuring LAN Segments 174
Configuring Samba for Workstation 176
Using Virtual Network Adapters in Promiscuous Mode on Linux Hosts 177
Maintaining and Changing MAC Addresses for Virtual Machines 177
Sample Custom Networking Configuration 178
Using Remote Connections and Sharing Virtual Machines 181
6
Understanding VMware Workstation Server 181
Connect to a Remote Server 184
Disconnect from a Remote Server 186
Creating and Managing Shared Virtual Machines 186
Upload a Virtual Machine to a Remote Server 190
Download a Virtual Machine from a Remote Server 190
Create a Virtual Machine on a Remote Host 191
Configure Shared and Remote Virtual Machines to Start with the Host 192
Using Roles to Assign Privileges 193
Using Permissions to Restrict Users 197
Using the vmware Command 201
7
Run the vmware Command 201
Incorporate Workstation Startup Options in a Windows Shortcut 202
Index 203
4 VMware, Inc.
Using VMware Workstation
Using VMware Workstation describes how to use VMware® Workstation and create, configure, and manage
virtual machines.
Intended Audience
This information is intended for anyone who wants to use Workstation and create and manage virtual
machines.
Where to Find Additional Information
See the following documents for more information about using Workstation. All of the documents are
available from the VMware Web site.
Getting Started with VMware Workstation describes how to install and upgrade Workstation, create a
n
typical virtual machine, and perform common virtual machine operations.
Installing and Configuring VMware Tools contains complete information on using VMware Tools.
n
The VMware Guest Operating System Installation Guide contains information about installing specific
n
guest operating systems.
VMware, Inc.
The online VMware Compatibility Guide lists the supported host and guest operating systems for
n
Workstation.
The Workstation online help provides quick reference information about Workstation settings and common
tasks. It is available from the Workstation Help menu and when you click Help on a Workstation dialog
box.
5
Using VMware Workstation
6 VMware, Inc.
Creating Virtual Machines 1
You can create a new virtual machine in Workstation by using the New Virtual Machine wizard, clone an
existing Workstation virtual machine or virtual machine template, import third-party and Open
Virtualization Format (OVF) virtual machines, and create a virtual machine from a physical machine.
You can also create shared virtual machines, which can be used by remote users, and virtual machines that
run on remote hosts. See Chapter 6, “Using Remote Connections and Sharing Virtual Machines,” on
page 181.
This chapter includes the following topics:
“Understanding Virtual Machines,” on page 7
n
“Preparing to Create a New Virtual Machine,” on page 8
n
“Create a New Virtual Machine on the Local Host,” on page 18
n
“Cloning Virtual Machines,” on page 22
n
“Virtualize a Physical Machine,” on page 25
n
“Importing Virtual Machines,” on page 27
n
“Installing and Upgrading VMware Tools,” on page 29
n
“Virtual Machine Files,” on page 40
n
Understanding Virtual Machines
A virtual machine is a software computer that, like a physical machine, runs an operating system and
applications. A virtual machine uses the physical resources of the physical machine on which it runs, which
is called the host system. Virtual machines have virtual devices that provide the same functionality as
physical hardware, but with the additional benefits of portability, manageability, and security.
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.
7
Using VMware Workstation
Preparing to Create a New Virtual Machine
You use the New Virtual Machine wizard to create a new virtual machine in Workstation. The wizard
prompts you to make decisions about many aspects of the virtual machine. You should make these
decisions before you start the New Virtual Machine wizard.
Selecting a Virtual Machine Configuration
When you start the New Virtual Machine wizard, the wizard prompts you to select a typical or custom
configuration.
Typical Configuration
If you select a typical configuration, you must specify or accept defaults for a few basic virtual machine
settings.
How you want to install the guest operating system.
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.
n
Whether to customize specific hardware settings, including memory allocation, number of virtual
n
processors, and network connection type.
Custom Configuration
You must select a custom configuration if you need to perform any of the following hardware
customizations.
Create a virtual machine that has a different Workstation version than the default hardware
n
compatibility setting.
Select the I/O controller type for the SCSI controller.
n
Select the virtual disk device type.
n
Configure a physical disk or an existing virtual disk instead of create a new virtual disk.
n
Allocate all virtual disk space rather than let disk space gradually grow to the maximum disk size.
n
Selecting the Virtual Machine Hardware Compatibility Setting
All virtual machines have a hardware version. The hardware version indicates which virtual hardware
features that the virtual machine supports, such as BIOS or EFI, number of virtual slots, maximum number
of CPUs, maximum memory configuration, and other hardware characteristics. The virtual machine
hardware compatibility setting determines the hardware features of the virtual machine.
If you select a typical configuration, the wizard uses the default hardware compatibility setting configured
in the Workstation preferences. By default, the default hardware compatibility setting is the installed
Workstation version.
If you select a custom configuration, the New Virtual Machine wizard prompts you to select a hardware
compatibility setting for the virtual machine. When you select a hardware compatibility setting, a list of the
VMware products and versions that are compatible with your selection appears. Limitations and features
that are not available for your selection are also listed. If a feature compatibility check box is available for
your selection, you can select that check box to see a list of the additional limitations.
To deploy virtual machines to run on a different VMware product, you might need to select a hardware
compatibility setting that is compatible with that product.
8 VMware, Inc.
Chapter 1 Creating Virtual Machines
Selecting a Guest Operating System
The New Virtual Machine prompts you to select the source media for the operating system that will run
inside the virtual machine. You can specify an installer disc inserted in a physical drive, an ISO image file, or
you can instruct the New Virtual Machine wizard to create a virtual machine that has a blank hard disk.
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.
NOTE For remote virtual machines, you must specify whether the physical drive or ISO image file is located
on the local host or remote host before you select the installer disc or ISO image file.
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 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.
Providing Easy Install Information
When the New Virtual Wizard detects an operating system that supports Easy Install, the wizard prompts
you for information about the guest operating system. After the virtual machine is created, the guest
operating system installation is automated and VMware Tools is installed.
For Windows guest operating systems, you must provide the following Easy Install information.
Table 1‑1. Easy Install Information for Windows Guests
Easy Install Prompt Description
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 For Windows Vista, Windows 7, and Windows Server 2008 guest operating
systems, select the operating system edition.
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
password)
(Optional) Save your login credentials and bypass the login dialog box when you
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.
VMware, Inc. 9
Using VMware Workstation
Table 1‑2. Easy Install Information for Linux Guests
Prompt Description
Full name The name to use to register the guest operating system, if registration is
required. Workstation 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.
Specifying the Virtual Machine Name and File Location
The New Virtual Machine wizard prompts you for a virtual machine name and a directory for the virtual
machine files.
The name of the default directory for virtual machine files is derived from the name of the guest operating
system, for example, Microsoft Windows 7 (32-bit).
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.
Virtual Machines Directory
Workstation stores standard virtual machines in the virtual machines directory.
The default location of the virtual machines directory depends on the host operating system.
Table 1‑3. Default Virtual Machines Directory
Host Operating System Default Location
Windows XP
Windows Server 2003
Windows Server 2008
Windows Vista
Windows 7
Windows 8
Linux
C:\Documents and Settings\username\My Documents\My Virtual
Machines
username is the name of the currently logged in user.
C:\Users\ username \Documents\Virtual Machines
username is the name of the currently logged in user.
homedir/vmware
homedir is the home directory of the currently logged in user.
Shared Virtual Machines Directory
Workstation stores shared virtual machines in the shared virtual machines directory, where VMware
Workstation Server manages them.
The default location of the shared virtual machines directory depends on the host operating system.
10 VMware, Inc.
Chapter 1 Creating Virtual Machines
Table 1‑4. Default Shared Virtual Machines Directory
Host Operating System Default Shared Virtual Machines Directory
Windows XP
Windows Server 2003
Windows Server 2008
Windows Vista
Windows 7
Windows 8
Linux
C:\Documents and Settings\All Users\Documents\Shared
Virtual Machines
C:\Users\Public\Documents\Shared Virtual Machines
/var/lib/vmware/Shared VMs
Select the Number of Processors for a Virtual Machine
When you select a custom configuration, the New Virtual Machine wizard prompts you to specify the
number of processors for the virtual machine.
Specifying multiple virtual processors is supported only on host machines that have at least two logical
processors. Single-processor hosts that have hyperthreading enabled or dual-core CPUs are considered to
have two logical processors. Multiprocessor hosts that have two CPUs are considered to have at least two
logical processors, regardless of whether they are dual-core or have hyperthreading enabled.
For Windows virtual machines running mostly office and Internet productivity applications, using multiple
virtual processors is not beneficial, so the default single virtual processor is ideal. For server workloads and
data-intensive computing applications, adding extra virtual processors may provide an increase in
application performance.
Application Recommended number of processors
Desktop applications 1 processor
Server operating systems 2 processors
Video encoding, modeling, and scientific 4 processors
In some circumstances, adding additional processors can decrease the overall perfomance of the virtual
machine and your computer. This can occur if the operating system or application is not using the
processors efficiently. In this case, reducing the number of processors is recommended.
Assigning all processors on your computer to the virtual machine results in extremely poor performance.
The host operating system must continue to perform background tasks even if no applications are running.
If you assign all processors to a virtual machine, this prevents important tasks from being completed.
Allocating Memory for a Virtual Machine
When you select a custom configuration, the New Virtual Machine wizard prompts you to specify the
default settings for memory allocation.
Color-coded icons correspond to the maximum recommended memory, recommended memory, and guest
operating system recommended minimum memory values. To adjust the memory allocated to the virtual
machine, move the slider along the range of values. The high end of the range is determined by the amount
of memory 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.
On 64-bit hosts, the maximum amount of memory for each virtual machine is 64GB. On 32-bit hosts, the
maximum amount of memory for each virtual machine is 8GB. You cannot power on virtual machines that
are configured to use more than 8GB of memory on 32-bit hosts. Memory management limitations on 32-bit
operating systems cause virtual machine memory to overcommit, which severely affects system
performance.
VMware, Inc. 11
Using VMware Workstation
The total amount of memory that you can assign to all virtual machines running on a single host machine is
limited only by the amount of RAM on the host machine.
You can change the amount of memory available to all virtual machines by modifying Workstation memory
settings.
Selecting the Network Connection Type for a Virtual Machine
When you select a custom configuration, the New Virtual Machine wizard prompts you to configure the
network connection type for the virtual machine.
If you are creating a remote virtual machine, you must select either a custom network or no network
connection.
Table 1‑5. Network Connection Settings
Setting Description
Use bridged networking Configure a bridged network connection for the virtual machine. With bridged
networking, the virtual machine has direct access to an external Ethernet network.
The virtual machine must have its own IP address on the external network.
If your host system is on a network and you have a separate IP address for your
virtual machine (or can get an IP address from a DHCP server), select this setting.
Other computers on the network can then communicate directly with the virtual
machine.
Use network address translation
(NAT)
Use host-only networking Configure a host-only network connection for the virtual machine. Host-only
Do not use a network connection Do not configure a network connection for the virtual machine.
Custom (Windows host) or
Named Network (Linux host)
Configure a NAT connection for the virtual machine. With NAT, the virtual
machine and the host system share a single network identity that is not visible
outside the network.
Select NAT if you do not have a separate IP address for the virtual machine, but you
want to be able to connect to the Internet.
networking provides a network connection between the virtual machine and the
host system, using a virtual network adapter that is visible to the host operating
system.
With host-only networking, the virtual machine can communicate only with the
host system and other virtual machines in the host-only network. Select host-only
networking to set up an isolated virtual network.
(Remote virtual machine only) Select a specific virtual network.
See Chapter 5, “Configuring Network Connections,” on page 147 for information about virtual switches,
virtual network adapters, the virtual DHCP server, and the NAT device.
Selecting the I/O Controller Type for a Virtual Machine
When you select a custom configuration, the New Virtual Machine wizard prompts you to select the I/O
controller type for the virtual machine.
Workstation installs an IDE controller and a SCSI controller in the virtual machine. SATA controllers are
supported for some guest operating systems. The IDE controller is always ATAPI. For the SCSI controller,
you can choose BusLogic, LSI Logic, or LSI Logic SAS. If you are creating a remote virtual machine on an
ESX host, you can also select a VMware Paravirtual SCSI (PVSCSI) adapter.
BusLogic and LSI Logic adapters have parallel interfaces. The LSI Logic SAS adapter has a serial interface.
The LSI Logic adapter has improved performance and works better with generic SCSI devices. The LSI
Logic adapter is also supported by ESX Server 2.0 and later.
12 VMware, Inc.
Chapter 1 Creating Virtual Machines
PVSCSI adapters are high-performance storage adapters that can provide greater throughput and lower
CPU utilization. They are best suited for environments where hardware or applications drive a very high
amount of I/O throughput, such as SAN environments. PVSCSI adapters are not suited for DAS
environments.
NOTE The choice of SCSI controller does not affect whether the virtual disk can be an IDE, SCSI, or SATA
disk.
Some guest operating systems, such as Windows XP, do not include a driver for the LSI Logic or LSI Logic
SAS adapter. You must download the driver from the LSI Logic Web site. Drivers for a Mylex (BusLogic)
compatible host bus adapter are not obvious on the LSI Logic Web site. Search the support area for the
numeric string in the model number, for example, search for 958 for BT/KT-958 drivers.
See the VMware Guest Operating System Installation Guide for driver support information. For guest operating
system support information and known issues, as well as SATA support, see the online Compatibility Guide
on the VMware Web site.
Selecting a Hard Disk for a Virtual Machine
When you select a custom configuration, the New Virtual Machine wizard prompts you to configure a hard
disk for the virtual machine.
Virtual hard disks are the best choice for most virtual machines because they are easy to set up and can be
moved to new locations on the same host system or to different host systems. In a typical configuration,
Workstation creates a new virtual hard disk for the virtual machine.
In some cases, you might want to select an existing virtual hard disk or give the virtual machine access to a
physical hard disk or unused partition on the host system.
Selecting the Virtual Hard Disk Type for a Virtual Machine on page 14
n
If you instruct the New Virtual Machine wizard to create a new virtual disk during a custom
configuration, the wizard prompts you to select the virtual hard disk type for the virtual machine.
Selecting the Disk Mode on page 14
n
When you select a custom configuration on a Linux host, you can use the New Virtual Machine
wizard to configure normal or independent mode for a disk.
Prepare to Use a Physical Disk or Unused Partition on page 14
n
You must perform certain tasks before you configure a virtual machine to use a physical disk or
unused partition on the host system.
Specifying Disk Capacity for a Virtual Machine on page 15
n
If you instruct the New Virtual Machine wizard to create a new virtual disk during a custom
configuration, the wizard prompts you to set the size of the virtual disk and specify whether to split
the disk into multiple virtual disk (.vmdk) files.
Specifying the Name and Location of Virtual Disk Files on page 17
n
During a custom configuration, if you instruct the New Virtual Machine wizard to create a new virtual
disk, use an existing virtual disk, or use a physical disk, the wizard prompts you for the name and
location of a virtual disk (.vmdk) file.
VMware, Inc. 13
Using VMware Workstation
Selecting the Virtual Hard Disk Type for a Virtual Machine
If you instruct the New Virtual Machine wizard to create a new virtual disk during a custom configuration,
the wizard prompts you to select the virtual hard disk type for the virtual machine.
You can set up a virtual disk as an IDE disk for any guest operating system. You can set up a virtual disk as
a SCSI disk for any guest operating system that has a driver for the LSI Logic or BusLogic SCSI controller
available in the virtual machine. You can set up a virtual disk
You can change virtual disk node and mode settings after a virtual machine is created.
Selecting the Disk Mode
When you select a custom configuration on a Linux host, you can use the New Virtual Machine wizard to
configure normal or independent mode for a disk.
In normal mode, disks are included in snapshots that you take of the virtual machine. If you do not want
data on the disk to be recorded when you take a snapshot of the virtual machine, configure the disk to be
independent.
If you configure a disk to be independent, you can further specify whether changes you make to the disk are
to persist or be discarded when you power off the virtual machine or restore a snapshot.
You can also exclude virtual disks from snapshots by modifying virtual machine settings.
Prepare to Use a Physical Disk or Unused Partition
You must perform certain tasks before you configure a virtual machine to use a physical disk or unused
partition on the host system.
You must perform these tasks before you run the New Virtual Machine wizard to add a physical disk to a
new virtual machine, and before you add a physical disk to an existing virtual machine.
Procedure
1 If a partition is mounted by the host or in use by another virtual machine, unmount it.
The virtual machine and guest operating system access a physical disk partition while the host
continues to run its operating system. Corruption is possible if you allow the virtual machine to modify
a partition that is simultaneously mounted on the host operating system.
Option Description
The partition is mapped to a
Windows Server 2003, Windows
Server 2008, or Windows XP host
The partition is mapped to a
Windows 7 or Windows 8 host
The partition is mapped to a
Windows Vista host
a Select Start > Settings > Control Panel > Administrative Tools >
Computer Management > Storage > Disk Management.
b Select a partition and select Action > All Tasks > Change Drive Letter
and Paths.
c Click Remove.
a Select Start > Control Panel.
b In the menu bar, click the arrow next to Control Panel.
c From the drop-down menu, select All Control Panel Items >
Administrative Tools > Computer Management > Storage > Disk
Management (Local).
d Right-click a partition and choose Change Drive Letter and Paths.
e Click Remove and OK.
a Select Start > Control Panel (Classic View) > Administrative Tools >
Computer Management > Storage > Disk Management.
b Right-click a partition and choose Change Drive Letter and Paths.
c Click Remove and OK.
14 VMware, Inc.
Chapter 1 Creating Virtual Machines
2 Check the guest operating system documentation regarding the type of partition on which the guest
operating system can be installed.
On Windows Vista and Windows 7 hosts, you cannot use the system partition, or the physical disk that
contains it, in a virtual machine. DOS, Windows 95, and Windows 98 operating systems must be
installed on the first primary partition. Other operating systems, such as Linux, can be installed on a
primary or an extended partition on any part of the drive.
3 If the physical partition or disk contains data that you need in the future, back up the data.
4 If you use a Windows host IDE disk in a physical disk configuration, verify that it is not configured as
the slave on the secondary IDE channel if the master on that channel is a CD-ROM drive.
5 On a Windows XP or Windows Server 2003 host, if the host is using a dynamic disk, use the disk
management tool to change the dynamic disk to a basic disk.
You cannot use a dynamic disk as a physical disk in a virtual machine.
a On the host, select Start > Settings > Control Panel > Administrative Tools > Computer
Management > Disk Management.
b Delete all logical volumes on the disk.
This action destroys all data on the disk.
c Right-click the disk icon and select Revert to Basic Disk.
d Partition the disk.
6 On a Linux host, set the device group membership or device ownership appropriately.
a Verify that the master physical disk device or devices are readable and writable by the user who
runs Workstation.
Physical devices, such as /dev/hda (IDE physical disk) and /dev/sdb (SCSI physical disk), belong to
group-id disk on most distributions. If this is the case, you can add VMware Workstation users to
the disk group. Another option is to change the owner of the device. Consider all the security
issues involved in this option.
b Grant VMware Workstation users access to all /dev/hd[abcd] physical devices that contain
operating systems or boot managers.
When permissions are set correctly, the physical disk configuration files in Workstation control
access. This reliability provides boot managers access to configuration files and other files they
might need to boot operating systems. For example, LILO needs to read /boot on a Linux partition
to boot a non-Linux operating system that might be on another drive.
Specifying Disk Capacity for a Virtual Machine
If you instruct the New Virtual Machine wizard to create a new virtual disk during a custom configuration,
the wizard prompts you to set the size of the virtual disk and specify whether to split the disk into multiple
virtual disk (.vmdk) files.
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.001GB and 8TB 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. 15
Using VMware Workstation
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 950GB, a series of 2GB virtual disk files are created. When
you split a virtual disk greater than 950GB, two virtual disk files are created. The maximum size of the first
virtual disk file is 1.9TB and the second virtual disk file stores the rest of the data.
For custom configurations, you can select Allocate all disk space now to allocate all disk space immediately
rather than allow the disk space to gradually grow to the maximum amount. Allocating all the disk space
immediately might provide better performance, but it is a time-consuming operation that requires as much
physical disk space as you specify for the virtual disk. If you allocate all the disk space immediately, you
cannot use the shrink disk feature.
After you create a virtual machine, you can edit virtual disk settings and add additional virtual disks.
Disk Size Compatibility
The size of a virtual disk is limited to 8TBs. However, your hardware version, bus type, and controller type
also impact the size of your virtual disks.
Workstation Hardware Version Bus Type Controller Type Maximum Disk Size
10 IDE ATAPI 8192GB (8TB)
10 SCSI BusLogic 2040GB (2TB)
10 SCSI LSI Logic 8192GB (8TB)
10 SCSI LSI Logic SAS 8192GB (8TB)
10 SCSI Paravirtualized SCSI 8192GB (8TB)
10 SATA All 8192GB (8TB)
9, 8, 7, 6.5 All All 2040GB (2TB)
6.0, 5 All All 950 GB
To discover your controller type, open the virtual machine .vmx file. The value of the setting
scsi0.virtualDev determines your controller type.
Value Controller Type
Blank or not present BusLogic
lsilogic LSI Logic
lsisas1068 LSI Logic SAS
16 VMware, Inc.
Chapter 1 Creating Virtual Machines
Specifying the Name and Location of Virtual Disk Files
During a custom configuration, if you instruct the New Virtual Machine wizard to create a new virtual disk,
use an existing virtual disk, or use a physical disk, the wizard prompts you for the name and location of a
virtual disk (.vmdk) file.
Table 1‑6. Required Information for Each Disk Type
Type of Disk Description
New virtual disk If you specified that all disk space should be stored in a
single file, Workstation uses the filename that you provide
to create one 40GB disk file. If you specified that disk space
should be stored in multiple files, Workstation generates
subsequent filenames by using the filename that you
provide. If you specified that files can increase in size,
subsequent filenames include an s in the file number, for
example, Windows 7-s001.vmdk. If you specified that all
disk space should be allocated when the virtual disk is
created, subsequent filenames include an f in the file
number, for example, Windows 7-f001.vmdk.
Existing virtual disk You select the name and location of an existing virtual disk
file.
Physical disk After the wizard prompts you to select a physical device
and specify whether to use the entire disk or individual
partitions, you must specify a virtual disk file. Workstation
uses this virtual disk file to store partition access
configuration information for the physical disk.
NOTE Earlier VMware products use the .dsk extension for virtual disk files.
Customizing Virtual Machine Hardware
You can click Customize Hardware on the last page of the New Virtual Machine wizard to customize the
virtual machine hardware.
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.
Worksheet for Creating a Virtual Machine
You can print this worksheet and write down the values to specify when you run the New Virtual Machine
wizard.
Table 1‑7. Worksheet: Creating a Virtual Machine
Option Fill In Your Value Here
Hardware compatibility setting
Guest operating system source
Guest operating system type (for manual installation)
Easy Install information for Windows guests
Product key
n
Operating system version
n
Full name
n
Password
n
Credentials for automatic login
n
VMware, Inc. 17
Using VMware Workstation
Table 1‑7. Worksheet: Creating a Virtual Machine (Continued)
Option Fill In Your Value Here
Easy Install information for Linux guests
Full name
n
User name
n
Password
n
Virtual machine name
Virtual machine location
Number of processors
Memory allocation
Network connection type
I/O controller type
Hard disk
Virtual hard disk type
Disk capacity
Virtual disk file name and location
Create a New Virtual Machine on the Local Host
You create a new virtual machine on the local host system by running the New Virtual Machine wizard.
You can also use the New Virtual Machine wizard to create shared virtual machines, which can be used by
remote users, and remote virtual machines, which run on remote hosts. See Chapter 6, “Using Remote
Connections and Sharing Virtual Machines,” on page 181.
Prerequisites
Verify that you have the information the New Virtual Machine wizard requires to create a virtual
n
machine. See “Preparing to Create a New Virtual Machine,” on page 8.
Verify that the guest operating system you plan to install is supported. See the online VMware
n
Compatibility Guide on the VMware Web site.
See the VMware Guest Operating System Installation Guide for information about the guest operating
n
system that you plan to install.
If you are installing the guest operating system from an installer disc, insert the installer disc in the CD-
n
ROM drive in the host system.
If you are installing the guest operating system from an ISO image file, verify that the ISO image file is
n
in a directory that is accessible to the host system.
If the virtual machine will use a physical disk or unused partition on the host system, perform the
n
appropriate preparation tasks. See “Prepare to Use a Physical Disk or Unused Partition,” on page 14.
18 VMware, Inc.
Procedure
1 Start the New Virtual Machine wizard.
Option Description
If the host is not connected to a remote server, select File > New
Windows host
Linux host
n
Virtual Machine.
If the host is connected to a remote server, select File > New Virtual
n
Machine > On this Computer.
Select File > New Virtual Machine.
2 Select the configuration type.
Option Description
Typical
Custom
The wizard prompts you to specify or accept defaults for basic virtual
machine settings. The typical configuration type is appropriate in most
instances.
You must select the custom configuration type to make a different virtual
machine version than the default hardware compatibility setting, specify
the I/O adapter type for SCSI adapters, specify whether to create an IDE,
SCSI, or SATA virtual disk, use a physical disk instead of a virtual disk,
use an existing virtual disk, or allocate all virtual disk space rather than let
disk space gradually grow to the maximum disk size.
3 If you selected the Custom option, select a hardware compatibility setting.
Chapter 1 Creating Virtual Machines
The hardware compatibility setting determines the hardware features of the virtual machine.
4 Select the source of the guest operating system.
Option Description
Use a physical disc
Use an ISO image
Install the guest operating system
later
Select the physical drive where you inserted the installation disc.
Type or browse to the location of the ISO image file for the guest operating
system.
Create a virtual machine that has a blank disk. You must install the guest
operating system manually after you create the virtual machine.
5 Specify information about the guest operating system.
Option Description
You are using Easy Install
You are not using Easy Install
Type the Easy Install information for the guest operating system.
Select the guest operating system type and version. If the guest operating
system is not listed, select Other.
6 Type a virtual machine name and type or browse to the directory for the virtual machine files.
7 Follow the prompts to configure the virtual machine.
If you selected a typical configuration, the wizard prompts you to configure the virtual disk size and
specify whether the disk should be split into multiple files. If you selected a custom configuration, the
wizard prompts you to configure the virtual machine processors, memory allocation, networking
configuration, I/O controller types, virtual disk, and virtual disk type and mode.
8 (Optional) Click Customize Hardware to customize the hardware configuration.
You can also modify virtual hardware settings after you create the virtual machine.
VMware, Inc. 19
Using VMware Workstation
9 (Optional) Select Power on this virtual machine after creation to power on the virtual machine after
you create it.
This option is not available if you are installing the guest operating system manually.
10 Click Finish to create the virtual machine.
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 you finished the New Virtual
Machine wizard, power on the virtual machine to start the guest operating system installation. See “Use
Easy Install to Install a Guest Operating System,” on page 20.
If you did not use Easy Install, install the guest operating system manually. See “Install a Guest Operating
System Manually,” on page 21.
Use Easy Install to Install a Guest Operating System
When you use Easy Install, you usually do not need to provide information during guest operating system
installation.
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
If the installer prompts you for a product key, username, or password, click in the virtual machine
n
window and type the required information.
Mouse and keyboard input are captured by the virtual machine.
If you are using physical discs and the installer prompts you for the next disk, use the CD-ROM or DVD
n
drive on the host system.
If you are using multiple ISO image files and the installer prompts you for the next disk, select the next
n
ISO image file.
Option Description
Windows host
Linux host
Click Change Disk and browse to the next ISO image file.
a Select VM > Removable Devices > CD/DVD > Settings and browse to
the next ISO image file.
b Select Connected.
c Click Save.
20 VMware, Inc.
Chapter 1 Creating Virtual Machines
Install a Guest Operating System Manually
Installing a guest operating system in a virtual machine is similar to installing an operating system on a
physical computer. If you do not use Easy Install when you create a virtual machine in the New Virtual
Machine wizard, you must install the guest operating system manually.
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
Verify that the operating system is supported. See the online VMware Compatibility Guide on the
n
VMware Web site.
See the VMware Guest Operating System Installation Guide for information on the guest operating system
n
that you are installing.
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 VM > Settings.
b On the Hardware tab, select CD/DVD drive.
c Select Connect at power on.
d (Remote virtual machine only) Select the location of the CD-ROM or DVD drive.
e Select Use physical drive and select a the drive.
f Click OK to save your changes.
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 VM > Settings.
b On the Hardware tab, select CD/DVD drive.
c Select Connect at power on.
d (Remote virtual machine only) Select the location of the ISO image file.
e Select Use ISO image file and browse to the location of the ISO image file.
f Click OK to save your changes.
3 If you are installing the guest operating system from an installer disc, insert the disc in the CD-ROM or
DVD drive.
4 Power on the virtual machine.
5 Follow the installation instructions provided by the operating system vendor.
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.
VMware, Inc. 21
Using VMware Workstation
7 If the operating system consists of multiple ISO image files, select the image file for the next CD.
a Select VM > Removable Devices > CD/DVD > Disconnect and disconnect from the current ISO
image file.
b Select VM > Removable Devices > CD/DVD > Settings and select the next ISO image file.
c Select Connected and click OK.
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,” on page 30.
Installing a Guest Operating System on a Physical Disk or Unused Partition
You can install a guest operating system directly on a physical disk or unused partition on the host system.
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.
Workstation supports physical disks up to 2TB capacity. Booting from an operating system already set up
on an existing SCSI disk or partition is not supported.
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.
Cloning Virtual Machines
Installing a guest operating system and applications can be time consuming. With clones, you can make
many copies of a virtual machine from a single installation and configuration process. Cloning a virtual
machine is faster and easier than copying it.
Clones are useful when you must deploy many identical virtual machines to a group. For example, an MIS
department can clone a virtual machine that has a suite of preconfigured office applications for each
employee. You can also configure a virtual machine that has a complete development environment and then
clone it repeatedly as a baseline configuration for software testing.
The existing virtual machine is called the parent virtual machine. When the cloning operation is complete,
the clone becomes a separate virtual machine.
22 VMware, Inc.
Chapter 1 Creating Virtual Machines
Changes made to a clone do not affect the parent virtual machine, and changes made to the parent virtual
machine do not appear in a clone. The MAC address and UUID for a clone are different from the parent
virtual machine.
Using Linked Clones on page 23
n
A linked clone is a copy of a virtual machine that shares virtual disks with the parent virtual machine
in an ongoing manner.
Using Full Clones on page 24
n
A full clone is a complete and independent copy of a virtual machine. It shares nothing with the
parent virtual machine after the cloning operation. Ongoing operation of a full clone is entirely
separate from the parent virtual machine.
Enable Template Mode for a Parent Virtual Machine of Linked Clones on page 24
n
To prevent the parent virtual machine for a linked clone from being deleted, you can designate the
parent as a template. When template mode is enabled, the virtual machine, and snapshots of the
virtual machine, cannot be deleted.
Clone a Virtual Machine on page 24
n
The Clone Virtual Machine wizard guides you through the process of cloning a virtual machine. You
do not need to locate and manually copy the parent virtual machine files.
Using Linked Clones
A linked clone is a copy of a virtual machine that shares virtual disks with the parent virtual machine in an
ongoing manner.
Because a linked clone is made from a snapshot of the parent, disk space is conserved and multiple virtual
machines can use the same software installation. All files available on the parent at the moment you take the
snapshot continue to remain available to the linked clone.
Ongoing changes to the virtual disk of the parent do not affect the linked clone, and changes to the disk of
the linked clone do not affect the parent. A linked clone must have access to the parent. Without access to
the parent, you cannot use a linked clone.
Because linked clones are created swiftly, you can create a unique virtual machine for each task. You can
also share a virtual machine with other users by storing the virtual machine on your local network where
other users can quickly make a linked clone. For example, a support team can reproduce a bug in a virtual
machine, and an engineer can quickly make a linked clone of that virtual machine to work on the bug.
You can make a linked clone from a linked clone, but the performance of the linked clone degrades. If you
make a full clone from a linked clone, the full clone is an independent virtual machine that does not require
access to the linked clone or its parent. You should make a linked clone of the parent virtual machine, if
possible.
IMPORTANT You cannot delete a linked clone snapshot without destroying the linked clone. You can safely
delete the snapshot only if you also delete the clone that depends on it.
VMware, Inc. 23
Using VMware Workstation
Using Full Clones
A full clone is a complete and independent copy of a virtual machine. It shares nothing with the parent
virtual machine after the cloning operation. Ongoing operation of a full clone is entirely separate from the
parent virtual machine.
Because a full clone does not share virtual disks with the parent virtual machine, full clones generally
perform better than linked clones. Full clones take longer to create than linked clones. Creating a full clone
can take several minutes if the files involved are large.
Because a full clone duplicates only the state of the virtual machine at the instant of the cloning operation, it
does not have access to snapshots of the parent virtual machine.
Enable Template Mode for a Parent Virtual Machine of Linked Clones
To prevent the parent virtual machine for a linked clone from being deleted, you can designate the parent as
a template. When template mode is enabled, the virtual machine, and snapshots of the virtual machine,
cannot be deleted.
NOTE You cannot enable template mode for a shared or remote virtual machine.
Prerequisites
If the parent does not have at least one snapshot, create a snapshot. See “Taking Snapshots of Virtual
Machines,” on page 77.
Procedure
1 Select the virtual machine to use as a parent of the linked clone and select VM > Settings.
2 On the Options tab, select Advanced.
3 Select Enable Template mode (to be used for cloning) and click OK.
Clone a Virtual Machine
The Clone Virtual Machine wizard guides you through the process of cloning a virtual machine. You do not
need to locate and manually copy the parent virtual machine files.
Prerequisites
Familiarize yourself with the different types of clones. See “Using Full Clones,” on page 24 and “Using
n
Linked Clones,” on page 23.
Run a defragmentation utility in the guest operating system to defragment the drives on the parent
n
virtual machine.
If the parent virtual machine is a Workstation 4.x and Workstation 4.x-compatible virtual machine,
n
upgrade it to Workstation 5.x or later.
If you are creating a linked clone, enable template mode for the parent virtual machine. See “Enable
n
Template Mode for a Parent Virtual Machine of Linked Clones,” on page 24.
Power off the parent virtual machine.
n
Procedure
1 Select the parent virtual machine and select VM > Manage > Clone.
24 VMware, Inc.
Chapter 1 Creating Virtual Machines
2 Select the state of the parent from which you want to create a clone.
You can create a clone from the current state of the parent virtual machine or from an existing snapshot.
If you select the current state, Workstation creates a snapshot of the parent virtual machine before
cloning it.
NOTE You cannot clone from the current state if template mode is enabled for the parent virtual
machine.
3 Specify whether to create a linked clone or a full clone.
4 Type a name and a location for the cloned virtual machine.
5 Click Finish to create the clone and Close to exit the wizard.
A full clone can take several minutes to create, depending on the size of the virtual disk that is being
duplicated.
6 If the parent virtual machine uses a static IP address, change the static IP address of the clone before the
clone connects to the network to prevent IP address conflicts.
Although the wizard creates a new MAC address and UUID for the clone, other configuration
information, such as the virtual machine name and static IP address configuration, is identical to that of
the parent virtual machine.
The summary view for a linked clone shows the path to the virtual machine configuration (.vmx) file of the
parent virtual machine.
Virtualize a Physical Machine
You can create a virtual machine from a Windows physical machine in Workstation. When you virtualize a
physical machine, you capture all of the applications, documents, and settings on the physical machine in a
new virtual machine. Workstation must be running on a Windows host system to use this feature.
Prerequisites
Verify that the physical machine that you want to virtualize is running Windows. You cannot create a
n
virtual machine from a non-Windows physical machine in Workstation.
Verify that you have administrative access on the physical machine that you want to virtualize and on
n
the Workstation host system.
Verify that the Workstation host system has network access to the physical machine that you want to
n
virtualize.
Verify that on the Workstation host system you have disabled User Account Control (UAC). For
n
instructions, see “Prepare a Windows Physical Machine for Virtualization,” on page 26.
Turn off firewall applications running on the physical machine that you want to virtualize.
n
Prepare the physical machine for virtualization. See “Prepare a Windows Physical Machine for
n
Virtualization,” on page 26.
Procedure
1 Power on the physical machine that you want to virtualize.
2 On the Windows host system, in Workstation, select File > Virtualize a Physical Machine.
If you have never virtualized a physical machine or imported a third-party virtual machine in
Workstation, Workstation installs VMware vCenter Converter Standalone. After the installation is
finished, you must restart the virtualization wizard.
VMware, Inc. 25
Using VMware Workstation
3 Type the hostname or IP address, user name, and password for the physical machine that you want to
virtualize.
You must use the Administrator account or a user account that is a member of the local Administrators
group.
4 Type a name for the new virtual machine and specify a location on the host system in which to store the
virtual machine files.
5 Type the user name and password for your user account on the host system.
6 Click Finish to create a virtual machine from the physical machine.
The amount of time required to create the virtual machine depends on the size of the hard disk on the
physical machine.
VMware Tools installation begins the first time you power on the new virtual machine.
Prepare a Windows Physical Machine for Virtualization
To avoid problems related to permissions and network access, you must perform certain steps to prepare a
Windows physical machine before you run the Virtualize a Physical Machine wizard.
Procedure
1 If the physical machine is running Windows XP, turn off simple file sharing on the physical machine.
Turning off simple file sharing does not turn off the Shared Documents feature. You can use the simple
file sharing interface, which is located in folder properties, to configure share and file permissions.
NOTE On Windows XP systems that are part of a workgroup, the simple file sharing interface is turned
on by default. Windows XP systems that are part of a domain use only the classic file sharing and
security interface.
a Open the Folder Options control panel.
b On the View tab, deselect Use Simple File Sharing (Recommended).
2 If the physical machine is running Windows Vista or Windows 7, disable User Account Control (UAC).
On Windows Vista, open the User Accounts control panel, select Turn User Account Control On
n
or Off, and deselect Use User Account Control (UAC) to help protect your computer.
On Windows 7, open the Change User Account Control Settings control panel and drag the slider
n
to Never notify.
Troubleshoot Windows Authentication Problems During Physical Machine Virtualization
User authentication fails when the Virtualize a Physical Machine wizard attempts to connect a Windows
physical machine.
Problem
After you provide user credentials for the physical machine, the Virtualize a Physical Machine wizard
reports that your user credentials are incorrect or you have insufficient permissions to connect to the
physical machine.
Cause
Simple file sharing or User Account Control (UAC) is enabled on the physical machine.
26 VMware, Inc.
Chapter 1 Creating Virtual Machines
Solution
Perform the steps in “Prepare a Windows Physical Machine for Virtualization,” on page 26 and rerun the
Virtualize a Physical Machine wizard.
Troubleshoot Windows Activation Problems
A virtual machine that you create from a physical machine prompts you to activate Windows when you use
it in Workstation.
Problem
After you create a virtual machine from a Windows Vista or Windows 7 physical machine, or from a
physical PC that came with Windows preinstalled, you were required to reactivate Windows in the virtual
machine.
Cause
When you create a virtual machine from a Windows Vista or Windows 7 physical machine, the operating
system detects that the computer hardware has changed. When you make a significant hardware change,
Microsoft requires you to activate Windows again.
The OEM versions of Windows that are preinstalled on some new computers are customized for those
computers. OEM licenses of Windows are not transferrable.
Solution
Any virtual machine that was created from a physical machine that had its Windows license key
successfully activated needs to be reactivated when you run it in Workstation.
The activation process in Windows Vista and Windows 7 is different from the Windows XP activation
process. In Windows Vista and Windows 7, retail activation keys are good for only one use. If you enter the
same activation key in Workstation that you used previously, you cannot successfully activate the virtual
machine.
The activation wizard tells you that the activation key was already used and prompts you to call the
Microsoft activation hotline to get a second key. If you did not previously call the hotline for the same
license key, you should receive a new activation key. Your call is not transferred to an operator unless you
call repeatedly for the same key.
See the Microsoft Web site for more information about why reactivation is necessary.
Importing Virtual Machines
You can import Windows XP Mode, Open Virtualization Format (OVF), and Windows Virtual PC virtual
machines in Workstation.
Import a Windows XP Mode Virtual Machine
You can import a Windows XP Mode virtual machine and run it in Workstation. When you import a
Windows XP Mode virtual machine, Workstation creates a new virtual machine in VMware runtime (.vmx)
format.
You can power on only one Windows XP Mode virtual machine at a time in Workstation. If you move a
Windows XP Mode virtual machine to another host system, it becomes a new virtual machine and you must
activate it.
NOTE Changes made to the original Windows XP Mode virtual machine through Virtual PC do not affect
the virtual machine imported in Workstation.
VMware, Inc. 27
Using VMware Workstation
Prerequisites
Verify that the Windows 7 Professional, Enterprise, or Ultimate edition operating system is running on
n
the host system. Importing Windows XP Mode virtual machines is not supported on Linux host
systems or on host systems that are running other versions of Windows.
Download and install the Windows XP Mode virtual machine on the host system.
n
Procedure
1 Select File > Import Windows XP Mode VM, or select File > Open and browse to the virtual machine
configuration (.vmc) file.
If you have never imported a third-party virtual machine or virtualized a physical machine in
Workstation, Workstation installs VMware vCenter Converter Standalone. After the installation is
finished, you must restart the import.
2 Type a name for the new virtual machine, type or browse to the directory for the virtual machine files,
and click Import.
Workstation begins importing the Windows XP Mode virtual machine.
After Workstation successfully imports the Windows XP Mode virtual machine, a new virtual machine
appears in the virtual machine library.
Import an Open Virtualization Format Virtual Machine
You can import an Open Virtualization Format (OVF) virtual machine and run it in Workstation.
Workstation converts the virtual machine from OVF format to VMware runtime (.vmx) format. You can
import both .ovf and .ova files.
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. You can import OVF 1.0 and later 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 installation directory under OVFTool.
See the OVF Tool User Guide on the VMware Web site for information on using the OVF Tool.
Procedure
1 In Workstation, select File > Open.
2 Browse to the .ovf or .ova file and click Open.
3 Type a name for the virtual machine, type or browse to the directory for the virtual machine files, and
click Import.
Workstation performs OVF specification conformance and virtual hardware compliance checks. A
status bar indicates the progress of the import process.
4 If the import fails, click Retry to try again, or click Cancel to cancel the import.
If you retry the import, Workstation relaxes the OVF specification conformance and virtual hardware
compliance checks and you might not be able to use the virtual machine in Workstation.
After Workstation successfully imports the OVF virtual machine, the virtual machine appears in the virtual
machine library.
28 VMware, Inc.
Chapter 1 Creating Virtual Machines
Import a Windows Virtual PC Virtual Machine
You can import a Windows Virtual PC virtual machine and run it in Workstation. Workstation converts the
virtual machine from Virtual PC (.vmc) format to VMware runtime (.vmx) format. This feature is supported
only on Windows host systems.
Prerequisites
Download and install the Virtual PC virtual machine on the Windows host system.
Procedure
1 In Workstation, select File > Open.
If you have never imported a third-party virtual machine or virtualized a physical machine in
Workstation, Workstation installs VMware vCenter Converter Standalone. After the installation is
finished, you must restart the import.
2 Browse to the .vmc file and click Open.
3 Type a name for the virtual machine, type or browse to the directory for the virtual machine files, and
click Import.
After Workstation successfully imports the Virtual PC virtual machine, the virtual machine appears in the
virtual machine library.
Installing and Upgrading VMware Tools
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 that you are using. Other compatibility options are also available.
Installing VMware Tools on page 30
n
VMware Tools is a suite of utilities that enhances the performance of the virtual machine’s guest
operating system and improves management of the virtual machine.
Upgrading VMware Tools on page 30
n
You can upgrade VMware Tools manually, or you can configure virtual machines to check for and
install newer versions of VMware Tools.
Configure Automatic Software Updates on page 31
n
You can configure Workstation to automatically download software updates, including new versions
of VMware Tools. When automatic software updates are enabled, Workstation always includes the
latest support for guest operating systems and virtual machines always have the latest version of
VMware Tools.
Configure VMware Tools Updates for a Specific Virtual Machine on page 32
n
You can configure virtual machines that have Windows or Linux guest operating systems to update
VMware Tools automatically. For other guest operating systems, you must manually update VMware
Tools.
Manually Installing and Upgrading VMware Tools on page 33
n
You can manually install or upgrade VMware Tools on Windows, Linux, NetWare, Solaris, and
FreeBSD virtual machines.
VMware, Inc. 29
Using VMware Workstation
Start the VMware User Process Manually If You Do Not Use a Session Manager on page 39
n
VMware Tools in Linux, Solaris, and FreeBSD guest operating systems uses the VMware User process
executable file. This program implements the fit-guest-to-window feature and Unity mode, among
other features.
Uninstall VMware Tools on page 39
n
Occasionally, an upgrade of VMware Tools is incomplete. You can usually solve the problem by
uninstalling VMware Tools and then reinstalling.
Installing VMware Tools
VMware Tools is a suite of utilities that enhances the performance of the virtual machine’s guest operating
system and improves management of the virtual machine.
Although the guest operating system can run without VMware Tools, many VMware features are not
available until you install VMware Tools. For example, if you do not have VMware Tools installed in your
virtual machine, you cannot use the shutdown or restart options from the toolbar. You can use only the
power options.
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 installers for VMware Tools are ISO image files. An ISO image file looks like a CD-ROM to your guest
operating system. Each type of guest operating system, including Windows, Linux, Solaris, FreeBSD, and
NetWare, 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.
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.
The installation procedure varies, depending on the operating system.
Upgrading VMware Tools
You can upgrade VMware Tools manually, or you can configure virtual machines to check for and install
newer versions of VMware Tools.
The guest operating system checks the version of VMware Tools when you power on a virtual machine. The
status bar of the virtual machine displays a message when a new version is available.
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.
30 VMware, Inc.
Loading...