VMware Workstation - 3.2 Instruction Manual

User’s Manual
TM
VMware Workstation
Version 3.2
VMware, Inc.
3145 Porter Drive Palo Alto, CA 94304 www.vmware.com
Please note that you will always find the most up-to-date technical docu­mentation on our Web site at http://www.vmware.com/support/.
The VMware Web site also provides the latest product updates.
Copyright © 1998–2002 VMware, Inc. All rights reserved. U.S. Patent No. 6,397,242 and patents pending. VMware, the VMware boxes logo, GSX Server and E SX Server are trademarks of VMware, I nc. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. All other marks and names mentioned herein may be trademarks of their respective companies. Revision: 20020905 Item: WS-ENG-Q302-405
Table of Contents
Introduction and System Requirements __________________________ 11
Welcome to VMware Workstation __________________________________ 12
Virtualizing Your Computing Resources ___________________________ 13 Host System Requirements ________________________________________14 Virtual Machine Specifications _____________________________________ 18 Supported Guest Operating Systems ________________________________21 What’s New in Version 3 __________________________________________23
New in Version 3.2 ____________________________________________23
New in Versions 3.0 and 3.1 _____________________________________23 Technical Support Resources ______________________________________26
The VMware Web Site _________________________________________26
VMware Newsgroups __________________________________________ 26
Reporting Problems ___________________________________________26
Installing VMware Workstation _________________________________ 29
Installing and Uninstalling VMware Workstation 3.2 _____________________ 30
Selecting Your Host System _____________________________________ 30 Installing VMware Workstation 3.2 on a Windows Host __________________ 31
Installing the VMware Workstation Software ________________________31
Uninstalling VMware Workstation 3.2 on a Windows Host _____________ 35 Installing VMware Workstation 3.2 on a Linux Host _____________________36
Installing the VMware Workstation Software ________________________36
Before You Install on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 Host Operating
System _____________________________________________________39
Uninstalling VMware Workstation 3.2 on a Linux Host _________________41
Upgrading VMware Workstation ________________________________ 43
Upgrading from VMware Workstation 2.0, 3.0 and 3.1 ___________________ 44 Preparing for the Upgrade ________________________________________45
Before You Install VMware Workstation 3.2 _________________________ 45
When You Remove Version 2.0 and Install Version 3.2 _________________ 46 Upgrading on a Windows Host ____________________________________47
Upgrading from Version 2.0, 3.0 or 3.1 to 3.2 ________________________47
www.vmware.com
3
Upgrading on a Linux Host ________________________________________53 Upgrading from VMware Workstation 1.x or VMware Express _____________ 58
Creating a New Virtual Machine _________________________________ 59
Preparing to Run a Virtual Machine _________________________________60 Setting up a New Virtual Machine on a Windows Host __________________ 61
What’s in a Virtual Machine on a Windows Host? ____________________61
Simple Steps to a New Virtual Machine on a Windows Host ____________62 Setting up a New Virtual Machine on a Linux Host ______________________ 69
What’s in a Virtual Machine on a Linux Host? ________________________69
Simple Steps to a New Virtual Machine on a Linux Host _______________70 Installing a Guest Operating System and VMware Tools __________________81 Installing Windows Me as a Guest Operating System ____________________ 82 Installing VMware Tools __________________________________________84
VMware Tools for Windows Guests _______________________________84
VMware Tools for Linux Guests __________________________________ 88
VMware Tools for FreeBSD Guests ________________________________89
Installing VMware Tools in a NetWare Virtual Machine ________________ 91 VMware Tools Configuration Options ________________________________ 92
Running VMware Workstation __________________________________ 95
A Quick Guide to Running VMware Workstation _______________________ 96
Overview of the VMware Workstation Window ______________________97
Starting a Virtual Machine on a Windows Host ______________________ 98
Starting a Virtual Machine on a Linux Host ________________________ 101
Checking the Status of VMware Tools ____________________________ 101
Using Full Screen Mode _______________________________________ 102
Installing New Software Inside the Virtual Machine __________________ 102
Cutting, Copying and Pasting __________________________________ 103
Sharing Files Between Guest and Host Operating Systems ____________103
Deciding How Your Virtual Machine Stores Data ____________________ 108
Suspending and Resuming Virtual Machines ______________________109
Resuming Virtual Machines Repeatedly from the Same Point __________111
Shutting Down a Virtual Machine _______________________________ 115
Adding, Configuring and Removing Devices in a Virtual Machine ______ 115
Connecting and Disconnecting Removable Devices _________________ 116
Fitting the VMware Workstation Window to the Virtual Machine _______117
Creating a Screen Shot of a Virtual Machine _______________________117
Setting General Preferences for VMware Workstation ________________118
4
www.vmware.com
Command Reference _________________________________________ 123
Moving and Sharing Virtual Machines ___________________________ 125
Moving and Sharing Virtual Machines ______________________________ 126 Moving a Virtual Machine ________________________________________ 127
Virtual Machines Use Relative Paths ______________________________127
Preparing your Virtual Machine for the Move ______________________ 127
Moving a Virtual Machine to a New Host Machine __________________ 128 Moving an Older Virtual Machine __________________________________ 130
Preparing Your Virtual Machine for the Move ______________________ 130
Preparing the New Host Machine _______________________________ 131
Considerations for Moving Disks in Undoable Mode _________________ 132 Sharing Virtual Machines with Other Users ___________________________134
Installing Guest Operating Systems _____________________________ 135
Choosing and Installing Guest Operating Systems _____________________136 Supported and Unsupported Guest Operating Systems ________________ 138
Supported Guest Operating Systems ____________________________ 138
Unsupported Guest Operating Systems __________________________ 139 Installation Notes for Particular Guest Operating Systems _______________141
Windows .NET Server Installation Guidelines _______________________ 142
Windows XP Installation Guidelines ______________________________144
Windows 2000 Installation Guidelines ____________________________ 147
Windows NT Installation Guidelines _____________________________ 149
Windows Me Installation Guidelines _____________________________152
Windows 98 Installation Guidelines ______________________________ 153
Windows 95 Installation Guidelines ______________________________ 156
DOS and Windows 3.x Installation Notes __________________________161
Caldera OpenLinux 2.2, 2.3 and 2.4 Installation Guidelines ____________163
Caldera OpenLinux 1.3 and Earlier Installation Guidelines _____________165
Corel Linux OS 1.1, 1.2 Installation Guidelines ______________________ 167
Corel Linux OS 1.0 Installation Guidelines _________________________ 169
Mandrake Linux 8.2 Installation Guidelines ________________________ 171
Mandrake Linux 8.0 and 8.1 Installation Guidelines __________________ 173
Red Hat Linux 7.3 Installation Guidelines __________________________175
Red Hat Linux 7.1 and 7.2 Installation Guidelines ____________________ 178
Red Hat Linux 7.0 Installation Guidelines __________________________181
Red Hat Linux 6.x Installation Guidelines __________________________ 183
Red Hat Linux 5.x Installation Guidelines __________________________ 185
www.vmware.com
5
SuSE Linux 8.0 Installation Guidelines ____________________________ 187
SuSE Linux Enterprise Server 7 Installation Guidelines ________________ 189
SuSE Linux 7.3 Installation Guidelines ____________________________190
SuSE Linux 7.2 Installation Guidelines ____________________________ 192
SuSE Linux 7.1 Installation Guidelines ____________________________ 194
SuSE Linux 7.0 Installation Guidelines ____________________________196
Turbolinux 7.0 Installation Guidelines ____________________________ 198
Turbolinux 6.0 Installation Guidelines ____________________________ 200
FreeBSD as a Guest Operating System ____________________________ 202
NetWare 6.0 Server Installation Guidelines ________________________209
Using Disks _________________________________________________ 213
Using Disks in a Virtual Machine ___________________________________214 Configuring Hard Disk Storage in a Virtual Machine ____________________216
Disk Types: Virtual and Raw ____________________________________216
Disk Modes: Persistent, Undoable and Nonpersistent ________________218
File Locations _______________________________________________221
Updating Filenames for Virtual Disks Created with Earlier VMware
Products ___________________________________________________ 224
Defragmenting and Shrinking Virtual Disks ________________________ 225 Adding Drives to a Virtual Machine ________________________________226
Adding Virtual Disks to a Virtual Machine _________________________ 226
Adding Raw Disks to a Virtual Machine ___________________________ 229
Adding DVD or CD-ROM Drives to a Virtual Machine ________________ 233
Adding Floppy Drives to a Virtual Machine ________________________ 234
Connecting a CD-ROM or Floppy Drive to an Image File ______________235 Configuring a Dual-Boot Computer for Use with a Virtual Machine ________ 237
Configuring Dual- or Multiple-Boot Systems to Run with VMware
Workstation ________________________________________________240
Setting Up Hardware Profiles in Virtual Machines ___________________ 247
Adding Uniprocessor Support to Windows NT 4.0 MPS Installations _____ 251
Running a Windows 2000, Windows XP or Windows .NET Server Virtual
Machine from an Existing Multiple-Boot Installation on Computers
with ACPI __________________________________________________ 252
Setting Up the SVGA Video Driver for a Windows 95 Guest Operating
System Booted from a Raw Disk ________________________________255
SVGA Video Driver Setup for Use with a Windows 98 Guest Operating
System Booted from a Raw Disk ________________________________257
6
www.vmware.com
Disk Partition Hiding for Dual- or Multiple-Boot Systems ______________259
Do Not Use Windows 2000, Windows XP and Windows .NET Server
Dynamic Disks as Raw Disks ____________________________________ 259
Configuring Dual- or Multiple-Boot SCSI Systems to Run with VMware
Workstation for Linux _________________________________________ 260 Installing an Operating System onto a Raw Partition from a Virtual Machine _ 265
Configuring a Windows Host ___________________________________ 266
Configuring a Linux Host ______________________________________ 268 Disk Performance in Windows NT Guests on Multiprocessor Hosts ________ 271
Improving Performance _______________________________________ 271
Networking _________________________________________________ 273
Configuring Your Virtual Network __________________________________274 Components of the Virtual Network ________________________________ 276 Common Networking Configurations ______________________________ 278
Bridged Networking _________________________________________ 278
Network Address Translation (NAT) ______________________________279
Host-Only Networking ________________________________________280 Custom Networking Configurations ________________________________ 282 Changing the Networking Configuration ____________________________ 285
Adding and Modifying Virtual Network Adapters ___________________285
Configuring Bridged Networking Options on a Windows Host _________287
Disabling and Removing NAT and Host-Only Adapters _______________289 Advanced Networking Topics ____________________________________293
Selecting IP Addresses on a Host-Only Network or NAT Configuration ___293
Avoiding IP Packet Leakage in a Host-Only Network _________________ 297
Changing the MAC Address of a Virtual Machine ___________________298
Controlling Routing Information for a Host-Only Network on a Linux Host 299
Other Potential Issues with Host-Only Networking on a Linux Host _____300
Using Samba for File Sharing on a Linux Host ______________________ 301
Configuring a Virtual Machine to Switch Network Adapters on a
Windows NT Host ___________________________________________ 309
Setting Up a Second Bridged Network Interface on a Linux Host _______311
Setting Up Two Separate Host-Only Networks _____________________ 312
Routing between Two Host-Only Networks _______________________316
Using Virtual Ethernet Adapters in Promiscuous Mode on a Linux Host __321 Understanding NAT ____________________________________________ 323
Using NAT in VMware Workstation ______________________________323
www.vmware.com
7
The Host Computer and the NAT Network ________________________ 323
DHCP on the NAT Network ____________________________________ 324
DNS on the NAT Network _____________________________________ 324
External Access from the NAT Network ___________________________ 324
Advanced NAT Configuration __________________________________325
Considerations for Using NAT __________________________________328
Using NAT with NetLogon (Windows Hosts and Virtual Machines Only) __328
Sample Windows vmnetnat.conf File ____________________________ 330
Video and Sound ____________________________________________ 333
Configuring Video and Sound in VMware Workstation 3.2 _______________334 Setting Screen Colors in a Virtual Machine ___________________________335
Changing Screen Colors on the Host _____________________________335
Changing Screen Colors in the Guest ____________________________335 Changing XFree86 Video Resolutions on a Linux Host __________________ 337
Configuration _______________________________________________337
Possible Issues ______________________________________________337 Configuring Sound in VMware Workstation __________________________ 339
Setting Up a Virtual Sound Card on a Windows Host ________________ 339
Setting Up a Virtual Sound Card on a Linux Host ____________________ 340
Setting Up Sound in the Guest Operating System ___________________ 340
Improving Sound Performance _________________________________343
Connecting Devices __________________________________________ 345
Using Devices with a Virtual Machine _______________________________ 346 Using Parallel Ports _____________________________________________ 348
Unidirectional Ports __________________________________________348
Bidirectional Ports ___________________________________________ 348
Default Configuration ________________________________________ 349
Installation in Guest Operating Systems __________________________ 349
Troubleshooting ____________________________________________ 350
Configuring a Bidirectional Parallel Port on a Linux Host ______________351
Devices You Can Use on a Bidirectional Parallel Port _________________ 354 Using Serial Ports ______________________________________________ 355
Using a Serial Port on the Host Computer _________________________355
Using a File on the Host Computer ______________________________ 357
Connecting an Application on the Host to a Virtual Machine __________ 358
Connecting Two Virtual Machines _______________________________ 359
Special Configuration Options for Advanced Users __________________ 362
8
www.vmware.com
Usage Scenarios: Debugging Over a Virtual Serial Port _______________ 363 Keyboard Mapping on a Linux Host ________________________________366
Quick Answers ______________________________________________ 366
The Longer Story ____________________________________________ 366
V-Scan Code Table ___________________________________________ 369 Using USB Devices in a Virtual Machine _____________________________375
Notes on USB Support in Version 3.2 _____________________________375
Enabling and Disabling the USB Controller ________________________375
Connecting USB Devices ______________________________________ 376
Using USB with a Windows Host ________________________________376
Using USB with a Linux Host ___________________________________377
Who Has Control Over a USB Device? ____________________________ 377
Disconnecting USB Devices from a Virtual Machine _________________378
Human Interface Devices ______________________________________ 378 Connecting to a Generic SCSI Device _______________________________ 379
Generic SCSI on a Windows Host Operating System _________________379
Generic SCSI on a Linux Host Operating System ____________________ 381
Performance Tuning _________________________________________ 385
Adjusting Virtual Machines for Best Performance ______________________ 386 Configuring VMware Workstation __________________________________ 387
General VMware Workstation Options ____________________________ 387
VMware Workstation on a Windows Host _________________________ 390
VMware Workstation on a Linux Host ____________________________ 391 Memory Usage Notes ___________________________________________ 392
Virtual Machine Memory Size __________________________________392
Reserved Memory ___________________________________________393
Using More than 1GB of Memory on a Linux Host ___________________ 394 Improving Performance for Guest Operating Systems __________________ 396
Windows 95 and Windows 98 Guest Operating System Performance Tips 396
Windows 2000, Windows XP and Windows .NET Server Guest Operating
System Performance Tips ______________________________________ 398
Linux Guest Operating System Performance Tips ___________________ 400
Special-Purpose Configuration Options _________________________ 401
Using Special-Purpose Configurations ______________________________ 402 Locking Out Interface Features ____________________________________ 403
Removing a Forgotten Password ________________________________403
www.vmware.com
9
Restricting the User Interface _____________________________________ 405
Using Repeatable Resume with a Restricted User Interface ____________405
Glossary ____________________________________________________ 409
Glossary _____________________________________________________ 410
Index ______________________________________________________ 415
10
www.vmware.com
1

