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
182 VMware, Inc.
4Click!OK!to!close!the!property!sheet.
5Right‐click!the!NIC!device,!and!choose!Properties!to!unbind!the!VMware!Bridge!
Protocol!from!each!physical!NIC!that!is!being!used!for!bridged!networking.!
6Clear!the!VMware!Bridge!Protocol!check!box.
7Click!OK!to!close!the!property!sheet.
Alternately,!you!can!use!the!Virtual!
Network!Editor!to!either!map!the!teamed!NIC!to!
VMnet0!or!exclude!the!physical!adapters!from!any!automatic!bridging!by!VMware!
Server.!For!information,!see!“Configuring!Bridged!Networking!Options!on!a!Windows!
Host”!on!page 164.
Changing the Teamed Networking Mode
If!you!change!the!teamed!networking!mode,!you!must!delete!the!original!NIC!team!on!
the!host!and!create!a!new!team.!Do!not!modify!a!virtual!machine’s!NIC!teaming!
settings.!
CAUTION Before!you!delete!the!original!team,!power!off!or!suspend!all!virtual!
machines!on!the!host!to!prevent!the!teaming!software!from!locking!up.
Setting Up Two Separate Host-Only Networks
For!some!configurations,!you!might!need!to!set!up!more!than!one!host‐only!network!on!
the!same!host!computer.!
You!might,!for!example,!want!to!have!two!virtual!machines!connected!to!one!host‐only!
network,!and!at!the!same!time!have!other!virtual!machines!connected!to!another!
host‐only!network.
!This!setup!isolates!network!traffic!on!each!network.
Or!you!might!want!to!test!routing!between!two!virtual!networks.!Or!test!a!virtual!
machine!with!multiple!network!interface!cards!—!without!using!any!physical!Ethernet!
adapters.!
On!Windows!hosts,!the!first!host‐only!network!is!set!up!automatically!when!you!install
!
VMware!Server.!
On!Linux!hosts,!the!first!host‐only!network!is!set!up!when!you!run!the!
vmware-config.pl!program!after!you!install!VMware!Server!(provided!you!agree!to!
install!host‐only!networking).!If! you!did!not!agree!to!use!host‐only!networking,!you!
need!to!run!the!script!again!to!
set!up!host‐only!networking.
To!set!up!the!second!host‐only!network,!follow!the!steps!outlined!below!for!your!host!
operating!system.