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
172 VMware, Inc.
! “Routing!Between!Two!Host‐Only!Networks”!on!page 185
! “Using!Virtual!Ethernet!Adapters!in!Promiscuous!Mode!on!a!Linux!Host”
Selecting IP Addresses on a Host-Only Network or NAT
Configuration
A!host‐only!network!uses!a!private!virtual!network.!The!host!and!all!virtual!machines!
configured!for!host‐only!networking!are!connected!to!the!network!through!a!virtual!
switch.!Typically!all!the!parties!on!this!private!network!use!the!TCP/IP!protocol!suite,!
although!other!communication!protocols!can!be!used.!
A!network
!address!translation!(NAT)!configuration!also!sets!up!a!private!network,!
which!must!be!a!TCP/IP!network.!The!virtual!machines!configured!for!NAT!are!
connected!to!that!network!through!a!virtual!switch.!The!host!computer!is!also!
connected!to!the!private!network!used!for!NAT!through!a!host!virtual!adapter.
Each!virtual
!machine!and!the!host!must!be!assigned!addresses!on!the!private!network.!
This!is!typically!done!using!the!DHCP!server!that!comes!with!VMware!Server.!Note!
that!this!server!does!not!service!virtual!(or!physical)!machines!residing!on!bridged!
networks.!
Addresses!can!also!be!assigned!statically!from!a!pool!of!
addresses!that!are!not!assigned!
by!the!DHCP!server.
If!host‐only!networking!is!enabled!when!VMware!Server!is!installed,!the!network!
number!to!use!for!the!virtual!network!is!automatically!selected!as!an!unused!private!IP!
network!number.!To!find!out!which!network!is!used!on!a!Windows!host,!choose!
Host!
>!Virtual!Network!Settings!and!check!the!subnet!number!associated!with!the!virtual!
network.!On!a!Linux!host,!run!ifconfig!in!a!terminal.
A!NAT!configuration!also!uses!an!unused!private!network!automatically!selected!
when!you!install!VMware!Server.!To!find!out!which!network!is!used!on!a!Windows!
host,!
choose!Host!>!Virtual!Network!Settings!and!check!the!subnet!number!associated!
with!the!virtual!network.!On!a!Linux!host,!run!ifconfig!in!a!terminal.
Using!DHCP!to!assign!IP!addresses!is!simpler!than!statically!assigning!them.!Most!
Windows!operating!systems,!for!example,!come!preconfigured!to!use!DHCP!at!boot!
time,!
so!Windows!virtual!machines!can!connect!to!the!network!the!first!time!they!are!
booted,!without!additional!configuration.!If!you!want!your!virtual!machines!to!
communicate!with!each!other!using!names!instead!of!IP!addresses,!however,!you!must!
set!up!a!naming!convention,!a!name!server!on!the!private!network,!or
!both.!In!that!case!
it!might!be!simpler!to!use!static!IP!addresses.
In!general,!if!you!have!virtual!machines!you!intend!to!use!frequently!or!for!extended!
periods!of!time,!it!is!probably!most!convenient!to!assign!them!static!IP!addresses!or!to!