Introduction and System Requirements

Introduction and System Requirements

Welcome to VMware Workstation

This section contains the following:
Host System Requirements on page 14
Virtual Machine Specifications on page 18
Supported Guest Operating Systems on page 21
What’s New in Version 3 on page 23
Technical Support Resources on page 26
Thank you for choosing VMware™ Workstation, the software that increases the productivity of developers and other technical professionals by letting them run multiple operating systems in secure, transportable, high-performance virtual computers.
If you’re new to VMware Workstation, this chapter is the place to start. It introduces you to some of the things you can do with VMware Workstation and guides you through installing the software and putting it to work.
If you’re a veteran user of VMware products, take a few minutes to see what’s new in version 3 and check out the notes on upgrading your installation.
12
www.vmware.com
Introduction and System Requirements

Virtualizing Your Computing Resources

VMware products provide a virtualization layer that turns your physical computers into a pool of logical computing resources. You can then dynamically allocate those resources to any operating system or application in the way that best meets your needs. You’ll be able to spend more time delivering tangible value to your business and less time installing operating systems, rebooting or reconfiguring hardware.
Run the operating systems you need — all at once
With VMware virtualization technology, you can set up completely independent installations of operating systems on a single machine. Multiple instances of Microsoft® Windows® or Linux® can run side by side in virtual machines that you create with the VMware Workstation software. Each virtual machine is equivalent to a PC with a unique network address and a full complement of hardware devices. You install and run a complete, unmodified operating system and application software, just as you would on a physical PC.
Host and Guest
•The physical computer on which you install the VMware Workstation software is called the host computer, and its operating system is called the host operating system.
• The operating system running inside a virtual machine is called a guest operating system.
• For definitions of these and other special terms, see the glossary at the end of this manual.
www.vmware.com
13
Introduction and System Requirements

Host System Requirements

What do you need to get the most out of VMware Workstation? Take the following list of requirements as a starting point. Remember that the virtual machines running under VMware Workstation are like physical computers in many ways — and, like physical computers, they generally perform better if they have faster processors and more memory.
PC Hardware
•Standard PC
400MHz or faster processor (recommended; 266MHz minimum) that supports the Pentium® instruction set Compatible processors include Intel: Celeron, Pentium II, Pentium III, Pentium 4 AMD™: K6-2, K6-III, Athlon™, Athlon MP, Athlon XP, Duron™
Multiprocessor systems supported
Memory
Enough memory to run the host operating system, plus memory required for each guest operating system and for applications on the host and guest
Recommended: 256MB; minimum: 128MB
14
Display
Greater than 256-color (8-bit) display adapter required
Linux hosts must have a video adapter supported by the XFree86 server to run guest operating systems in full-screen mode
Disk Drives
100MB (for Windows hosts), 20MB (for Linux hosts) free space required for basic installation
At least 1GB free disk space recommended for each guest operating system and the application software used with it; using 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
IDE or SCSI hard drives, CD-ROM and DVD-ROM drives supported
Guest operating systems can reside on physical disk partitions or in virtual disk files
www.vmware.com
Introduction and System Requirements
Local Area Networking (Optional)
Any Ethernet controller supported by the host operating system
Non-Ethernet networks supported using built-in network address translation (NAT) or using host-only networking plus routing software on the host operating system
Windows Host Operating Systems
Windows .NET Web Server beta 3, Windows .NET Standard Server beta 3 and Windows .NET Enterprise Server beta 3 (experimental)
Windows XP Professional and Windows XP Home Edition; Service Pack 1
Windows 2000 Professional, Windows 2000 Server and Windows 2000 Advanced Server; Service Pack 2; Service Pack 3
Windows NT® Workstation 4.0 and Windows NT Server 4.0; Service Pack 3 or higher
Caution: Do not install VMware Workstation on a Windows NT Server 4.0 system that is configured as a primary or backup domain controller.
Internet Explorer 4.0 or higher required for help system
Linux Host Operating Systems
Supported distributions and kernels are listed below. VMware Workstation may not run on systems that do not meet these requirements.
Note: As newer Linux kernels and distributions are released, VMware modifies and tests its products for stability and reliability on those host platforms. We make every effort to add support for new kernels and distributions in a timely manner, but until a kernel or distribution is added to the list below, its use with our product is not supported. Look for newer prebuilt modules in the Download area of our Web site. Go to www.vmware.com/download/.
Mandrake™ Linux 8.2 — stock 2.4.18-6mdk
Mandrake Linux 8.1 — stock 2.4.8-26mdk, upgrade 2.4.8-34mdk
Mandrake Linux 8.0 — stock 2.4.3-20mdk
Red Hat™ Linux 7.3 — stock 2.4.18
Red Hat Linux 7.2 — stock 2.4.7-10, upgrade 2.4.9-7, upgrade 2.4.9-13, upgrade
2.4.9-21, upgrade 2.4.9-31
Red Hat Linux 7.1 — stock 2.4.2-2, upgrade 2.4.3-12
Red Hat Linux 7.0 — stock 2.2.16-22, upgrade 2.2.17-14
www.vmware.com
15
Introduction and System Requirements
Red Hat Linux 6.2 — upgrade 2.2.15-2.5.0, Dell specific 2.2.14-6.1.1 (Red Hat Linux
6.2 does not support Pentium 4 CPUs)
Caution: VMware does not support running VMware Workstation on the stock
2.2.14-5.0 kernel.
SuSE™ Linux 8.0 — stock 2.4.18
SuSE™ Linux Enterprise Server 7 — stock 2.4.7
SuSE Linux 7.3 — stock 2.4.10
Note: If you are installing VMware Workstation on a SuSE 7.1, 7.2 or 7.3 SMP host, you need to install the non-PAE-enabled kernel on the host before you begin installing VMware Workstation. For more information, see Before You
Install on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 Host Operating System on page 39.
SuSE Linux 7.2 — stock 2.4.4
SuSE Linux 7.1 — stock 2.2.18, stock 2.4.0
SuSE Linux 7.0 — stock 2.2.16
Turbolinux 7.0
Turbolinux 6.0
Caldera® OpenLinux™ 2.4 — stock 2.2.14
Caldera OpenLinux 2.3 — stock 2.2.10
Caldera OpenLinux 2.2 — stock 2.2.5
VMware Workstation may run on other Linux distributions; attempting to do so is recommended for expert Linux users only.
Other Linux host operating system requirements:
Linux kernel 2.2.14-5.0 is not supported
Standard Linux installation with glibc version 2 or higher
Version 2.1.36 of the SCSI Generic (sg.o) driver required to use generic SCSI devices in virtual machines
VMware Workstation requires an X server
• XFree86-3.3.3.1 or higher release
• XFree86 version 3.3.4 or higher server recommended
If you are using a recent Linux distribution, it should include an appropriate X server by default. To find out what XFree86 server is running on your computer, as root, run X -version.
16
www.vmware.com
Introduction and System Requirements
Hosts Using PAE Options Not Supported
Host operating systems that use the Physical Address Extension (PAE) processor options cannot be used to run VMware Workstation 3.2. This issue affects Linux hosts if PAE is enabled in the kernel. It affects Windows hosts if booted with the /PAE option.
If you are installing VMware Workstation on a SuSE Linux 7.1, 7.2 or 7.3 SMP host, you must install the non-PAE-enabled kernel before you can install the VMware software. Please complete the steps in Before You Install on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 Host
Operating System on page 39.
www.vmware.com
17
Introduction and System Requirements

Virtual Machine Specifications

Each virtual machine created with VMware Workstation 3.2 provides a platform that includes the following devices that your guest operating system can see.
Processor
Intel Pentium II or later, depending on host processor
Intel MMX if available on host processor
Single processor per virtual machine on symmetric multiprocessor systems
Chip Set
Intel 440BX-based motherboard with NS338 SIO chip
BIOS
PhoenixBIOS 4.0 Release 6
Memory
Up to 1GB, depending on host memory
Maximum of 1GB total available for all virtual machines
Graphics
VGA and SVGA support
18
IDE Drives
Up to four devices disks, CD-ROM or DVD-ROM (DVD drives can be used to read data DVD-ROM discs; DVD video is not supported)
Hard disks can be virtual disks or physical disks
IDE virtual disks up to 128GB
CD-ROM can be a physical device or an ISO image file
SCSI Devices
Up to seven devices
SCSI virtual disks up to 256GB
Hard disks can be virtual disks or physical disks
Generic SCSI support allows devices to be used without need for drivers in the
host OS
Works with scanners, CD-ROM, DVD-ROM, tape drives and other SCSI devices
www.vmware.com
Introduction and System Requirements
Mylex® (BusLogic) BT-958 compatible host bus adapter (requires add-on driver from VMware for Windows XP and Windows .NET Server)
Floppy Drives
Up to two 1.44MB floppy devices
Physical drives or floppy image files
Serial (COM) Ports
Up to four serial (COM) ports
Output to serial ports, Windows or Linux files, or named pipes
Parallel (LPT) Ports
Up to two bidirectional parallel (LPT) ports
Output to parallel ports or host operating system files
USB ports
Two-port USB 1.1 controller
Supports devices including USB printers, scanners, PDAs, hard disk drives,
memory card readers and still digital cameras
Keyboard
104-key Windows 95/98 enhanced
Mouse and Drawing Tablets
PS/2 mouse
Serial tablets supported
Ethernet Card
Up to three virtual Ethernet cards
AMD PCnet-PCI II compatible
Sound
Sound output and input
Creative Labs Sound Blaster® 16, PCM sound compatible (MIDI sound, game
controllers and joysticks not supported.)
Virtual Networking and File Sharing
Nine virtual Ethernet switches (three reserved for bridged, host-only and NAT networking)
www.vmware.com
19
Introduction and System Requirements
Virtual Ethernet support includes TCP/IP, NetBEUI, Microsoft Networking, Samba, Novell® NetWare® and Network File System
Built-in NAT supports client software using TCP/IP, FTP, DNS, HTTP and Telnet
20
www.vmware.com
Introduction and System Requirements

Supported Guest Operating Systems

The operating systems listed here have been tested in VMware Workstation 3.2 virtual machines and are officially supported. For notes on installing the most common guest operating systems, see Installing Guest Operating Systems on page 135.
Other operating systems designed for Intel-based PCs may work, as well. For a current list of supported guest operating systems, see the support section of the VMware Web site, www.vmware.com/support/.
Microsoft Windows
Windows .NET Web Server beta 3, Windows .NET Standard Server beta 3 and Windows .NET Enterprise Server beta 3 (experimental)
Windows XP Professional and Windows XP Home Edition; Service Pack 1
Windows 2000 Professional, Windows 2000 Server and Windows 2000 Advanced
Server; Service Pack 2; Service Pack 3
Windows NT Workstation 4.0 and Windows NT Server 4.0; Service Pack 3 or higher
Windows Me
Windows 98 and Windows 98 SE
Windows 95 (all OSR releases)
Windows for Workgroups
Windows 3.1
Microsoft MS-DOS
MS-DOS 6
Linux
Mandrake Linux 8.0, 8.1and 8.2
Red Hat Linux 6.2, 7.0, 7.1, 7.2 and 7.3
SuSE Linux 7.0, 7.1, 7.2, 7.3, SLES 7 and 8.0
Turbolinux 6.0 and 7.0
Caldera OpenLinux 2.x
Novell NetWare
NetWare 6.0 (experimental)
www.vmware.com
21
Introduction and System Requirements
FreeBSD
FreeBSD 3.x, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5 and 4.6
Note: If you use SCSI virtual disks larger than 2GB with FreeBSD 3.x or 4.x (up to and including 4.3), there are known problems, and the guest operating system does not boot. To work around this issue, see Setting the Disk Geometry for a
FreeBSD SCSI Virtual Disk on page 202.
Guests Using PAE Options Not Supported
Guest operating systems that use the Physical Address Extension (PAE) processor options are not supported under VMware Workstation 3.2. This issue affects Linux guest operating systems if PAE is enabled in the kernel. It affects Windows guest operating systems if booted with the /PAE option.
Note: At this time, we are providing experimental support for NetWare 6, which is a PAE- en a b le d ke r ne l .
22
www.vmware.com
Introduction and System Requirements

