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 Server Virtual Machine Guide
26 VMware, Inc.
! <vmname>.vmdk.REDO_xxxxxx!—!A!redo‐log!file!created!automatically!when!a!
virtual!machine!is!in!independent‐nonpersistent!mode.!This!file!stores!changes!
made!to!a!virtual!disk!while!the!virtual!machine!is!running.!More!than!one!such!
file!might!exist.!The!xxxxxx!indicates!a!unique!suffix!added!automatically!by!
VMware!Server!to
!avoid!duplicate!filenames.
! <vmname>.vmss!—!The!suspended!state!file,!which!stores!the!state!of!a!suspended!
virtual!machine.
NOTE Some!earlier!VMware!products!used!the!extension!.std!for!suspended!
state!files.
! <vmname>.vmsn!—!The!snapshot!state!file,!which!stores!the!running!state!of!a!virtual!
machine!at!the!time!you!take!a!snapshot!of!it.
There!might!also!be!other!files,!some!of!which!are!present!only!while!a!virtual!machine!
is!running.
Virtual Disks
A!virtual!disk!is!made!up!of!one!or!more!.vmdk!files.!If!you!specify!to!split!the!virtual!
disk!into!2GB!files,!the!number!of!.vmdk!files!depends!on!the!size!of!the!virtual!disk.
By!default,!all!virtual!disk!space!is!preallocated!when!you!create!the!virtual!disk.!Make!
sure!you!have!enough!disk!space!on!the!host!before!you!create!a!preallocated!disk.
If!you!do!not!allocate!all!disk!space!when!you!create!the!virtual!disk,!the!.vmdk!files!
grow!in!size!as!data!is!added!to!the!virtual!disk.!Almost!all!of!a!.vmdk!file’s!content!is!
the!virtual!machine’s!data,!with!a!small!portion!allotted!to!virtual!machine!overhead.!
If!the!virtual!machine!is!connected!directly!to!a!physical!disk,!rather!than!to!a!virtual!
disk,!the!.vmdk!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.
Permissions and Running Virtual Machines
When!you!create!a!virtual!machine,!by!default!the!virtual!machine!is!private,!which!
means!you!are!the!only!user!who!can!access!it.!If!you!choose!the!custom!path!when!
creating!the!virtual!machine,!you!can!specify!that!all!users!can!access!the!virtual!
machine.
When!a!virtual!machine!is!
private,!it!appears!only!in!the!inventory!of!the!console!of!the!
user!who!created!it.!The!virtual!machine!does!not!appear!in!the!inventory!of!consoles!