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
228 VMware, Inc.
These!configuration!lines!can!be!added!to!the!individual!virtual!machine!configuration,!
to!your!personal!VMware!Server!configuration!(~/.vmware/config),!or!even!to!the!
host‐wide!(/etc/vmware/config)!or!installation‐wide!(usually!
/usr/local/lib/vmware/config)!configuration.!
When!key!code!mapping!cannot!be!used!(or!is!disabled),!VMware!Server!maps!
keysyms!to!v‐
scan!codes.!It!does!this!using!one!of!the!tables!in!the!xkeymap!directory!in!
the!VMware!Server!installation!(usually!/usr/local/lib/vmware).
Which!table!you!should!use!depends!on!the!keyboard!layout.!The!normal!distribution!
includes!tables!for!PC!keyboards!for!the!United!States!and!a!number!of!European!
countries!and!languages.
!And!for!most!of!these,!there!are!both!the!101‐key!(or!102‐key)!
and!the!104‐key!(or!105‐key)!variants.!
VMware!Server!automatically!determines!which!table!to!use!by!examining!the!current!
X!keymap.!However,!its!decision‐making!process!can!sometimes!fail.!In!addition,!each!
mapping!is!fixed!
and!might!not!be!completely!right!for!any!given!keyboard!and!X!key!
code‐to‐keysym!mapping.!For!example,!a!user!might!have!swapped!Ctrl!and!Caps!
Lock!using!xmodmap.!This!means!the!keys!are!swapped!in!the!virtual!machine!when!
using!a!remote!server!(keysym!mapping)!but!unswapped!when!
using!a!local!server!
(key!code!mapping).!
Therefore,!keysym!mapping!is!necessarily!imperfect.!To!make!up!for!this!defect,!you!
can!change!most!of!the!behavior!using!configuration!settings:!
! xkeymap.language = <keyboard-type>
Use!this!if!VMware!Server!has!a!table!in!xkeymap!for!your!keyboard!but!can’t!detect!
it.!<keyboard-type>!must!be!one!of!the!tables!in!the!xkeymap!directory.!(See!above!
for!location.)!However,!the!failure!to!detect!the!keyboard!probably!means!the!table!
isn’t!completely!correct!for!you.!
! xkeymap.keysym.<sym> = <v-scan code>
If!you!use!keysym!mapping,!map!keysym!<sym>!to!<v-scan code>.!When!you!do,!
<sym>!must!be!an!X!keysym!name!and!<v-scan code>!should!be!a!C‐syntax!
hexadecimal!number!(for! example,!0x001).!
The!easiest!way!to!find!the!keysym!name!for!a!key!is!to!run!xev!or!xmodmap -pk.
!
The!X!header!file!/usr/X11R6/include/X11/keysymdef.h!has!a!complete!list!of!
keysyms.!(The!name!of!a!keysym!is!the!same!as!its!C!constant!without!the!XK_!
prefix.)!Most!v‐scan!codes!are!in!the!“V‐Scan!Code!Table”!on!page 229.
The!xkeymap!tables!themselves!are!also!helpful.!Use!them!to!fix
!small!errors!in!an!
existing!mapping.!
! xkeymap.fileName = <file-path>
Use!the!keysym!mapping!table!in!<file-path>.!A!table!is!a!sequence!of!