What’s New in Version 3

Whether youre a long-time power user of VMware Workstation or a beginning user who is just learning what you can do with virtual machines, the new features in VMware Workstation 3 extend its capabilities and make it easier to use. Here are some highlights of the many new and improved features in this release.

New in Version 3.2

Designed for Microsoft Windows Certification
VMware Workstation 3.2 for Windows has earned Microsoft's Designed for Windows certification. This certification assures users that VMware Workstation has full functionality on Windows NT, Windows 2000 and Windows XP hosts and is designed to take advantage of new Windows XP features.
New Administrative Lockout Feature
You can require a password for access to several key administrative features — creating new virtual machines, editing virtual machine configurations and editing network settings.
Additional Host and Guest Operating System Support
You can use the latest Microsoft and Linux operating systems, including:
Microsoft® Windows® XP, Service Pack 1 beta
Microsoft Windows 2000, Service Pack 3
New Linux distributions, including Red Hat Linux 7.3, SuSE Linux 8.0 and
Turbolinux 6.0 and 7.0

New in Versions 3.0 and 3.1

Improved Host and Guest Operating System Support
You can use recent Microsoft and Linux operating systems, including:
Microsoft® Windows® .NET Web Server beta 3 (experimental)
Microsoft Windows .NET Standard Server beta 3 (experimental)
Microsoft Windows .NET Enterprise Server beta 3 (experimental)
New Linux distributions, including Mandrake Linux 8.2, Red Hat Linux 7.2 and
SuSE Linux 7.3
FreeBSD 4.5 (guest operating system only)
www.vmware.com
23
Introduction and System Requirements
Netware 6.0 guest operating system experimental support (without VMware Tools)
Note: For the most current list of supported host and guest operating systems, visit the VMware Web site at www.vmware.com/suppor t/ws3/doc/.
Improved NAT Performance and Functionality
Faster network address translation networking
Support for NetLogon, allowing you to log on to a Windows domain from a
virtual machine so you can access file shares on physical computers in the domain
Support for UDP and TCP port forwarding to connect to virtual machines
New Repeatable Resume Feature
Resume a virtual machine from a specific point at which you suspended it, over and over. This is useful for a classroom or QA environment, where you want to start your guest operating system with applications already running and system settings tailored to your needs; or, in the event of a catastrophic failure, to restart from the same point, instead of rebooting the virtual machine.
Experimental Support for Remote Desktop
Connect to your Windows host remotely through Windows Terminal Services and Windows XP Remote Desktop and launch virtual machines.
24
Full Japanese Localization on Windows Hosts
VMware Workstation for Windows hosts contains a localized graphical user interface, installer, VMware Tools, messaging and in-product Help in Japanese.
Use of Microsoft Windows Installer
On VMware Workstation for Windows hosts, take advantage of the Windows Installer to customize your Workstation installations.
Other New Features
New serial port implementation.
Note: The new serial port implementation deprecates the use of TTY-type virtual serial ports in a virtual machine.
Improved disk performance on Windows 95 and Windows 98 through direct memory access (DMA).
Simpler migration of virtual machines, which now recognize relative paths.
Improved cursor performance.
www.vmware.com
Introduction and System Requirements
Easy menu access to modify bridged networking settings for a Windows host; choose Manage Virtual Networks on the Settings menu. This menu item replaces the Settings button in the Configuration Editor on the panel for a virtual machines network adapter.
www.vmware.com
25
Introduction and System Requirements

Technical Support Resources

The VMware Web Site

The latest technical support and troubleshooting notes are available on the VMware Web site at www.vmware.com/support/.

VMware Newsgroups

The VMware newsgroups are primarily forums for users to help each other. You are encouraged to read and post issues, work-arounds and fixes. While VMware personnel may read and post to the newsgroups, they are not a channel for official support. The VMware NNTP news server is at news.vmware.com.
The following groups are devoted to discussions about VMware Workstation.
vmware.for-windowsnt.configuration vmware.for-windowsnt.general vmware.for-windowsnt.experimental vmware.for-linux.configuration vmware.for-linux.general vmware.for-linux.experimental
The following groups are for discussions about guest operating systems.
vmware.guest.windows95 vmware.guest.windows98 vmware.guest.windowsnt vmware.guest.windows2000 vmware.guest.windowsXP vmware.guest.linux vmware.guest.netware vmware.guest.misc
You can discuss .NET Server issues in the vmware.guest.windowsXP forum.
26

Reporting Problems

If you have problems while running VMware Workstation, please report them to the VMware support team.
These guidelines describe the information we need from you to diagnose problems.
If a virtual machine exits abnormally or crashes, please save the log file before you launch another virtual machine. The key log file to save is the VMware log file for the affected virtual machine on a Windows host, the vmware.log
www.vmware.com
Introduction and System Requirements
file in the same directory as the configuration file (.vmx) of the virtual machine that had problems; on a Linux host, the <vmname>.log or vmware.log file in the same directory as the configuration file (.cfg) of the virtual machine that had problems. Also save any core files (core or vmware-core). Provide these to VMware along with any other information that might help us to reproduce the problem.
If you are reporting a problem you encountered while installing VMware Workstation, it is also helpful to have your installation log file.
On a Windows host, the file is VMInst.log. It is saved in your temp folder. On a Windows NT host, the default location is C:\temp. On a Windows 2000, Windows XP or Windows .NET Server host, the default location is
C:\Documents and Settings\<username>\Local Settings\Temp. The Local Settings folder is hidden by default. To see
its contents, open My Computer, go to Tools > Folder Options, click the View tab and select Show Hidden Files and Folders.
Be sure to register your serial number. You may then report your problems by submitting a support request at www.vmware.com/requestsupport.
www.vmware.com
27
2

Installing VMware Workstation

Installing VMware Workstation
Installing and Uninstalling VMware
Workstation 3.2
The following sections describe how to install VMware Workstation on your Linux or Windows host system:
Selecting Your Host System
Installing VMware Workstation 3.2 on a Windows Host on page 31
Installing the VMware Workstation Software on page 31
Uninstalling VMware Workstation 3.2 on a Windows Host on page 35
Installing VMware Workstation 3.2 on a Linux Host on page 36
Installing the VMware Workstation Software on page 36
Before You Install on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 Host Operating System on
page 39
Uninstalling VMware Workstation 3.2 on a Linux Host on page 41

Selecting Your Host System

VMware Workstation is available for both Windows and Linux host computers. The installation files for both host platforms are included on the same CD-ROM.
Your serial number allows you to use VMware Workstation only on the host operating system for which you licensed the software. If you have a serial number for a Windows host, you cannot run the software on a Linux host, and vice versa.
To use VMware Workstation on a different host operating system for example, to use it on a Linux host if you have licensed the software for a Windows host purchase a license on the VMware Web site. You may also get an evaluation license at no charge for a 30-day evaluation of the software. For more information, see
www.vmware.com/download/.
To install on a supported Windows host computer, see Installing VMware Workstation
3.2 on a Windows Host on page 31. To install on a Linux host computer, see Installing
VMware Workstation 3.2 on a Linux Host on page 36.
30
Upgrading from Previous Versions
If you are upgrading from a previous version of VMware Workstation, read Upgrading
VMware Workstation on page 43 before you begin.
www.vmware.com
Installing VMware Workstation
Installing VMware Workstation 3.2 on a
Windows Host
Getting started with VMware Workstation is simple. The key steps are
1. Install the VMware Workstation software as described in this section.
2. Start VMware Workstation and enter your serial number. You need to do this only once the first time you start VMware Workstation after you install it.
3. Create a virtual machine using the New Virtual Machine Wizard. See Creating a
New Virtual Machine on page 59.
4. Install a guest operating system in the new virtual machine. You need the installation media (CD-ROM or floppy disks) for your guest operating system. See
Installing a Guest Operating System and VMware Tools on page 81.
5. Install the VMware Tools package inside your virtual machine for enhanced performance. See Installing VMware Tools on page 84.
6. Start using your virtual machine.
Before you begin, be sure you have
A computer and host operating system that meet the system requirements for running VMware Workstation. See Host System Requirements on page 14.
The VMware Workstation installation software. If you bought the packaged distribution of VMware Workstation, the installation software is on the CD in your package. If you bought the electronic distribution, the installation software is in the file you downloaded.
Your VMware Workstation serial number. The serial number is included in the VMware Workstation package or in the email message confirming your electronic distribution order.
The installation CD or disks for your guest operating system.

Installing the VMware Workstation Software

1. Log on to your Microsoft Windows host as the Administrator user or as a user who is a member of the Windows 2000 Administrators group.
Caution: Do not install VMware Workstation on a Windows NT Server 4.0 system that is configured as a primary or backup domain controller.
www.vmware.com
31
Installing VMware Workstation
Note: On a Windows XP or Windows .NET Server host computer, you must be
logged in as a local administrator (that is, not logged in to the domain) in order to install VMware Workstation.
Note: Although you must be logged in as an administrator to install VMware Workstation, a user with normal user privileges can run the program after it is installed. Keep in mind that you need one license for each user.
2. If you are installing from a CD, from the Start menu, choose Run and enter D:\setup.exe, where D: is the drive letter for your CD-ROM drive.
If you are installing from a downloaded file, from the Start menu, choose Run, browse to the directory where you saved the downloaded installer file (the name is similar to VMwareWorkstation-<xxxx>.exe, where <xxxx> is a series of numbers representing the version and build numbers).
3. The Welcome dialog box appears. Click Next.
32
4. Acknowledge the end user license agreement (EULA). Select the I accept the
terms in the license agreement option, then click Next.
www.vmware.com
Installing VMware Workstation
Note: If you are upgrading from VMware Workstation 3.0 and did not uninstall
the software, proceed to step 6.
5. Choose the directory in which to install VMware Workstation. To install it in a directory other than the default, click Change and browse to your directory of choice. If the directory does not exist, the installer creates it for you. Click Next.
Caution: Do not install VMware Workstation on a network drive.
Note: Windows and the Microsoft Installer limit the length of a path to a folder
to 255 characters for a path to a folder on a local drive and 240 characters for a path to a folder on a mapped or shared drive. If the path to the VMware Workstation program folder exceeds this limit, an error message appears. You must select or enter a shorter path.
6. The installer has gathered the necessary information and is ready to begin installing the software. Click Install. The installer begins copying files to your host.
www.vmware.com
33
Installing VMware Workstation
If you want to change any settings or information you provided, now is the time to make those changes. Click Back until you reach the dialog box containing the information you want to change.
7. If the installer detects that the CD-ROM autorun feature is enabled, you are prompted with the option to disable it. Disabling this feature prevents undesirable interactions with the virtual machines you install on this system.
8. On a Windows NT host, you may see a Digital Signature Not Found dialog box when the installer begins to install the VMware Virtual Ethernet Adapter. You can safely ignore this message. Click Yes to continue the installation.
9. A dialog box appears, asking if you want to rename existing virtual disks using the new .vmdk extension. Click Search Disk to search all local drives on the host computer and make this change.
One Chance to Rename Disk Files
The Rename Virtual Disks dialog box appears only once. If you click Cancel, you will not have another opportunity to update the filenames and configuration files automatically.
34
www.vmware.com
The converter also renames the files that store the state of a suspended virtual machine, if it finds them. It changes the old .std file extension to .vmss. However, it is best to resume and shut down all suspended virtual machines before you upgrade from VMware Workstation 2.0 to Workstation 3.2.
Besides renaming files, the converter updates the corresponding virtual machine configuration files so they identify the virtual disks using the new filenames.
Note: If you store your virtual disk files or suspended state files on a Windows XP or Windows .NET Server host or if you may do so in the future it is important to convert the filenames to avoid conflicts with the System Restore feature of Windows XP and Windows .NET Server.
10. Click Finish . The VMware Workstation software is installed.
Installing VMware Workstation
11. A prompt suggests that you reboot your PC. Reboot now to allow VMware Workstation to complete the installation correctly.

Uninstalling VMware Workstation 3.2 on a Windows Host

To uninstall VMware Workstation 3.2, use the VMware Workstation uninstaller.
1. Launch the uninstaller. Start > Programs > VMware > VMware Workstation Uninstallation
2. Click Yes.
3. Follow the on-screen instructions.
Near the end of the uninstallation process, you are asked if you want to remove your VMware Workstation licenses. If you click Yes, all licenses on the host computer are permanently removed.
www.vmware.com
35
Installing VMware Workstation
Installing VMware Workstation 3.2 on a
Linux Host
Getting started with VMware Workstation is simple. The key steps are
1. Install the VMware Workstation software as described in this chapter.
2. Start VMware Workstation and enter your serial number. You need to do this only once the first time you start VMware Workstation after you install it.
3. Create a virtual machine using the Configuration Wizard. See Creating a New
Virtual Machine on page 59.
4. Install a guest operating system in the new virtual machine. You need the installation media (CD-ROM or floppy disks) for your guest operating system. See
Installing a Guest Operating System and VMware Tools on page 81.
5. Install the VMware Tools package inside your virtual machine for enhanced performance. See Installing VMware Tools on page 84.
6. Start using your virtual machine.
Before you begin, be sure you have
A computer and host operating system that meet the system requirements for running VMware Workstation. See Host System Requirements on page 14.
The VMware Workstation installation software. If you bought the packaged distribution of VMware Workstation, the installation software is on the CD in your package. If you bought the electronic distribution, the installation software is in the file you downloaded.
Your VMware Workstation serial number. The serial number is included in the VMware Workstation package or in the email message confirming your electronic distribution order.
The installation CD or disks for your guest operating system.
36

