Specifications
Table Of Contents
- Virtual Machine Guide
- Contents
- Introduction and System Requirements
- VMware Server Overview
- Features of VMware Server
- Support for 32-bit and 64-bit Guest Operating Systems
- Two-Way Virtual SMP (Experimental Support)
- Connect to VMware GSX Virtual Machines and Hosts
- Upgrade and Use GSX Virtual Machines
- Move Existing Virtual Machines
- Compatible with VMware Workstation 5.x Virtual Machines
- Configure Virtual Hardware Devices to be Automatically Detected
- Take and Revert to Snapshots in the Background
- Support for VMware Virtual Machine Importer
- Support for VirtualCenter
- APIs Included with VMware Server
- Host System Requirements
- Virtual Machine Specifications
- Virtual Processor
- Virtual Chipset
- Virtual BIOS
- Virtual Memory
- Virtual Graphics
- Virtual IDE Drives
- Virtual SCSI Devices
- Virtual PCI Slots
- Virtual Floppy Drives
- Virtual Serial (COM) Ports
- Virtual Parallel (LPT) Ports
- Virtual USB ports
- Virtual Keyboard
- Virtual Mouse and Drawing Tablets
- Virtual Ethernet Card
- Virtual Networking
- Virtual Sound Adapter
- Supported Guest Operating Systems
- Technical Support Resources
- Creating a New Virtual Machine
- Using VMware Tools
- About VMware Tools
- Installing VMware Tools
- Installing VMware Tools in a Windows Virtual Machine
- To install VMware Tools in a Windows Guest Operating System
- Additional Steps When Migrating from Old Versions of Windows
- To migrate from Windows NT guest operating systems
- To migrate from Windows Me guest operating systems
- To migrate from Windows 98 guest operating systems
- To migrate from Windows 95 guest operating systems
- Automating the Installation of VMware Tools in a Windows Guest
- Installing VMware Tools in a Linux Virtual Machine
- Installing VMware Tools in a NetWare Virtual Machine
- Installing VMware Tools in a Windows Virtual Machine
- Executing Scripts When the Virtual Machine’s Power State Changes
- Configuring VMware Tools
- Configuring VMware Tools in a Windows Virtual Machine
- Configuring VMware Tools in a Linux, FreeBSD, or Solaris Virtual Machine
- Configuring VMware Tools in a NetWare Virtual Machine
- Configuring VMware Tools in a NetWare 6.5, 6.0, or NetWare 5.1 Guest
- Viewing Information About VMware Tools
- Connecting Devices with VMware Tools
- Shrinking Virtual Disks with VMware Tools
- Setting Options with VMware Tools
- Configuring VMware Tools for NetWare Guests in the System Console
- Summary of VMware Tools Commands for a NetWare Guest
- About the VMware Tools Service
- Running Virtual Machines
- Overview of the VMware Server Console Window
- Connecting to Virtual Machines and VMware Server Hosts
- Changing the Power State of a Virtual Machine
- Controlling the Virtual Machine Display
- Running Virtual Machines from DVDs or CD-ROM Discs
- Using PXE with Virtual Machines
- Installing Software in a Virtual Machine
- Cutting, Copying, and Pasting Text
- Using Devices in a Virtual Machine
- Command Reference
- Preserving the State of a Virtual Machine
- Suspending and Resuming Virtual Machines
- Taking Snapshots
- Using Disks in a Virtual Machine
- Configuring Hard Disk Storage in a Virtual Machine
- Configuring Optical and Floppy Drives
- Adding Drives to a Virtual Machine
- Using VMware Virtual Disk Manager
- Installing an Operating System onto a Physical Partition
- Disk Performance in Windows NT Guests on Multiprocessor Hosts
- Networking
- Components of the Virtual Network
- Common Networking Configurations
- Custom Networking Configurations
- Changing the Networking Configuration
- Advanced Networking Topics
- Selecting IP Addresses on a Host-Only Network or NAT Configuration
- Avoiding IP Packet Leakage in a Host-Only Network
- Maintaining and Changing the MAC Address of a Virtual Machine
- Controlling Routing for a Host-Only Network on a Linux Host
- Issues with Host-Only Networking on a Linux Host
- Setting Up a Second Bridged Network Interface on a Linux Host
- Configuring Bridged Networking When Using Teamed Network Interface Cards
- Setting Up Two Separate Host-Only Networks
- To set up the second host-only interface on a Windows host
- To set up the second host-only interface on a Linux host
- Configuring the Virtual Machines
- Configuration 1 - Connect to the Default Host-Only Interface
- Configuration 2 - Connect to the Newly Created Host-Only Interface
- Configuration 3 - Connect to Two Host-Only Interfaces
- Routing Between Two Host-Only Networks
- Setting Up the First Host-Only Interface
- To set up the second host-only interface on a Windows host
- To set up the second host-only interface on a Linux host
- Setting Up the Virtual Machines
- Virtual Machine 1 - Connected to the Default Host-Only Interface
- Virtual Machine 2 - Connected to the Newly Created Host-Only Interface
- Virtual Machine 3 - Connected to Both Host-Only Interfaces
- Using Virtual Ethernet Adapters in Promiscuous Mode on a Linux Host
- Understanding NAT
- Using Samba for File Sharing on a Linux Host
- Sample smb.conf for Host-Only Networking
- Sample smb.conf for Bridged Networking
- Adding User Names and Passwords to the VMware Server Samba Password File
- If You Are Already Running Samba
- Using a Samba Server for Both Bridged and Host-Only Networks
- Using VMware Server’s Samba with an Existing Installation
- Sample smb.conf for Running Two Samba Servers at the Same Time
- Configuring Devices
- Using Parallel Ports
- Using Serial Ports
- Keyboard Mapping on a Linux Host
- Using USB Devices in a Virtual Machine
- Connecting to a Generic SCSI Device
- Using Two-Way Virtual Symmetric Multiprocessing (Experimental)
- Video and Sound
- Performance Tuning for Virtual Machines
- Glossary
- Index
VMware, Inc. 123
Chapter 6 Using Disks in a Virtual Machine
If!you!are!setting!up!a!new!virtual!machine,!follow!the !custom!path!in!the!New!Virtual!
Machine!Wizard.!In!the!screen!that!lets!you!specify!the!virtual!disk’s!capacity,!select!
Split!disk!into!2GB!files.
If!you!are!adding!a!virtual!disk!to!an!existing!virtual!machine,!follow!the!steps
!in!the!
Add!Hardware!Wizard.!In!the!screen!that!lets!you!specify!the!virtual!disk’s!capacity,!
select!Split!disk!into!2GB!files.
When!a!disk!is!split!into!multiple!files,!larger!virtual!disks!have!more!.vmdk!files.!
The!first!.vmdk!file!for!each!disk!is!small!and!contains!pointers!to!
the!other!files!that!
make!up!the!virtual!disk.!The!other!.vmdk!files!contain!data!stored!by!your!virtual!
machine!and!use!a!small!amount!of!space!for!virtual!machine!overhead.
By!default,!all!disk!space!is!allocated!when!you!create!the!virtual!disk.!A!preallocated!
virtual!disk!has!fixed!file!
sizes,!and!most!of!the!files!are!2GB.!As!mentioned!above,!the!
first!file!is!small.!The!last!file!in!the!series!might!also!be!smaller!than!2GB.
If!you!chose!not!to!allocate!the!space!in!advance,!the!.vmdk!files!grow!as!data!is!added,!
to!a!maximum!of!2GB!
each!—!except!for!the!first!file!in!the!set,!which!remains!small.
The!virtual!machine!settings!editor!shows!the!name!of!the!first!file!in!the!set!—!the!one!
that!contains!pointers!to!the!other!files!in!the!set.!The!other!files!used!for!that!disk!are!
assigned!names!
based!on!the!name!of!the!first!file.!
For!example,!a!Windows!2000!Server!virtual!machine!using!the!default!configuration,!
with!files!that!grow!as!needed,!stores!the!disk!in!files!named!Windows 2000
Server.vmdk,!Windows 2000 Server-s001.vmdk,!Windows 2000 Server-s002.vmdk!and!so!
on.
If!the!disk!space!is!allocated!in!advance!and!the!virtual!disk
!is!split!into!2GB!files,!the!
names!are!similar,!except!that!they!include!an!f!instead!of!an!s!—!for!example,!Windows
2000 Server-f001.vmdk.!If!the!disk!is!not!split!into!2GB!files,!the!virtual!machine!stores!
the!disk!in!two!files,!named!Windows 2000 Server.vmdk!and!Windows 2000
Server-flat.vmdk.
If!you!are!using
!a!physical!disk,!the!.vmdk!file!stores!information!about!the!physical!disk!
or!partition!used!by!the!virtual!machine.
Redo-Log Files
Redo‐log!files!are!stored!in!the!virtual!machine’s!working!directory,!and!are!for!saving!
changes!to!independent‐nonpersistent!disks.!Redo‐log!files!save!blocks!that !the!virtual!
machine!modifies!while!it!is!running.!The!redo‐log!file!for!a!disk!in!
independent‐nonpersistent!mode!is!not!saved!when!the!
virtual!machine!is!powered!off!
or!reset.!