2.0
Table Of Contents
- VMware Server User’s Guide
- Contents
- About This Book
- Introduction and System Requirements
- VMware Server Product Benefits
- New Features of VMware Server 2.0
- Web-Based Interface
- VMware Remote Console
- Increased Memory Support
- Increase in Number of Network Adapters Supported
- Quiesced Backups of Virtual Machines on Windows
- Support for High-Speed USB 2.0 Devices
- Additional Host Operating System Support
- Additional Guest Operating System Support
- Improved 64-Bit Guest Support
- 64-Bit Sound Driver
- Native 64-Bit Host Support on Linux
- Updated VIX API
- VMCI Sockets Interface
- About the Host and Guest Computers
- Host System Requirements
- VI Web Access and VMware Remote Console Client System Requirements
- Virtual Machine Specifications
- Supported Guest Operating Systems
- Windows 64-Bit Operating Systems
- Windows 32-Bit Guest Operating Systems
- Linux 64-Bit Guest Operating Systems
- Linux 32-Bit Guest Operating Systems
- Sun Solaris 64-Bit Guest Operating Systems
- Sun Solaris 32-Bit Guest Operating Systems
- Novell NetWare 32-Bit Guest Operating System
- Processor Support for 64-Bit Guest Operating Systems
- Installing VMware Server
- Installation Prerequisites
- Installing VMware Server on a Windows Host
- Uninstalling VMware Server on a Windows Host
- Installing VMware Server on a Linux Host
- Configuring VMware Server on a Linux Host Using vmware-config.pl
- Uninstalling VMware Server on a Linux Host
- Upgrading from VMware Server 1
- Where to Go Next
- Learning VMware Server Basics: Using VI Web Access
- Creating and Upgrading Virtual Machines
- Before You Create a Virtual Machine
- Using the New Virtual Machine Wizard
- Installing the Guest Operating System
- Updating the Guest Operating System
- Upgrading the Virtual Machine Version
- Installing and Using VMware Tools
- Components of VMware Tools
- Installing VMware Tools
- Manually Installing VMware Tools in a Windows Guest System
- Configuring the Video Driver on Older Versions of Windows
- Installing VMware Tools in a Linux Guest System
- Installing VMware Tools in a Solaris Guest System
- Installing VMware Tools in a FreeBSD Guest System
- Installing VMware Tools in a NetWare Guest System
- Starting the VMware User Process Manually If You Do Not Use a Session Manager on UNIX
- Updating VMware Tools
- Uninstalling VMware Tools
- Repairing or Changing VMware Tools
- Using the VMware Tools Control Panel
- Customizing VMware Tools
- Using the VMware Tools Command-Line Interface
- Managing VMware Server
- Running Virtual Machines
- Running VMware Tools
- Changing the Power State of a Virtual Machine
- Changing Virtual Machine Name and Guest System Settings
- Changing Virtual Machine Power Settings
- Changing Virtual Machine Snapshot Settings
- Changing Virtual Machine Advanced Settings
- Deleting a Virtual Machine
- Using VMware Remote Console
- Generating and Sharing Virtual Machine Shortcuts
- Editing Notes in the Virtual Machine Summary Tab
- Editing the Hardware Configuration of a Virtual Machine
- Adding Hardware to a Virtual Machine
- Installing New Software in a Virtual Machine
- Advanced Options for Application Developers
- Configuring Virtual Machine Hardware
- Configuring Hard Disks
- Configuring CD/DVD Drives
- Configuring Floppy Drives
- Configuring Passthrough (Generic) SCSI Devices
- Configuring SCSI Controllers
- Configuring USB Controllers and Devices
- Configuring Sound
- Configuring Serial Ports
- Configuring Parallel Ports
- Keyboard Mapping on Linux Hosts
- Preserving the State of a Virtual Machine
- Suspending and Resuming Virtual Machines
- Using Snapshots
- What to Use Snapshots For
- What Is Captured by a Snapshot
- Activities That Conflict with Snapshots
- Enabling and Disabling Background Snapshots for All Virtual Machines
- Snapshots and a Virtual Machine’s Hard Disks
- Excluding Virtual Disks from Snapshots
- Taking a Snapshot
- Reverting to a Snapshot
- Removing a Snapshot
- Locking a Snapshot
- Managing Roles and Permissions
- Configuring a Virtual Network
- Network Basics
- Components of the Virtual Network
- Common Networking Configurations
- Example Custom Networking Configuration
- 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
- Potential 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
- Routing Between Two Host-Only Networks
- Using Virtual Network 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
- Using the Virtual Network Editor
- Performance Tuning for VMware Server
- Configuring and Maintaining the Host System
- Allocating Memory to a Virtual Machine
- Editing Virtual Machine Memory
- Using Two-Way Virtual Symmetric Multiprocessing
- Editing Virtual Processors
- Configuring and Maintaining Guest Operating Systems
- Installing Linux Guest Operating Systems in Text Mode
- Selecting the Correct Guest Operating System
- Installing VMware Tools
- Temporarily Disabling Acceleration in the Guest Operating System
- Avoiding Remote Disk Access
- Managing Snapshots and Virtual Disks
- Disabling Debugging Mode
- Disabling CD/DVD Drive Polling
- Disabling Fade Effects in Windows 2000, Windows XP, and Windows Server 2003
- Disabling Visual Effects in Windows 98
- Configuring Swap File Usage in Windows 95 and Windows 98
- Enabling Hardware Acceleration in Windows Server 2003
- Configuring Direct Memory Access (DMA) Disk Settings
- Using DMA in Windows NT Guests on Multiprocessor Host Systems
- Monitoring Virtual Machine Performance on Windows Hosts
- Configuring Clustering on Windows Hosts
- Defined Privileges
- Alarms
- Datacenter
- Datastore
- Extensions
- Folders
- Global
- Host CIM
- Host Configuration
- Host Inventory
- Host Local Operations
- Network
- Performance
- Permissions
- Resource
- Scheduled Task
- Sessions
- Tasks
- Virtual Machine Configuration
- Virtual Machine Interaction
- Virtual Machine Inventory
- Virtual Machine Provisioning
- Virtual Machine State
- Files That Make Up a Virtual Machine
- Glossary
- Index
VMware, Inc. 247
Chapter 11 Configuring a Virtual Network
5Ifyouarerunningtherouteronthehostcomputer,assigndefaultrouteraddresses
basedontheaddressesofthehost‐onlyadaptersonthehostcomputer.Inthefirst
virtualmachine’snetworkingconfiguration,thedefaultrouteraddressshouldbe
theIPaddressforthehost‐onlyadapterconnectedtoVMnet1.
Inthesecondvirtual
machine’snetworkingconfiguration,thedefaultrouteraddressshouldbetheIP
addressforthehost‐onlyadapterconnectedtoVMnet2.
Ifyouarerunningtheroutersoftwareonthethirdvirtualmachine,setthedefault
routeraddressesinthefirsttwovirtualmachinesbasedonthose
usedbythethird
virtualmachine.Inthefirstvirtualmachine’snetworkingconfiguration,the
defaultrouteraddressshouldbetheIPaddressforthethirdvirtualmachine’s
networkadapterconnectedtoVMnet1.Inthesecondvirtualmachine’snetworking
configuration,thedefaultrouteraddressshouldbetheIPaddressforthethird
virtualmachine’snetworkadapterconnectedtoVMnet2.
Atthispointyoushouldbeabletopingtheroutermachinefromvirtualmachinesone
andtwo.Andiftheroutersoftwareissetupcorrectly,youshouldbeableto
communicatebetweenthefirstandsecondvirtualmachines.
Using Virtual Network Adapters in Promiscuous Mode on a
Linux Host
VMwareServerdoesnotallowthevirtualnetworkadaptertogointopromiscuous
modeunlesstheuserrunningVMwareServerhaspermissiontomakethatsetting.This
followsthestandardLinuxpracticethatonlyrootcanputanetworkinterfaceinto
promiscuousmode.
WhenyouinstallandconfigureVMwareServer,you
mustruntheinstallationasroot.
VMwareServercreatestheVMnetdeviceswithrootownershipandrootgroup
ownership,whichmeansthatonlyroothasreadandwritepermissionstothedevices.
Tosetthevirtualmachine’snetworkadaptertopromiscuousmode,youmustlaunch
VMwareServerasrootbecauseyou
musthavereadandwriteaccesstotheVMnet
device.Forexample,ifyouareusingbridgednetworking,youmusthaveaccessto
/dev/vmnet0.
TograntselectedotherusersreadandwriteaccesstotheVMnetdevice,youcancreate
anewgroup,addtheappropriateuserstothegroupand
grantthatgroupreadand
writeaccesstotheappropriatedevice.Youmustmakethesechangesastherootuser
onthehostoperatingsystem.Forexample,youcanenterthefollowingcommands:
chgrp <newgroup> /dev/vmnet0
chmod g+rw /dev/vmnet0
<newgroup>isthegroupthatshouldhavetheabilitytosetvmnet0topromiscuous
mode.