Installing the VMware Workstation Software

If you are installing VMware Workstation on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 SMP host, please read Before You Install on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 Host Operating
System on page 39.
Note: The steps below describe an installation from a CD-ROM disc. If you downloaded the software, the steps are the same except that you start from the
www.vmware.com
Installing VMware Workstation
directory where you saved the installer file you downloaded, not from the Linux directory on the CD.
1. Log on to your Linux host with the user name you plan to use when running VMware Workstation.
2. In a terminal window, become root so you can carry out the initial installation steps.
su -
3. Mount the VMware Workstation CD-ROM.
4. Change to the Linux directory on the CD.
5. Do one of the following:
To use the RPM installer, run RPM specifying the installation file.
rpm -Uhv VMware-<xxx>.rpm (where VMware-<xxx>.rpm is the installation file on the CD; in place of <xxx> the filename contains numbers that correspond to the version and
build)
Note: If you are upgrading from VMware Workstation 3.0, before you install the RPM package, you need to remove the prebuilt modules RPM package included in the 3.0 release. To remove the modules, type the following at a command prompt:
rpm -e VMwareWorkstationKernelModules
To use the tar installer, you may either copy a tar archive to your hard disk and
install following the directions below, or skip the steps for copying and unpacking the archive and install directly from the vmware-distrib directory on the CD. Copy the tar archive to a directory on your hard drive, for example, /tmp.
cp VMware-<xxx>.tar.gz /tmp
Change to the directory to which you copied the file.
cd /tmp
Unpack the archive.
tar zxf VMware-<xxxx>.tar.gz
Change to the installation directory.
cd vmware-distrib
Run the installation script.
./vmware-install.pl
Accept the default directories for binary files, library files, manual files, documentation files and init script.
www.vmware.com
37
Installing VMware Workstation
6. Run the configuration script.
vmware-config.pl
Note: If you use the RPM installer, you need to run this script separately from the command line. If you install from the tar archive, the installer offers to launch the configuration script for you. Answer Yes when you see the prompt.
Use this script to reconfigure VMware Workstation whenever you upgrade your kernel. It is not necessary to reinstall VMware Workstation after you upgrade your kernel.
You can also use vmware-config.pl to reconfigure the networking options for VMware Workstation for example, to add or remove host-only networks.
7. Press Enter to read the end user license agreement (EULA). You may page through it by pressing the space bar. If the Do you accept… prompt doesn’t appear, press Q to get to the next prompt.
8. The remaining prompts are worded in such a way that, in most cases, the default response is appropriate. Some exceptions are noted here:
The configuration script prompts you
Do you want this script to automatically configure your system to allow your virtual machines to access the host's file system?
If you already have Samba running on your host computer, answer No. If Samba is not already running on your host computer, answer Yes to this question; the VMware Workstation installer configures it for you. When prompted for a user name and password to use with the Samba configuration, enter the user name you used in step 1 above.
To enable host-only networking, respond Yes to the following prompts if they
appear:
Do you want your virtual machines to be able to use the host's network resources? Do you want to be able to use host-only networking in your virtual machines? Do you want this script to probe for an unused private subnet?
This allows for the sharing of files between the virtual machine and the host operating system. For more information, see Host-Only Networking on
page 280.
38
www.vmware.com
Installing VMware Workstation
Note: If you do not enable host-only networking now, you cannot allow a
virtual machine to use both bridged and host-only networking.
9. The configuration program displays a message saying the configuration completed successfully. If it does not, run the installation program again.
10. When done, exit from the root account. exit

Before You Install on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 Host Operating System

If you are installing VMware Workstation on a SuSE Linux 7.1, 7.2, 7.3 or 8.0 host operating system running an SMP (symmetric multiprocessor) kernel, you need to install the non-PAE-enabled kernel for your SuSE Linux 7.1, 7.2, 7.3 or 8.0 SMP host before you can install the VMware software.
SuSE Linux 7.1, 7.2, 7.3 and 8.0 SMP kernels implement 64GB PAE memory and are not supported. For SuSE Linux 7.1 and 7.2 hosts, the non-PAE-enabled versions of these SMP kernels can be installed from the RPM package available on the SuSE distribution CD-ROM (/suse/images/k_psmp.rpm). For a SuSE Linux 7.3 or 8.0 host, you can select the non-PAE-enabled SMP kernel by running the YaST2 configuration utility.
The VMware Workstation installer contains prebuilt modules that work with the non­PAE-enabled kernels for SuSE Linux 7.1, 7.2, 7.3 and 8.0 SMP distributions.
Installing the Non-PAE-Enabled Kernel on a SuSE Linux 7.1 or 7.2 Host
1. Mount the SuSE CD-ROM containing the non-PAE-enabled kernel package.
mount -t iso9660 /dev/cdrom /mnt/cdrom
2. Save your current kernel and, if necessary, your current initrd.
cp /boot/vmlinuz /boot/vmlinuz.old
cp /boot/initrd /boot/initrd.old
3. Uninstall the current kernel package.
rpm -e k_smp-2.4.4-14
4. Install the new kernel package.
rpm -Uhv /mnt/cdrom/suse/images/k_psmp.rpm
5. Create a new initial ram disk, which holds the drivers used for accessing your root file system (for example, if it resides on a SCSI disk). If your system does not need a ram disk, it won't be created.
mk_initrd
www.vmware.com
39
Installing VMware Workstation
6. Reconfigure the Linux loader (LILO).
lilo
Note: If you are using LOADLIN, you have to copy the /boot/vmlinuz kernel image and the /boot/initrd initial ram disk to your DOS partition.
7. Reboot your SuSE host operating system.
Installing the Non-PAE-Enabled Kernel on a SuSE 7.3 or 8.0 Host
1. Log in as root and run YaST2.
2. Click System, then Select kernel.
3. Select Kernel 2.4 with SMP -- support for older processors (Pentium Classic). This selects the 4GB non-PAE-enabled kernel.
4. Click Finis h, then click Close to exit YaST. When you reboot your host machine in the next step, the new kernel is selected and the inetd process automatically starts.
5. Reboot your SuSE Linux host operating system.
After you finish configuring your SuSE Linux 7.1, 7.2, 7.3 or 8.0 host operating system, you are ready to install VMware Workstation.
40
www.vmware.com
Installing VMware Workstation

Uninstalling VMware Workstation 3.2 on a Linux Host

If you used the RPM installer to install VMware Workstation, remove the software from your system by running
rpm -e VMwareWorkstation
If you used the tar installer to install VMware Workstation, remove the software from your system by running
vmware-uninstall.pl
www.vmware.com
41
3

Upgrading VMware Workstation

Upgrading VMware Workstation
Upgrading from VMware
Workstation 2.0, 3.0 and 3.1
The following sections describe how to upgrade VMware Workstation from version
2.0, 3.0 and 3.1 to version 3.2 on your Linux or Windows host system and how to use existing virtual machines under VMware Workstation 3.2:
Preparing for the Upgrade on page 45
Upgrading on a Windows Host on page 47
Upgrading on a Linux Host on page 53
Upgrading from VMware Workstation 1.x or VMware Express on page 58
44
www.vmware.com
Upgrading VMware Workstation

Preparing for the Upgrade

Before You Install VMware Workstation 3.2

There are a few steps you should take while your previous version of VMware Workstation is still on your computer and before you install VMware Workstation 3.2 to ensure the best possible upgrade experience.
Resume and Shut Down Suspended Virtual Machines
If you plan to use virtual machines created under VMware Workstation 2.0, 3.0, 3.1 or a prerelease version of VMware Workstation 3.2, be sure they have been shut down completely before you remove the release you used to create them.
If the virtual machine is suspended, resume it in the earlier release, shut down the guest operating system, then power off the virtual machine.
Note: If you attempt to resume a virtual machine that was suspended under a different VMware product or a different version of VMware Workstation, a dialog box gives you the choice of discarding or keeping the file that stores the suspended state. To recover the suspended state, you must click Keep, then resume the virtual machine under the correct VMware product. If you click Discard, you can power on normally, but the suspended state is lost.
Commit or Discard Changes to Disks in Undoable Mode
If you plan to use existing virtual machines that have disks in undoable mode, commit or discard any changes to the virtual disks before you remove the release you used to create them.
Resume or power on the virtual machine in the earlier release, shut down the guest operating system, power off the virtual machine and either commit or discard changes to the disk in undoable mode when prompted.
Back Up Virtual Machines
As a precaution, back up all the files in your virtual machine directories including the .vmdk or .dsk, .cfg or .vmx and nvram files for any existing virtual machines you plan to migrate to VMware Workstation 3.2.
Virtual machines updated for full compatibility with VMware Workstation 3.2 cannot be used under VMware Workstation 2.0.
www.vmware.com
45
Upgrading VMware Workstation

When You Remove Version 2.0 and Install Version 3.2

There is a key precaution you should take when you remove VMware Workstation 2.0 or a prerelease version of VMware Workstation 3.2 and install VMware Workstation 3.2.
Note: You should also take the following into consideration if you decide to uninstall version 3.0 or 3.1.
Leave the Existing License in Place
The installation steps for your host may require that you run an uninstaller to remove a previous version of VMware Workstation from your machine.
On a Windows host, the uninstaller offers to remove licenses from your registry. If you think you may want to use the previous version of VMware Workstation again, do not remove the licenses. You can safely keep licenses for multiple VMware products on the computer at the same time.
On a Linux host, the license remains in place. You do not need to take any special action. You may safely leave the license where it is.
46
www.vmware.com
Upgrading VMware Workstation

Upgrading on a Windows Host

Upgrading from Version 2.0, 3.0 or 3.1 to 3.2

The Upgrade Process
In most cases, upgrading from version 2.0, 3.0 or 3.1 is a four-step process. If you are upgrading from Workstation 2.0 on a Windows 2000 host that has host-only networking, there is an additional step. See Upgrading on a Windows 2000 Host with
Host-Only Networking below for details.
1. Uninstall the version now installed on your computer.
2. Reboot your computer.
3. Install version 3.2.
4. Reboot your computer.
Removing Version 2.0
To uninstall version 2.0, use the VMware Workstation uninstaller.
1. Launch the uninstaller. Start > Programs > VMware > VMware for Windows NT Uninstallation
2. Click Yes.
3. Follow the on-screen instructions. You may safely keep your existing licence in the Windows registry.
After you reboot, follow the instructions in Installing VMware Workstation 3.2 on a
Windows Host on page 31.
Removing Version 3.0 or 3.1
To uninstall version 3.0 or 3.1, use the VMware Workstation uninstaller.
1. Launch the uninstaller. Start > Programs > VMware > VMware Workstation Uninstallation
2. Click Yes.
3. Follow the on-screen instructions. You may safely keep your existing licence in the Windows registry.
After you reboot, follow the instructions in Installing VMware Workstation 3.2 on a
Windows Host on page 31.
www.vmware.com
47
Upgrading VMware Workstation
Upgrading on a Windows 2000 Host with Host-Only Networking
If you have set up host-only networking for VMware Workstation 2.0 on a Windows 2000 host, the upgrade process has five steps.
1. Uninstall your host-only adapter (or adapters).
A. On the host computer, start the Add/Remove Hardware Wizard.
Start > Settings > Control Panel > Add/Remove Hardware Click Next.
B. Select Uninstall/Unplug a Device. Click Next.
C. Select Uninstall a Device. Click Next.
D. Select VMware Virtual Ethernet Adapter, then follow the wizard’s
instructions.
If you have more than one host-only adapter, repeat these steps for each of them.
2. Uninstall version 2.0.
3. Reboot your computer.
4. Install version 3.2.
5. Reboot your computer.
48
Using Virtual Machines Created with Version 2.0 under Version 3.2
There are, broadly speaking, three approaches you can take to setting up virtual machines under VMware Workstation 3.2. Choose one of these approaches. There are no issues using virtual machines created under VMware Workstation 3.0 or 3.1.
Create everything new from the start. Use the New Virtual Machine Wizard to set up a new virtual machine and install a guest operating system in the virtual machine as described in Creating a New Virtual Machine on page 59. If you set up your virtual machines in this way, you will be using the latest technology and will enjoy the best possible virtual machine performance.
Use an existing configuration file (.vmx) and virtual disk (.dsk if you do not convert to new filenames when you install VMware Workstation or .vmdk if you do convert).
Upgrade VMware Tools to the new version following the instructions for your guest operating system in Installing VMware Tools on page 84. You should not remove the older version of VMware Tools before installing the new version.
A virtual machine set up in this way should run without problems. However, you will not have the benefits of certain new features. You will not have USB ports.
www.vmware.com
Upgrading VMware Workstation
You will not have the new BIOS, which makes it easier to use one of the operating systems on a dual-boot host machine as a guest operating system in a virtual machine. Also, you will not have the new unified virtual video hardware, which helps simplify the installation of VMware Tools.
Note: On Windows hosts, VMware Workstation 3.2 offers to convert virtual disk .dsk filenames to use the new .vmdk extension at the time you install VMware Workstation. If you are storing virtual disk files on a Windows XP or Windows .NET Server host, it is especially important that you allow VMware Workstation to make this change in order to avoid conflicts with the Windows XP or Windows .NET Server System Restore feature. The .vmdk extension can be used for virtual disks under any VMware product. VMware Workstation 3.2 automatically updates references to the virtual disk files in configuration files on the host computer. If you are using the same virtual disk file from any other computer, you need to update the configuration files with the new filename. For details, see Updating Filenames for Virtual Disks Created with Earlier VMware
Products on page 224.
Use an existing virtual machine and upgrade the virtual hardware. This gives you access to new features, but the process is one-way you cannot reverse it.
Start by using an existing configuration file (.vmx) and virtual disk (.dsk if you do not convert to new filenames when you install VMware Workstation or .vmdk if you do convert).
Upgrade VMware Tools to the new version following the instructions for your guest operating system in Installing VMware Tools on page 84. You should not remove the older version of VMware Tools before installing the new version.
Upgrade the virtual hardware so you can use USB devices in your virtual machine.
Note: On Windows hosts, VMware Workstation 3.2 offers to convert virtual disk .dsk filenames to use the new .vmdk extension at the time you install VMware Workstation. If you are storing virtual disk files on a Windows XP or Windows .NET Server host, it is especially important that you allow VMware Workstation to make this change in order to avoid conflicts with the Windows XP or Windows .NET Server System Restore feature. The .vmdk extension can be used for virtual disks under any VMware product. VMware Workstation 3.2 automatically updates references to the virtual disk files in configuration files on the host computer. If you are using the same virtual disk file from any other computer, you need to update the configuration files with the new filename. For
www.vmware.com
49
Virtual Hardware Upgrade Is Irreversible
The process of upgrading the virtual hardware is irreversibl e and makes the disks attached to this virtual machine incompatible with Workstation 2.0. You should make backup copies of your virtual disks before starting the upgrade.
Upgrading VMware Workstation
details, see Updating Filenames for Virtual Disks Created with Earlier VMware
Products on page 224.
Upgrading the Virtual Hardware in an Existing Virtual Machine
On the Settings menu, choose Upgrade Virtual Hardware. A dialog box appears, warning that the upgrade process cannot be reversed. Click Yes to continue, then follow the directions.
If you are using a Windows 95, Windows 98 or Windows Me virtual machine created under VMware Workstation 2.0 and choose to upgrade the virtual hardware, you need to take several steps to be sure the new virtual hardware is recognized properly by the guest operating system. With other guest operating systems, these special steps are not needed.
Before you upgrade the virtual hardware, make sure you have installed the latest version of VMware Tools, including the SVGA driver, then power off your virtual machine.
Take the steps listed under the name of your guest operating system.
Windows Me Guest
1. Choose Settings > Upgrade Virtual Hardware.
2. A warning message appears. It says: This operation will cause the virtual hardware your guest operating system runs on to change…”
Click Yes.
3. Click Po wer On.
4. Click OK to dismiss the message A legacy SVGA driver has been detected.
5. Several Plug and Play messages appear. You can safely ignore them.
6. Log on to Windows Me. More Plug and Play messages are displayed. One refers to the VMware SVGA driver.
Click Yes to restart your computer.
7. Log on to Windows Me. The SVGA driver is not working properly.
8. From the Windows Start menu, choose Settings > Control Panel > System > Device Manager > Display Adapters.
Manually remove the two SVGA drivers.
9. Restart Windows Me.
A VMware SVGA II adapter is detected and Windows installs it.
Windows notifies you to restart your computer.
50
www.vmware.com
Upgrading VMware Workstation
Click Yes.
10. The SVGA driver should be working correctly.
Windows 98 Guest
1. Choose Settings > Upgrade Virtual Hardware.
2. A warning message appears. It says: This operation will cause the virtual hardware your guest operating system runs on to change…”
Click Yes.
3. Click Power On.
4. Click OK to dismiss the message A legacy SVGA driver has been detected.
5. Log on to Windows 98. You see a number of Plug and Play messages. You may need to insert your Windows 98 installation CD.
6. A blue screen appears. Press any key to dismiss the blue screen.
7. Click Reset to restart the virtual machine (because it is not responding).
8. Click OK to dismiss the message A legacy SVGA driver has been detected.
Again, you see a number of Plug and Play messages.
Windows notifies you to restart Windows.
Click Yes.
9. Log on to Windows 98. The SVGA driver is not working properly.
10. From the Windows Start menu, choose Settings > Control Panel > System > Device Manager > Display Adapters.
Manually remove the two conflicting SVGA drivers.
11. Restart Windows 98.
A VMware SVGA II adapter is detected and Windows installs it.
12. Restart Windows 98.
13. The SVGA driver should be working correctly.
Windows 95 Guest
1. Choose Settings > Upgrade Virtual Hardware.
2. A warning message appears. It says: This operation will cause the virtual hardware your guest operating system runs on to change…"
Click Yes.
3. Click Power On.
www.vmware.com
51
Upgrading VMware Workstation
4. Click OK to dismiss the message A legacy SVGA driver has been detected.
5. Log on to Windows 95.
You see a number of Plug and Play messages. Click Cancel for the following devices: Standard host CPU bridge, PCI bridge and PCI Universal bus.
6. The SVGA driver is not working properly.
7. From the Windows Start menu, choose Settings > Control Panel > System > Device Manager > Display Adapters.
Manually remove the SVGA driver.
8. Restart Windows 95.
9. Again, you see a number of Plug and Play messages. Click Cancel for the following devices: Standard host CPU bridge, PCI bridge and PCI Universal bus.
10. A VMware SVGA II adapter is detected and Windows installs it.
11. Restart Windows 95.
12. Once again, you see a number of Plug and Play messages. Again, click Cancel for the following devices: Standard host CPU bridge, PCI bridge and PCI Universal bus.
13. The SVGA driver should be working correctly.
52
Check Guest Operating System Selection
If your guest operating system is Windows 2000, update the setting in the Configuration Editor (Settings > Configuration Editor > Options) to reflect the specific version of Windows 2000 you are running.
www.vmware.com
Upgrading VMware Workstation

Upgrading on a Linux Host

Removing Version 2.0, 3.0 or 3.1
If you used the tar installer to install version 2.0, 3.0 or 3.1, and you plan to use the tar installer for version 3.2, you do not need to take any special steps to uninstall the older version. Just follow the installation instructions Installing VMware Workstation 3.2 on a
Linux Host on page 36.
If you used the RPM installer to install version 2.0, 3.0 or 3.1, you need to take the following steps to upgrade to version 3.2.
Note: If you are currently using version 3.0, you need to uninstall the prebuilt modules RPM package that was installed with 3.0 before you uninstall the 3.0 software. You do not need to take this step if you are currently using version 2.0 or 3.1.
1. If you are running version 2.0, uninstall it as root by running
rpm -e VMware
If you are running version 3.0, as root uninstall the prebuilt modules, then uninstall VMware Workstation by running
rpm -e VMwareWorkstationKernelModules rpm -e VMwareWorkstation
If you are running version 3.1, uninstall it as root by running
rpm -e VMwareWorkstation
2. Install version 3.2 following the instructions in Installing VMware Workstation 3.2
on a Linux Host.
Using Virtual Machines Created with Version 2.0 under Version 3.2
There are, broadly speaking, three approaches you can take to setting up virtual machines under VMware Workstation 3.2. Choose one of these approaches. There are no issues using virtual machines created under VMware Workstation 3.0 or 3.1.
Create everything new from the start. Use the Configuration Wizard to set up a new virtual machine and install a guest operating system in the virtual machine as described in Creating a New Virtual Machine on page 59. If you set up your virtual machines in this way, you will be using the latest technology and will enjoy the best possible virtual machine performance.
Use an existing configuration file (.vmx) and virtual disk (.dsk if you do not convert to new filenames when you install VMware Workstation or .vmdk if you do convert).
www.vmware.com
53
Upgrading VMware Workstation
Upgrade VMware Tools to the new version following the instructions for your guest operating system in Installing VMware Tools on page 84. You should not remove the older version of VMware Tools before installing the new version.
A virtual machine set up in this way should run without problems. However, you will not have the benefits of certain new features. You will not have USB ports. You will not have the new BIOS, which makes it easier to use one of the operating systems on a dual-boot host machine as a guest operating system in a virtual machine. Also, you will not have the new unified virtual video hardware, which helps simplify the installation of VMware Tools.
Note: On Linux hosts, VMware Workstation 3.2 offers to convert virtual disk .dsk filenames to use the new .vmdk extension the first time you run a virtual machine after installing VMware Workstation. If you are storing virtual disk files on a Windows XP or Windows .NET Server computer a file server, for example it is especially important that you allow VMware Workstation to make this change in order to avoid conflicts with the Windows XP or Windows .NET Server System Restore feature. The .vmdk extension can be used for virtual disks under any VMware product. VMware Workstation 3.2 automatically updates references to the virtual disk files in configuration files on the host computer. If you are using the same virtual disk file from any other computer, you need to update the configuration files with the new filename. For details, see Updating Filenames for
Virtual Disks Created with Earlier VMware Products on page 224.
Use an existing virtual machine and upgrade the virtual hardware. This gives you access to new features, but the process is one-way you cannot reverse it.
Start by using an existing configuration file (.cfg) and virtual disk (.dsk if you do not convert to new filenames when you install VMware Workstation or .vmdk if you do convert).
Upgrade VMware Tools to the new version following the instructions for your guest operating system in Installing VMware Tools on page 84. You should not remove the older version of VMware Tools before installing the new version.
Upgrade the virtual hardware so you can use USB devices in your virtual machine.
Note: On Linux hosts, VMware Workstation 3.2 offers to convert virtual disk .dsk filenames to use the new .vmdk extension the first time you run a virtual machine after installing VMware Workstation. If you are storing virtual disk files on a Windows XP or Windows .NET Server computer a file server, for example it is especially important that you allow VMware Workstation to make this change in order to avoid conflicts with the Windows XP or Windows .NET Server
54
www.vmware.com
Upgrading VMware Workstation
System Restore feature. The .vmdk extension can be used for virtual disks under any VMware product. VMware Workstation 3.2 automatically updates references to the virtual disk files in configuration files on the host computer. If you are using the same virtual disk file from any other computer, you need to update the configuration files with the new filename. For details, see Updating Filenames for
Virtual Disks Created with Earlier VMware Products on page 224.
Upgrading the Virtual Hardware in an Existing Virtual Machine
On the Settings menu, choose Upgrade Virtual Hardware. A dialog box appears, warning that the upgrade process cannot be reversed. Click Yes to continue, then follow the directions.
If you are using a Windows 95, Windows 98 or Windows Me virtual machine created under VMware Workstation 2.0 and choose to upgrade the virtual hardware, you need to take several steps to be sure the new virtual hardware is recognized properly by the guest operating system. With other guest operating systems, these special steps are not needed.
Before you upgrade the virtual hardware, make sure you have installed the latest version of VMware Tools, including the SVGA driver, then power off your virtual machine.
Take the steps listed under the name of your guest operating system.
Virtual Hardware Upgrade Is Irreversible
The process of upgrading the virtual hardware is irreversibl e and makes the disks attached to this virtual machine incompatible with Workstation 2.0. You should make backup copies of your virtual disks before starting the upgrade.
Windows Me Guest
1. Choose Settings > Upgrade Virtual Hardware.
2. A warning message appears. It says: This operation will cause the virtual hardware your guest operating system runs on to change…”
Click Yes.
3. Click Power On.
4. Click OK to dismiss the message A legacy SVGA driver has been detected.
5. Several Plug and Play messages appear. You can safely ignore them.
6. Log on to Windows Me. More Plug and Play messages are displayed. One refers to the VMware SVGA driver.
Click Yes to restart your computer.
7. Log on to Windows Me. The SVGA driver is not working properly.
8. From the Windows Start menu, choose Settings > Control Panel > System > Device Manager > Display Adapters.
Manually remove the two SVGA drivers.
www.vmware.com
55
Upgrading VMware Workstation
9. Restart Windows Me.
A VMware SVGA II adapter is detected and Windows installs it.
Windows notifies you to restart your computer.
Click Yes.
10. The SVGA driver should be working correctly.
Windows 98 Guest
1. Choose Settings > Upgrade Virtual Hardware.
2. A warning message appears. It says: This operation will cause the virtual hardware your guest operating system runs on to change…”
Click Yes.
3. Click Po wer On.
4. Click OK to dismiss the message A legacy SVGA driver has been detected.
5. Log on to Windows 98. You see a number of Plug and Play messages. You may need to insert your Windows 98 installation CD.
6. A blue screen appears. Press any key to dismiss the blue screen.
7. Click Reset to restart the virtual machine (because it is not responding).
8. Click OK to dismiss the message A legacy SVGA driver has been detected.
Again, you see a number of Plug and Play messages.
Windows notifies you to restart Windows.
Click Yes.
9. Log on to Windows 98. The SVGA driver is not working properly.
10. From the Windows Start menu, choose Settings > Control Panel > System > Device Manager > Display Adapters.
Manually remove the two conflicting SVGA drivers.
11. Restart Windows 98.
A VMware SVGA II adapter is detected and Windows installs it.
12. Restart Windows 98.
13. The SVGA driver should be working correctly.
56
Windows 95 Guest
1. Choose Settings > Upgrade Virtual Hardware.
www.vmware.com
Upgrading VMware Workstation
2. A warning message appears. It says: This operation will cause the virtual hardware your guest operating system runs on to change…"
Click Yes.
3. Click Power On.
4. Click OK to dismiss the message A legacy SVGA driver has been detected.
5. Log on to Windows 95.
You see a number of Plug and Play messages. Click Cancel for the following devices: Standard host CPU bridge, PCI bridge and PCI Universal bus.
6. The SVGA driver is not working properly.
7. From the Windows Start menu, choose Settings > Control Panel > System > Device Manager > Display Adapters.
Manually remove the SVGA driver.
8. Restart Windows 95.
9. Again, you see a number of Plug and Play messages. Click Cancel for the following devices: Standard host CPU bridge, PCI bridge and PCI Universal bus.
10. A VMware SVGA II adapter is detected and Windows installs it.
11. Restart Windows 95.
12. Once again, you see a number of Plug and Play messages. Again, click Cancel for the following devices: Standard host CPU bridge, PCI bridge and PCI Universal bus.
13. The SVGA driver should be working correctly.
Check Guest Operating System Selection
If your guest operating system is Windows 2000, update the setting in the Configuration Editor (Settings > Configuration Editor > Misc) to reflect the specific version of Windows 2000 you are running.
www.vmware.com
57
Upgrading VMware Workstation
Upgrading from VMware Workstation
1.x or VMware Express
If you are upgrading from VMware Workstation 1.x, uninstall version 1.x, then follow the instructions for a new installation of VMware Workstation 3.2. See Installing
VMware Workstation 3.2 on a Windows Host on page 31 or Installing VMware Workstation 3.2 on a Linux Host on page 36.
Note: VMware does not recommend migrating virtual machines created under version 1.x to version 3.2. If you have virtual machines created under version 1.x and need to use them under version 3.2, you should first upgrade to VMware Workstation
2.0, run the virtual machines under version 2.0 and upgrade VMware Tools, then upgrade to VMware Workstation 3.2.
To upgrade from VMware Express to VMware Workstation, uninstall VMware Express, then follow the instructions for a new installation of VMware Workstation 3.2. See
Installing VMware Workstation 3.2 on a Linux Host on page 36.
To migrate virtual machines created with VMware Express for use under VMware Workstation 3.2, follow the instructions for migrating virtual machines from VMware Workstation 2.0 to Workstation 3.2. See Upgrading on a Linux Host on page 53.
58
www.vmware.com
4

Creating a New Virtual Machine

Creating a New Virtual Machine

Preparing to Run a Virtual Machine

The following sections describe how to create a new virtual machine and install VMware Tools:
Setting up a New Virtual Machine on a Windows Host on page 61
Whats in a Virtual Machine on a Windows Host? on page 61
Simple Steps to a New Virtual Machine on a Windows Host on page 62
Setting up a New Virtual Machine on a Linux Host on page 69
Whats in a Virtual Machine on a Linux Host? on page 69
Simple Steps to a New Virtual Machine on a Linux Host on page 70
Installing a Guest Operating System and VMware Tools on page 81
Installing Windows Me as a Guest Operating System on page 82
Installing VMware Tools on page 84
VMware Tools Configuration Options on page 92
60
www.vmware.com
Creating a New Virtual Machine
Setting up a New Virtual Machine
on a Windows Host
The New Virtual Machine Wizard guides you through the key steps for setting up a new virtual machine, helping you set various options and parameters. You can then use the Configuration Editor (Settings > Configuration Editor) if you need to make any changes to your virtual machines setup.
A new virtual machine is like a physical computer with a blank hard disk. Before you can use it, you need to format the virtual disk and install an operating system. The operating systems installation program may handle the formatting step for you.

Whats in a Virtual Machine on a Windows Host?

The virtual machine typically is stored on the host computer in a set of files, all of which are in a folder set aside for that particular virtual machine. In these examples, <vmname> is the name of your virtual machine. The key files are:
<vmname>.vmx the configuration file, which stores settings chosen in the New Virtual Machine Wizard or Configuration Editor.
nvram the file that stores the state of the virtual machines BIOS.
<vmname>.vmdk the virtual disk file, which stores the contents of the
virtual machines hard disk drive.
A virtual disk comprises one or more .vmdk files. The larger the size of the virtual disk, the more .vmdk files. As data is added to a virtual disk, the .vmdk files grow in size, to a maximum of 2GB each. Almost all of a .vmdk files content is the virtual machines data, with a small portion allotted to virtual machine overhead. If the virtual disk is 2GB or larger, VMware Workstation creates multiple .vmdk files.
If the virtual machine is connected directly to a physical disk, rather than using a virtual disk, there is no .vmdk file. Instead, a .raw file stores information about the partitions the virtual machine is allowed to access.
Note: Earlier VMware products used the extension .dsk for virtual disk files.
vmware.log the file that keeps a log of key VMware Workstation activity. This can be useful in troubleshooting if you encounter problems. This file is stored in the folder that holds the configuration (.vmx) file of the virtual machine.
www.vmware.com
61
Creating a New Virtual Machine
<vmname>.vmdk.REDO the redo-log file, created automatically when a virtual machine is used in undoable or nonpersistent mode. This file stores changes made to the virtual disk while the virtual machine is running.
<vmname>.vmss the suspended state file, which stores the state of a suspended virtual machine.
Note: Earlier VMware products used the extension .std for suspended state files.
There may be other files as well, some of which are present only while a virtual machine is running.

Simple Steps to a New Virtual Machine on a Windows Host

By default, the new virtual machine uses an IDE disk in persistent mode for Windows 95, Windows 98, Windows Me, Windows XP, Windows .NET Server and FreeBSD guests. The default for other guest operating systems is a SCSI disk in persistent mode.
Follow these steps to create a virtual machine using a virtual disk.
1. Start VMware Workstation. If you allowed the installer to place a VMware Workstation icon on your desktop, double-click the icon. Otherwise, use the Start menu (Start > Programs > VMware > VMware Workstation).
2. If this is the first time you have launched VMware Workstation, you are prompted to enter your 20-character serial number. This number is on the registration card in your package. Enter your serial number and click OK.
The serial number you enter is saved in your license file and VMware Workstation does not ask you for it again. For your convenience, VMware Workstation automatically sends the serial number to the VMware Web site when you use certain Web links built into the product (for example, Help > VMware software
on the Web > Register Now! and Help > VMware software on the Web > Request Support). This allows us to direct you to the correct Web page for
registration and support for your product.
3. Start the New Virtual Machine Wizard.
When you start VMware Workstation, you can open an existing virtual machine or create a new one. Click New Virtual Machine to begin creating your virtual machine.
4. The New Virtual Machine Wizard presents you with a series of screens that you navigate using the Next and Prev buttons at the bottom of each screen. At each screen, follow the instructions, then click Next to proceed to the next screen.
62
www.vmware.com
Creating a New Virtual Machine
5. Select the method you want to use for configuring your virtual machine.
If you select Typical, the wizard prompts you to specify or accept defaults for
The guest operating system
The virtual machine name and the location of the virtual machines files
The network connection type
If you select Custom, you also can specify how to set up your disk create a new virtual disk, use an existing virtual disk or use a physical disk and make the settings needed for the type of disk you select.
Select Custom if you want to
Make a virtual disk larger or smaller than 4GB
Store your virtual disks files in a particular location
Use an IDE virtual disk for a guest operating system that would otherwise
have a SCSI virtual disk created by default
Use a physical disk rather than a virtual disk (for expert users)
Select VMware Guest OS Kit if you have a Guest OS Kit and want to use it to create a preconfigured virtual machine using a virtual disk. If you select VMware Guest OS Kit, the wizard asks you to specify the drive where you have placed the Guest OS Kit CD-ROM. When you click Finish, it launches the Guest OS Kit installation program. For more information on VMware Guest OS Kits, see
www.vmware.com/products/guestoskits/.
www.vmware.com
63
Creating a New Virtual Machine
6. Select a guest operating system.
This screen asks which operating system to install in the virtual machine. The New Virtual Machine Wizard uses this information to select appropriate default values, such as the amount of disk space needed. The wizard also uses this information when naming associated virtual machine files.
If the operating system you are using is not listed, select Other.
The remaining steps assume you plan to install a Windows Me guest operating system. You can find detailed installation notes for this and other guest operating systems in Installing Guest Operating Systems on page 135.
7. Select a name and folder for the virtual machine.
64
The name specified here appears in the Virtual Machine Name list on VMware Workstations opening screen. It is also used as the name of the folder where the files associated with this virtual machine are stored.
Each virtual machine should have its own folder. All associated files, such as the configuration file and the disk file, are placed in this folder. On Windows 2000, Windows XP and Windows .NET Server, the default folder is C:\Documents
and Settings\<username>\My Documents\My Virtual Machines\Windows Me. On Windows NT, the default folder is
www.vmware.com
Creating a New Virtual Machine
C:\WINNT\Profiles\<username>\Personal\My Virtual Machines\Windows Me.
Virtual machine performance may be slower if your virtual hard disk is on a network drive. For best performance, be sure the virtual machines folder is on a local drive. However, if others users need to access this virtual machine, you should consider placing the virtual machine files in a location that is accessible to them. For more information, see Sharing Virtual Machines with Other Users on
page 134.
8. Configure the networking capabilities of the virtual machine.
If your host computer is on a network and you have a separate IP address for your virtual machine (or can get one automatically from a DHCP server), select Use bridged networking.
If you do not have a separate IP address for your virtual machine but you want to be able to connect to the Internet, select Use network address translation (NAT). NAT is useful if you have a wireless NIC on your host (as bridged networking is not supported on wireless NICs) and allows for the sharing of files between the virtual machine and the host operating system.
For more details about VMware Workstation networking options, see
Networking on page 273.
9. If you selected Typical as your configuration path, click Finish and the wizard sets up the files needed for your virtual machine.
If you selected Custom as your configuration path, continue with the steps for configuring a disk for your virtual machine.
www.vmware.com
65
Creating a New Virtual Machine
10. Select the disk type.
Select Create a new virtual disk.
Virtual disks are the best choice for most virtual machines. They are quick and easy to set up and can be moved to new locations on the same host computer or to different host computers. Virtual disks start as small files on the host computers hard drive, then expand as needed up to the size you specify in the next step.
To use an existing operating system on a physical hard disk (a “raw” disk), read
Configuring a Dual-Boot Computer for Use with a Virtual Machine on page 237.
To install your guest operating system directly on an existing IDE disk partition, read the reference note Installing an Operating System onto a Raw Partition from
a Virtual Machine on page 265.
Caution: Raw disk configurations are recommended only for expert users.
Caution: If you are using a Windows .NET Server, Windows XP or Windows 2000
host, see Do Not Use Windows 2000, Windows XP and Windows .NET Server
Dynamic Disks as Raw Disks on page 259.
To install the guest operating system on a raw IDE disk, select Existing IDE Disk Partition. To use a raw SCSI disk, add it to the virtual machine later with the Configuration Editor. Booting from a raw SCSI disk is not supported. For a discussion of some of the issues involved in using a raw SCSI disk, see
Configuring Dual- or Multiple-Boot SCSI Systems to Run with VMware Workstation for Linux on page 260.
66
www.vmware.com
Creating a New Virtual Machine
11. Specify the size of the virtual disk.
Enter the size of the virtual disk that you wish to create. Use the default of 4GB or change the setting. The maximum size is 128GB for an IDE virtual disk or 256GB for a SCSI virtual disk. When you specify the size of the virtual disk, that amount of disk space is not immediately occupied by the virtual disk files. The virtual disk files grow as needed when applications and files are added to it.
Note: If this setting is larger than the capacity of the host machine’s hard disk, a warning message appears. You can ignore this message for now, as you can move this virtual machine to a drive that can hold it at a later time.
12. Specify the location of the virtual disks files.
If a SCSI virtual disk is created by default and you want to use a virtual IDE disk instead, or if you want to specify which device node should be used by your SCSI or IDE virtual disk, click Advanced.
Make the Virtual Disk Big Enough
The virtual disk should be large enough to hold the guest operating system and all of the software that you intend to install, with room for data and growth.
You cannot change the virtual disk’s maximum capacity later.
You can install additional virtual disks using the Configuration Editor
For example, you need about 500MB of actual free space on the file system containing the virtual disk to install Windows Me and popular applications such as Microsoft Office inside the virtual machine. You can set up a single virtual disk to hold these files. Or you can split them up installing the operating system on the first virtual disk and using a second virtual disk for applications or data files.
www.vmware.com
67
Creating a New Virtual Machine
13. Click Finish and the wizard sets up the files needed for your virtual machine.
68
www.vmware.com
Creating a New Virtual Machine
Setting up a New Virtual Machine
on a Linux Host
The Configuration Wizard guides you through the key steps for setting up a new virtual machine, helping you set various options and parameters. You can then use the Configuration Editor (Settings > Configuration Editor) if you need to make any changes to your virtual machines setup.
A new virtual machine is like a physical computer with a blank hard disk. Before you can use it, you need to format the virtual disk and install an operating system. The operating systems installation program may handle the formatting step for you.

Whats in a Virtual Machine on a Linux Host?

The virtual machine typically is stored on the host computer in a set of files, all of which are in a directory set aside for that particular virtual machine. In these examples, <vmname> is the name of your virtual machine. The key files are:
<vmname>.cfg the configuration file, which stores settings chosen in the Configuration Wizard or Configuration Editor.
nvram the file that stores the state of the virtual machines BIOS.
<vmname>.vmdk the virtual disk file, which stores the contents of the
virtual machines hard disk drive.
A virtual disk comprises one or more .vmdk files. The larger the size of the virtual disk, the more .vmdk files. As data is added to a virtual disk, the .vmdk files grow in size, to a maximum of 2GB each. If the virtual disk is 2GB or larger, VMware Workstation creates multiple .vmdk files.
If the virtual machine is connected directly to a physical disk, rather than using a virtual disk, there is no .vmdk file. Instead, a .raw file stores information about the partitions the virtual machine is allowed to access.
Note: Earlier VMware products used the extension .dsk for virtual disk files.
<vmname>.log or vmware.log the file that keeps a log of key VMware Workstation activity. This can be useful in troubleshooting if you encounter problems. This file is stored in the directory that holds the configuration (.cfg) file of the virtual machine.
<vmname>.vmdk.REDO the redo-log file, created automatically when a virtual machine is used in undoable or nonpersistent mode. This file stores changes made to the virtual disk while the virtual machine is running.
www.vmware.com
69
Creating a New Virtual Machine
<vmname>.vmss the suspended state file, which stores the state of a suspended virtual machine.
Note: Earlier VMware products used the extension .std for suspended state files.
There may be other files as well, some of which are present only while a virtual machine is running.
By default, the new virtual machine uses an IDE disk in persistent mode for Windows 95, Windows 98, Windows Me, Windows XP, Windows .NET Server and FreeBSD guests. The default for other guest operating systems is a SCSI disk in persistent mode.
Before you begin configuring your virtual machine, check the following notes and make any necessary adjustments to the configuration of your host operating system.
The real time clock function must be compiled into your Linux kernel
VMware Workstation for Linux requires that the parallel port PC-style hardware
option (CONFIG_PARPORT_PC) be built and loaded as a kernel module (that is, it must be set to m when the kernel is compiled).

Simple Steps to a New Virtual Machine on a Linux Host

Follow these steps to create a virtual machine using a virtual disk.
1. In a terminal window, launch VMware Workstation.
vmware &
2. If this is the first time you have launched VMware Workstation, you are prompted to enter your 20-character serial number. This number is on the registration card in your package. Enter your serial number and click OK.
The serial number is saved in your license file and VMware Workstation does not ask you for it again. For your convenience, VMware Workstation automatically sends the serial number to the VMware Web site when you use certain Web links built into the product (for example, Help > VMware software on the Web > Register Now! and Help > VMware software on the Web > Request Support). This allows us to direct you to the correct Web page for registration and support for your product.
3. If this is the first time you have launched VMware Workstation, a dialog box asks if you want to rename existing virtual disks using the new .vmdk extension. Click OK to search all local drives on the host computer and make this change.
The converter also renames the files that store the state of a suspended virtual machine, if it finds them. It changes the old .std file extension to .vmss.
70
www.vmware.com
Creating a New Virtual Machine
However, it is best to resume and shut down all suspended virtual machines before you upgrade to Workstation 3.2.
Besides renaming files, the converter updates the corresponding virtual machine configuration files so they identify the virtual disks using the new filenames.
Note: If you store your virtual disk files or suspended state files on a Windows XP or Windows .NET Server host or if you may do so in the future it is important to convert the filenames to avoid conflicts with the System Restore feature of Windows XP and Windows .NET Server.
4. Start the Configuration Wizard.
When you start VMware Workstation, the startup screen has three options:
Run the Configuration Wizard.
Run the Configuration Editor.
Open an existing configuration.
It also allows you to select a recently used configuration from a list.
The default selection is Run the Configuration Wizard.
One Chance to Rename Disk Files
The Rename Virtual Disks dialog box appears only once. If you click Cancel, you will not have another opportunity to update the filenames and configuration files automatically.
5. To start the Configuration Wizard, click OK. You can also start the Configuration Wizard from the File menu (select File > Wizard).
The Configuration Wizard presents you with a series of screens that you navigate using the Next and Prev buttons at the bottom of each screen. At each screen, follow the instructions, then click Next to proceed to the next screen.
www.vmware.com
71
Creating a New Virtual Machine
6. Select the method you want to use for configuring your virtual machine.
If you select Create standard virtual machine, the wizard prompts you to specify or accept defaults for
The name of the guest operating system
The path to the directory for the guest operating system and a display name
for the virtual machine
The disk type setting
Whether to install a new virtual disk, use an existing virtual disk or use a
physical disk drive
The size of the virtual disk
Select Install VMware Guest OS Kit if you have a Guest OS Kit and want to use it to create a preconfigured virtual machine using a virtual disk. If you select Install VMware Guest OS Kit, the wizard asks you to specify the path to the installer file on the Guest OS Kit CD-ROM. When you click Finish, it launches the Guest OS Kit installation program. For more information on VMware Guest OS Kits, see
www.vmware.com/products/guestoskits/.
The Finish button is not available initially. When there is enough information for the Configuration Wizard to finish the configuration, this button becomes available. Click Finish to have the Configuration Wizard enter default values for the remaining options. This is the fastest way to configure your virtual machine.
72
www.vmware.com
Creating a New Virtual Machine
7. Select a guest operating system.
This screen asks which operating system to install in the virtual machine. The Configuration Wizard uses this information to select appropriate default values, such as the amount of disk space needed. The wizard also uses this information when naming associated virtual machine files.
If the operating system you are using is not listed, select Other and enter the name of the operating system.
The remaining steps assume you plan to install a Windows Me guest operating system. You can find detailed installation notes for this and other guest operating systems in Installing Guest Operating Systems on page 135.
www.vmware.com
73
Creating a New Virtual Machine
8. Select a directory and display name for the virtual machine.
Each virtual machine should have its own directory. All associated files, such as the configuration file and the disk file, are placed in this directory.
The default location is <homedir>/vmware/winME, where <homedir> is the home directory of the user who is currently logged on. If others users need to access this virtual machine, you should consider placing the virtual machine files in a location that is accessible to them. For more information, see Sharing
Virtual Machines with Other Users on page 134.
Enter a display name for the virtual machine or accept the default. In this case, the default is Windows Millennium.
74
www.vmware.com
Creating a New Virtual Machine
9. Select the disk type.
Select Create a new virtual disk.
Virtual disks are the best choice for most virtual machines. They are quick and easy to set up and can be moved to new locations on the same host computer or to different host computers. Virtual disks start as small files on the host computers hard drive, then expand as needed up to the size you specify in the next step.
To use an existing virtual disk with this virtual machine, select Use an existing virtual disk.
To use an existing operating system on a physical hard disk (a raw disk), read
Configuring a Dual-Boot Computer for Use with a Virtual Machine on page 237.
To install your guest operating system directly on an existing IDE disk partition, read the reference note Installing an Operating System onto a Raw Partition from
a Virtual Machine on page 265.
Caution: Raw disk configurations are recommended only for expert users.
To install the guest operating system on a raw IDE disk, select Use a physical disk. To use a raw SCSI disk, add it to the virtual machine later with the Configuration Editor. Booting from a raw SCSI disk is not supported. For a discussion of some of the issues involved in using a raw SCSI disk, see
Configuring Dual- or Multiple-Boot SCSI Systems to Run with VMware Workstation for Linux on page 260.
www.vmware.com
75
Make the Virtual Disk Big Enough
The virtual disk should be large enough to hold the guest operating system and all of the software that you intend to install, with room for data and growth.
You cannot change the virtual disk’s maximum capacity later.
You can install additional virtual disks using the Configuration Editor
For example, you need about 500MB of actual free space on the file system containing the virtual disk to install Windows Me and popular applications such as Microsoft Office inside the virtual machine. You can set up a single virtual disk to hold these files. Or you can split them up installing the operating system on the first virtual disk and using a second virtual disk for applications or data files.
Creating a New Virtual Machine
10. Select the size of the virtual disk.
Enter the size of the virtual disk that you wish to create. Use the default of 4000 (megabytes, or 4GB) or change the setting. The maximum size is 128GB for an IDE virtual disk or 256GB for a SCSI virtual disk. When you specify the size of the virtual disk, that amount of disk space is not immediately occupied by the virtual disk file. The virtual disk file grows as needed when applications and files are added to it.
Note: If this setting is larger than the capacity of the host machine's hard disk, a warning message appears. You can ignore this message for now, as you can move this virtual machine to a drive that can hold it at a later time.
76
www.vmware.com
Creating a New Virtual Machine
11. Enable the CD-ROM drive.
Most operating systems require the use of a CD-ROM for installation.
Select CD-ROM enabled. To enter the path to the CD-ROM drive, Click Browse or type the path to the CD-ROM drive. For example, /dev/cdrom.
If you wish, you can disable access to the CD-ROM drive later from the Devices menu when your virtual machine is running.
www.vmware.com
77
Creating a New Virtual Machine
12. Enable the floppy disk drive.
Select the Floppy enabled option. To enter the path to the floppy drive, click Browse or type the path to the physical floppy drive (for example, type /dev/fd0).
Some operating systems may require the use of a floppy drive during installation.
If you wish, you can disable access to the floppy drive later using the Configuration Editor (Settings > Configuration Editor) or from the Devices menu when your virtual machine is running.
78
www.vmware.com
Creating a New Virtual Machine
13. Configure the networking capabilities of the virtual machine.
To enable your virtual machine to use an existing Ethernet connection on your host computer, select Bridged networking.
To enable your virtual machine to use a virtual network limited to the host and the virtual machines running on the host, select Host-only networking.
To enable your virtual machine to use both an existing Ethernet connection on your host computer and also a virtual network limited to the host and the virtual machines running on the host, select Bridged and host-only networking. This allows for the sharing of files between the virtual machine and the host operating system.
To give the virtual machine access to the host computers dial-up or external network connection using the hosts IP address, select NAT. NAT is useful if you have a wireless NIC on your host (as bridged networking is not supported on wireless NICs) and allows for the sharing of files between the virtual machine and the host operating system.
For more details about VMware Workstation networking options, see
Networking on page 273.
www.vmware.com
79
Creating a New Virtual Machine
14. Review and finish the configuration.
This screen presents all the options you selected. Review it for accuracy and click Done to complete the virtual machine configuration.
80
www.vmware.com
Creating a New Virtual Machine
Installing a Guest Operating System
and VMware Tools
Installing a guest operating system inside your VMware Workstation virtual machine is essentially the same as installing it on a physical computer. The basic steps for a typical operating system are:
1. Start VMware Workstation.
2. Insert the installation CD-ROM or floppy disk for your guest operating system.
3. Power on your virtual machine click the Power On button.
4. Follow the instructions provided by the operating system vendor.
The next section provides notes on installing a Windows Me guest operating system. The screen shots illustrate the process on a Windows host. The steps are the same on a Linux host.
For information on installing other guest operating systems, see Installing Guest
Operating Systems on page 135.
www.vmware.com
81
Creating a New Virtual Machine
Installing Windows Me as a Guest
Operating System
You can install Windows Me in a virtual machine using the standard Windows Me CD.
Note: Some Microsoft Windows Me OEM disks included with new computers are customized for those computers and include device drivers and other utilities specific to the system hardware. Even if you can install this Windows Me operating system on your physical computer, you may not be able to install it in a VMware Workstation virtual machine. You may need to purchase a new copy of Windows to install in a virtual machine.
Before installing the operating system, be sure that you have already created a new virtual machine and configured it using the New Virtual Machine Wizard (on Windows hosts) or Configuration Wizard (on Linux hosts).
Installation Steps
1. Use the VMware Workstation Configuration Editor to verify the virtual machine’s devices are set up as you expect before starting the installation. For example, if you would like the Windows Me Setup program to install networking services, be sure that a virtual Ethernet adapter is installed in the virtual machine’s configuration. VMware also recommends that you disable the screen saver on the host system before starting the installation process.
2. Insert the Windows Me CD in the CD-ROM drive.
3. Power on the virtual machine to start installing Windows Me.
4. Choose to boot from CD-ROM, then select Start Windows Me Setup from CD- ROM. The setup program runs FDISK and reboots.
82
www.vmware.com
Creating a New Virtual Machine
5. Once again, choose to boot from CD-ROM, then select Start Windows Me Setup from CD-ROM. The setup program continues installing Windows Me.
6. Follow the Windows Me installation steps as you would for a physical computer.
www.vmware.com
83
Don’t Forget VMware Tools
It is very important that you install VMware Tools in the guest operating system. If you do not install VMware Tools, the graphics environment within the virtual machine is limited to VGA mode graphics (640x480, 16 color).
With the VMware Tools SVGA driver installed, Workstation supports up to 32-bit displays and high display resolution, with significantly faster overall graphics performance.
Other tools in the package support time synchronization between host and guest, automatic grab and release of the mouse cursor, copying and pasting between guest and host, and improved mouse performance in some guest operating systems.
Creating a New Virtual Machine

Installing VMware Tools

The installers for VMware Tools for Windows, Linux and FreeBSD guest operating systems are built into VMware Workstation as ISO image files. (An ISO image file looks like a CD-ROM to your guest operating system and even appears as a CD-ROM in Windows Explorer. You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file.)
VMware Tools for Windows supports Windows 95, Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP and Windows .NET Server guest operating systems.
Note: VMware Tools is not included in NetWare 6 virtual machines. For more information, see www.vmware.com/download/netware_tools.html.
When you choose Settings > VMware Tools Install from the VMware Workstation menu bar, VMware Workstation temporarily connects the virtual machines first virtual CD-ROM drive to the ISO image file that contains the VMware Tools installer for your guest operating system and begins the installation process. (If you decide not to proceed with the installation, choose Settings > Cancel VMware Tools Install to return your virtual machines CD-ROM drive to its original configuration.)

VMware Tools for Windows Guests

The details of how you install VMware Tools depend on the version of Windows you are running. The steps that follow show how to install VMware Tools in a Windows Me guest. Some steps that are automated in newer versions of Windows must be performed manually in Windows 9x and Windows NT.
Note: If you are running VMware Workstation for Windows, and your virtual machine has only one CD-ROM drive, the CD-ROM drive must be configured as an IDE or SCSI CD-ROM drive. It cannot be configured as a generic SCSI device.
To add an IDE or SCSI CD-ROM drive, see Adding, Configuring and Removing Devices
in a Virtual Machine on page 115. For information about generic SCSI, see Connecting to a Generic SCSI Device on page 379.
Installing VMware Tools in a Windows Guest Operating System
1. Power on the virtual machine.
2. When the guest operating system starts, prepare your virtual machine to install VMware Tools.
Choose Settings > VMware Tools Install.
84
www.vmware.com
Creating a New Virtual Machine
The remaining steps take place inside the virtual machine.
3. If you have auto-run enabled in your guest operating system (the default setting for Windows operating systems), a dialog box appears after a few seconds. It asks if you want to install VMware Tools. Click Yes to launch the InstallShield wizard.
If autorun is not enabled, the dialog box does not appear automatically. If it doesnt appear, run the VMware Tools installer. Click Start > Run and enter D:\setup\setup.exe where D: is your first virtual CD-ROM drive.
Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system and even appears as a CD-ROM in Windows Explorer. This image contains all the files needed to install VMware Tools in your guest operating system. When you finish installing VMware Tools, this image file no longer appears in your CD-ROM drive.
4. Follow the on-screen instructions.
5. On Windows .NET Server , Windows Me, Windows 98 SE and Windows 98 guests, the SVGA driver is installed automatically and the guest operating system uses it after it reboots. With Windows 2000 and Windows XP guests, you do not have to reboot before you can use the new driver.
Additional Steps for Some Versions of Windows When Migrating from Old Disk Versions
If you are migrating a VMware Workstation 2.0 disk to VMware Workstation 3.2 and your guest operating system is Windows NT, Windows Me, Windows 98 or Windows
www.vmware.com
85
Creating a New Virtual Machine
95, you need to configure the video driver by hand. Instructions open automatically in Notepad at the end of the installation process. If the Notepad window is hidden, bring it to the front by clicking the Notepad button on the Windows taskbar.
For details, see the steps that correspond to your guest operating system.
Windows NT
1. After installing VMware Tools, click Finish. The Display Properties dialog box appears.
2. Click the Display Type button. The Display Type dialog box appears.
3. Click the Change button. The Change Display dialog box appears.
4. Select VMware, Inc. from the Manufacturer list.
5. Select VMware SVGA as the display adapter and click OK.
6. Click Yes in response to the on-screen question about third-party drivers to install the driver, then click OK to confirm the drivers were installed.
7. Click Close from the Display Type dialog box, then click Close from the Display Properties dialog box.
8. Click Yes to restart Windows NT and start using the new video driver.
9. The VMware Tools background application is launched automatically when you reboot your virtual machine.
86
Windows Me
1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
2. Click the Advanced button.
3. Click the Adapter tab.
4. Click the Change button. This starts the Update Device Driver Wizard.
5. The Wizard now presents two options. Choose the second option to Specify the location of the driver.
Click Next.
6. Check the Specify a location checkbox. Enter the following path:
D:\video\win9x
D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.
Click OK.
7. Windows Me automatically locates your driver.
www.vmware.com
Creating a New Virtual Machine
8. Select the VMware SVGA II display adapter and click Next.
9. Click Next to install the driver.
If you are upgrading a virtual machine created under VMware Workstation 2.0, you may see a dialog box that warns, The driver you are installing is not specifically designed for the hardware you have. Do you wish to continue? Click Yes.
After the driver is installed, click Fini sh.
10. Click Yes to restart Windows Me and start using the new video driver.
11. The VMware Tools background application starts automatically when you reboot your virtual machine.
Windows 98
1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
2. Click the Advanced button. The Standard Display Adapter (VGA) Properties dialog box appears. If you are upgrading from a previous version of the VMware drivers, this dialog box is titled VMware SVGA Properties.
3. Click the Adapter tab.
4. Click the Change button. This starts the Update Device Driver Wizard. Click Next.
5. The Wizard presents two options. Choose the option to Display a list of all drivers in a specific location…. Click Next.
6. Select Have Disk. The Install From Disk dialog box appears.
7. Enter the following path:
D:\video\win9x
D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.
Click OK.
8. Select VMware SVGA display adapter and click OK.
9. Answer Yes to the on-screen question, then click Next to install the driver. After the driver is installed, click Finish.
10. Click Close in the SVGA Properties dialog box, then click Close in the Display Settings dialog box.
11. Click Yes to restart Windows 98 and start using the new video driver.
www.vmware.com
87
Creating a New Virtual Machine
12. The VMware Tools background application starts automatically when you reboot your virtual machine.
Windows 95
1. After installing VMware Tools, click Finish. The Display Settings dialog box appears.
2. Click the Advanced Properties button. The Advanced Display Properties dialog box appears.
3. Click the Change button. This brings up the Select Device dialog box.
4. Select Have Disk.
5. Enter the following path:
D:\video\win9x
D: is the drive letter for the first virtual CD-ROM drive in your virtual machine.
Click OK.
6. Click OK again to install the driver.
7. Click Close from the Advanced Display Properties dialog box, then click Close from the Display Setting dialog box.
8. Click Yes to restart Windows 95 and start using the new video driver.
9. The VMware Tools background application starts automatically when you reboot your virtual machine.
88

VMware Tools for Linux Guests

1. Power on the virtual machine.
2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.
Choose Settings > VMware Tools Install.
The remaining steps take place inside the virtual machine.
3. As root, open a terminal, mount the VMware Tools virtual CD-ROM image, copy its contents to /tmp, then unmount it.
Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system. This image contains all the files needed to install VMware Tools in your guest operating system.
www.vmware.com
Creating a New Virtual Machine
Note: Some Linux distributions use different device names or organize the
/dev directory differently. If your CD-ROM drive is not /dev/cdrom, modify the following commands to reflect the conventions used by your distribution.
mount -t iso9660 /dev/cdrom /mnt cp /mnt/vmware-linux-tools.tar.gz /tmp umount /dev/cdrom
4. Untar the VMware Tools tar file in /tmp, and install it.
cd /tmp tar zxf vmware-linux-tools.tar.gz cd vmware-linux-tools ./install.pl
5. Start X and your graphical environment if they are not started yet.
6. In an X terminal, launch the VMware Tools background application.
vmware-toolbox &
You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su).
Starting VMware Tools Automatically
You may find it helpful to configure your guest operating system so VMware Tools starts when you start your X server. The steps for doing so vary depending on your Linux distribution and the desktop environment you are running. Check your operating system documentation for the appropriate steps to take.
For example, in a Red Hat Linux 7.1 guest using GNOME, follow these steps.
1. Open the Startup Programs panel in the GNOME Control Center.
Main Menu (the foot icon in the lower left corner of the screen) > Programs > Settings > Session > Startup Programs
2. Click Add….
3. In the Startup Command field, enter vmware-toolbox.
4. Click OK, click OK again, then close the GNOME Control Center.
The next time you start X, VMware Tools starts automatically.

VMware Tools for FreeBSD Guests

1. Power on the virtual machine.
2. Prepare your virtual machine to install VMware Tools.
Choose Settings > VMware Tools Install.
www.vmware.com
89
Creating a New Virtual Machine
The remaining steps take place inside the virtual machine, not on the host computer.
3. As root, open a terminal, mount the VMware Tools virtual CD-ROM image, copy its contents to /tmp, then unmount it.
Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The VMware Workstation software contains an ISO image that looks like a CD-ROM to your guest operating system. This image contains all the files needed to install VMware Tools in your guest operating system.
mount /cdrom cp /cdrom/vmware-freebsd-tools.tar.gz /tmp umount /cdrom
4. Untar the VMware Tools tar file in /tmp, and install it.
cd /tmp tar zxf vmware-freebsd-tools.tar.gz cd vmware-freebsd-tools ./install.pl
5. Start X and your graphical environment if they are not started yet.
6. In an X terminal, launch the VMware Tools background application.
vmware-toolbox &
You may run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su).
Note: In a FreeBSD 4.5 guest operating system, sometimes VMware Tools does not start after you install VMware Tools, reboot the guest operating system or start VMware Tools on the command line in the guest. An error message appears:
Shared object libc.so.3 not found.
The required library was not installed. This does not happen with full installations of FreeBSD 4.5, but does occur for minimal installations. To fix the problem of the missing library, complete the following steps:
1. Insert and mount the FreeBSD 4.5 installation CD or access the ISO image file.
2. Change directories and run the install script.
cd /cdrom/compat3x ./install.sh
90
www.vmware.com
Creating a New Virtual Machine

Installing VMware Tools in a NetWare Virtual Machine

1. Power on the virtual machine.
2. Prepare your virtual machine to install VMware Tools.
Choose Settings > VMware Tools Install.
The remaining steps take place inside the virtual machine.
3. Load the CD9660.NSS driver so the CD-ROM device mounts the ISO image as a volume. In the system console, type
LOAD CD9660.NSS
4. When the driver finishes loading you can begin installing VMware Tools. In the system console, type
vmwtools:\setup.ncf
5. Restart the guest operating system. In the system console, type
restart server
www.vmware.com
91
Creating a New Virtual Machine

VMware Tools Configuration Options

This section shows the options available in a Windows Me guest operating system. Similar configuration options are available in VMware Tools for other guest operating systems.
To open the VMware Tools control panel, double-click the VMware Tools icon in the system tray.
If the VMware Tools icon is not displayed in the system tray, go to Start > Settings > Control Panel.
92
The Devices tab allows you to enable or disable removable devices. (You can also set these options from the Devices menu of the VMware Workstation application window.)
The Shrink tab gives you access to the controls you need if you wish to reclaim unused space in a virtual disk.
www.vmware.com
Creating a New Virtual Machine
The Other tab shows the Miscellaneous Options.
Time synchronization between the virtual machine and the host operating system
Note: You can synchronize the time between the guest and host operating systems only when you set the clock in the guest operating system to a time earlier than the time set in the host.
Show VMware Tools in the taskbar
www.vmware.com
93
5

Running VMware Workstation

Running VMware Workstation
A Quick Guide to Running VMware
Workstation
After you have installed VMware Workstation, a guest operating system and VMware Tools, how do you run your virtual machine? The following sections give you highlights of the most common tasks.
Overview of the VMware Workstation Window on page 97
Starting a Virtual Machine on a Windows Host on page 98
Starting a Virtual Machine on a Linux Host on page 101
Checking the Status of VMware Tools on page 101
Using Full Screen Mode on page 102
Installing New Software Inside the Virtual Machine on page 102
Cutting, Copying and Pasting on page 103
Sharing Files Between Guest and Host Operating Systems on page 103
Deciding How Your Virtual Machine Stores Data on page 108
Suspending and Resuming Virtual Machines on page 109
Resuming Virtual Machines Repeatedly from the Same Point on page 111
Shutting Down a Virtual Machine on page 115
Adding, Configuring and Removing Devices in a Virtual Machine on page 115
Connecting and Disconnecting Removable Devices on page 116
Fitting the VMware Workstation Window to the Virtual Machine on page 117
Creating a Screen Shot of a Virtual Machine on page 117
Setting General Preferences for VMware Workstation on page 118
Command Reference on page 123
The quick reference card, included in your VMware Workstation package, provides similar information in an easy-to-use format.
For purposes of illustration, the examples in these sections use a Windows Me guest operating system. Some commands used in the illustrations will be different for other guest operating systems.
96
www.vmware.com
Running VMware Workstation

Overview of the VMware Workstation Window

Think of your VMware Workstation virtual machine as a separate computer that runs in a window on your physical computer's desktop.
Instead of using physical buttons to turn this computer on and off, you use buttons in the toolbar at the top of the VMware Workstation window.
Toolbar when virtual machine is powered off (Windows host)
Toolbar when virtual machine is powered off (Linux host)
Toolbar when virtual machine is powered on ( Windows host)
Toolbar when virtual machine is powered on (Linux host)
www.vmware.com
97
Running VMware Workstation
Toolbar when virtual machine is suspended ( Windows host)
Toolbar when virtual machine is suspended (Linux host)
On a Windows host, there are separate Power Off and Power On buttons. When you suspend a virtual machine, the Power On button becomes a Resume button. On a Linux host, the power button is labeled Power On or Power Off, depending on whether your virtual machine is running or not.
On a Windows host, an alert appears at the bottom left corner of the VMware Workstation window when your virtual machine is not running the version of VMware Tools that matches your version of VMware Workstation. You see a small icon and a note you can click to begin installing VMware Tools. This gives you a quick way to launch the VMware Tools installer. It is especially useful immediately after you install the guest operating system in a new virtual machine.
On a Linux host, a note in the bottom bar of the VMware Workstation window alerts you when your virtual machine is not running the version of VMware Tools that matches your version of VMware Workstation. To launch the VMware Tools installer, choose Settings > VMware Tools Install….
Note: Your guest operating system must be completely installed and running when you install VMware Tools.
For details, see Installing VMware Tools on page 84.
98

Starting a Virtual Machine on a Windows Host

1. Start VMware Workstation by double-clicking the shortcut on your desktop or launch the program from the Start menu (Start > Programs > VMware >
VMware Workstation).
www.vmware.com
Running VMware Workstation
The VMware Workstation window opens.
2. Select the name of the virtual machine you want to use in the virtual machine list at the left of the opening screen, then click Power On.
If the virtual machine you want to use is not shown there, click the Open Existing Virtual Machine icon and browse to the .vmx file for the virtual machine you want to use. That virtual machine will be added to the virtual machine list so you can open it easily the next time you want to use it.
Note: By default, VMware Workstation 3.2 stores virtual machines in the My Documents folder of the user who is logged on when the virtual machine is created. On Windows .NET Server, Windows XP and Windows 2000, the default folder is C:\Documents and Settings\<username>\My Documents\My Virtual Machines\<guestOSname>. On Windows NT, the default folder is
C:\WINNT\Profiles\<username>\Personal\My Virtual Machines\<guestOSname>. Earlier versions of VMware Workstation stored
virtual machines in C:\Program Files\VMware\VMs\<guestOSname> by default.
3. Click the Power On button to start the virtual machine.
4. Click anywhere inside the VMware Workstation window to give the virtual machine control of your mouse and keyboard.
5. If you need to log on, type in your name and password just as you would on a physical computer.
www.vmware.com
99
Running VMware Workstation
Removing a Name from the Virtual Machine Name List
You can remove the name of a virtual machine from the list in the VMware Workstation window at any time. Removing the name from the list does not affect the virtual machines files. You can add the virtual machine to the list again at any time by opening it, as described above.
To remove a name from the list, take these steps.
100
1. Right-click a name in the list once to select it.
2. After a brief pause, right-click the name again to pop up a context menu.
3. Choose Remove From List to remove the selected virtual machine’s name.
You may also choose Power On to power on the selected virtual machine or Settings… to modify settings for the selected virtual machine in the Configuration Editor.
www.vmware.com
Loading...