ADVANCED SERVER VIRTUALIZATION VMware and Microsoft Platforms in the Virtual Data center phần 6 pot

358  Advanced Server Virtualization between virtual network adapters connected to that virtual switch.  ere are three virtual machines confi gured on this ESX Server. Virtual Machine 1 has one virtual network adapter that is connected to Virtual Switch 0. Network traffi c from Virtual Machine 1 will be routed through Virtual Switch 0 and on through vmnic0, if necessary. Note that Virtual Switch 1 does not have a virtual network adapter connected. No traffi c will be present on Virtual Switch 1 and therefore no traffi c will be present on vmnic1, the physical network adapter to which Virtual Switch 1 is bound. Virtual Machine 2 has two virtual network adapters installed.  e fi rst virtual network adapter, Ethernet0, is connected to Virtual Switch 2 and the second virtual network adapter, Ethernet1, is connected to Virtual Switch 3. Virtual Machine 3 has an identical network confi guration as Physical Server Hardware Layer VMware ESX Server Virtualization Layer Virtual Machine 1 Ethernet0 Virtual Machine 2 Ethernet0 Virtual Machine 3 Ethernet0 Service Console eth0 vmnic0 vmnic1 vmnic2 vmnic3 vmnic4 DIRECT ACCESS TO PHYSICAL NETWORK ADAPTER bond0 Virtual Switch 0 Virtual Switch 1 2 3 vmnet_0 Ethernet1 Ethernet1 Physical Network Switch Virtual Switch Virtual Switch Figure 17.13 VMware ESX Server Networking Components. Marshall_AU3931_C017.indd 358Marshall_AU3931_C017.indd 358 4/13/2006 1:41:50 PM4/13/2006 1:41:50 PM VMware ESX Server Advanced Topics  359 Virtual Machine 2.  ese two virtual machines must be important because they both have their external network connections bound to Virtual Switch 2. Virtual Switch 2 is bound to bond0, which aggregates three physical network adapters. Bond0 could lose up to two physical network adapters without aff ecting the connectivity to Virtual Machine 2 and Virtual Machine 3.  e second virtual network adapter in Virtual Machine 2 and Virtual Machine 3 are connected to Virtual Switch 3, which is a private network because Virtual Switch 3 is not bound to any physical network adapters in the server. Virtual Machine 2 and Virtual Machine 3 can communicate with each other over this link. It is possible that these two virtual machines are clustered and need a private network link in order to monitor each other.  is diagram shows a fairly complex networking scenario that is possible with ESX Server, although even more complex confi gu- rations are possible. MAC Addresses Virtual network adapters can have one or more IP addresses assigned to them.  is is completely confi gured and controlled by the virtual machine’s guest op- erating system. Virtual network adapters must also have a MAC address just as if it were a physical network adapter. Physical network adapters have a glob- ally unique MAC address permanently assigned to each card. Because virtual network adapters are created in software, their MAC addresses cannot be per- manently assigned as in a physical network adapter. Instead, the MAC address is a confi gurable value assigned to each virtual network adapter either dynami- cally by ESX Server or statically by an administrator. Dynamic MAC addresses are automatically generated by ESX Server and static MAC addresses must be confi gured explicitly by an administrator for each virtual network adapter that requires a static MAC address.  e value of a virtual network adapter’s MAC address is stored within the virtual machine’s confi guration fi le. If a virtual ma- chine has not been explicitly confi gured to use a static MAC address for a virtual network adapter, it will have a dynamically generated MAC address assigned to the virtual network adapter.  ere are three keyword/value pairs in the virtual machine’s confi guration fi le that specify the dynamically generated MAC ad- dress.  ey are as follows: Ethernet<id>.addressType = “generated” Ethernet<id>.generatedAddress = “00:0c:29:1e: aa:94” Ethernet<id>.generatedAddressOffset = “0”  e <id> token represents the id of the specifi c virtual network adapter. For virtual machines that have only one virtual network adapter, <id> usually equals 0 (Ethernet0). If a virtual machine has more than one virtual network adapter, the <id> of each virtual network adapter is incremented by 1. A virtual machine Marshall_AU3931_C017.indd 359Marshall_AU3931_C017.indd 359 4/13/2006 1:41:51 PM4/13/2006 1:41:51 PM 360  Advanced Server Virtualization confi gured with two virtual network adapters will have a set of entries for Ether- net0 and another set of entries for Ethernet1 in its confi guration fi le.  e Ethernet<id>.addressType keyword/value pair defi nes the type of MAC address that is assigned to the virtual network adapter.  is keyword/value pair is used for dynamically generated MAC addresses and for static MAC addresses. If a dynamically generated MAC address is being used, the value is “generated.” If a static MAC address is being used, the value is “static.”  e Ethernet<id>.generatedAddress keyword/value pair contains the actual MAC address that has been dynamically generated and assigned to the virtual machine.  is keyword/value is created automatically upon powering on the virtual machine when then Ethernet<id>.addressType keyword has a value of “generated.” In ESX Server, dynamically generated MAC addresses always use 00:0C:29 as the fi rst three bytes of the MAC address value.  is is one of two Organizationally Unique Identifi ers (OUI) assigned to VMware for use with virtual MAC addresses. VMware’s other OUI, 00:50:56, is used for static MAC addresses.  e Ethernet<id>.generatedAddressOff set keyword/value pair is also required when using dynamically generated MAC addresses and its value is usually zero.  is keyword/value is created automatically upon powering on the virtual ma- chine when then Ethernet<id>.addressType keyword has a value of “generated.”  is value is the off set used against the virtual machine’s UUID (Universally Unique Identifi er) when generating MAC addresses. ESX Server uses an algorithm for generating dynamic MAC addresses that at- tempts to create MAC address value unique not only within a single ESX Server, but also across ESX Servers. Each virtual machine has a keyword/value pair in its confi guration fi le named uuid.location.  is keyword/value pair contains the virtual machine’s UUID, which is a 128-bit (16-byte) numeric value that is universally unique within its given context.  is means that no other virtual ma- chines will have the same UUID, even across multiple ESX Servers around the world. UUID (also referred to as GUID for Globally Unique Identifi ers) genera- tion is very common in many computing scenarios where an object should have a unique name across all space and time. In ESX Server, each virtual machine’s UUID is based in part by the absolute path to the virtual machine’s confi gura- tion fi le and by the ESX Server’s SMBIOS UUID. If a confl ict occurs when generating a dynamic MAC address on a single ESX Server, the Ethernet<id>. generatedAddressOff set value is incremented and the algorithm is generates a new MAC address.  is iterative process repeats until a unique MAC address is generated. In almost all cases, the unique MAC address is generated on the fi rst attempt. It is important to note that ESX Server cannot check for confl icting MAC addresses across multiple ESX Servers. Instead of relying on ESX Server to create unique MAC addresses, it is pos- sible to confi gure static MAC addresses for each virtual network adapter. Static MAC addresses must be explicitly confi gured by an administrator to be used. Marshall_AU3931_C017.indd 360Marshall_AU3931_C017.indd 360 4/13/2006 1:41:51 PM4/13/2006 1:41:51 PM VMware ESX Server Advanced Topics  361 Static MAC addresses in ESX Server must use the VMware OUI, 00:50:56 as the fi rst 3 bytes of the static MAC address value.  is is in stark contrast to Mi- crosoft Virtual Server, which allows any MAC address value to be used without restrictions. Furthermore, ESX Server limits the range of allowable values for the fourth byte of static MAC addresses to the range 00 to 3F. Static MAC addresses must be within the following range: 00:50:56:00:00:00 to 00:50:56:3F:FF:FF. To confi gure a virtual network adapter to use a static MAC address, the vir- tual machine’s confi guration fi le must be edited as follows.  Remove the following keyword/value pairs: Ethernet<id>.generatedAddress Ethernet<id>.generatedAddressOffset  Edit the following keyword/value pair: From: Ethernet<id>.addressType = “generated” To: Ethernet<id>.addressType = “static”  Add the following keyword/value pair: Ethernet<id>.address = “<mac>” In the listing above, <id> is the Ethernet adapter number of the virtual network adapter being confi gured with a static MAC address and <mac> is the value of the static MAC address using the format: OO:UU:II:XX:YY:ZZ where OO:UU: II represents the static MAC address OUI for VMware ESX Server, 00:50:56, and XX:YY:ZZ represents the unique MAC address value from 00:00:00 to 3F: FF:FF. To confi gure a virtual network adapter to use a dynamically generated MAC address instead of a static MAC address, the virtual machine’s confi guration fi le must be edited as follows.  Remove the following keyword/value pairs: Ethernet<id>.address  Edit the following keyword/value pair: From: Ethernet<id>.addressType = “static” To: Ethernet<id>.addressType = “generated” )  e next time the virtual machine is powered on, the necessary keyword/value pairs that support a dynamically generated MAC address will automatically be Marshall_AU3931_C017.indd 361Marshall_AU3931_C017.indd 361 4/13/2006 1:41:51 PM4/13/2006 1:41:51 PM 362  Advanced Server Virtualization added to the virtual machine’s confi guration fi le as well as the new, dynamically generated MAC address value. In ESX Server, MAC address values are colon-delimited unlike Microsoft Vir- tual Server where MAC address values are hyphen-delimited. As a best practice, the values of MAC addresses should be in all upper case. Another best practice is to confi gure static MAC addresses for all virtual network adapters in all virtual machines and make the necessary confi guration updates before the fi rst time that the virtual machine is powered on.  is reduces the chances of confi guring the TCP/IP properties of a virtual machine with a dynamic MAC address and then later changing it to a static MAC address and confusing the network switch by ARPing the same IP address with two diff erent MAC addresses. It is extremely important that MAC addresses within a network are unique. It is a best practice to use a static, unique MAC address for every virtual net- work adapter across all physical servers, ESX Servers, and virtual machines in an entire data center. Even though MAC addresses realistically only need to be unique within an Ethernet collision domain, the isolation of some physical net- work switch’s VLAN implementations can be suspect. Also, within ESX Server, although virtual switches do provide network isolation, if two isolated virtual switches have virtual network adapters connected which have the same MAC address, strange eff ects have been experienced even though the two confl icting MAC addresses could never “see” each other. Keeping all MAC addresses of all virtual network adapters 100 percent unique is a good method of eliminating potential and seemingly obscure network problems. To determine the MAC address of a virtual network adapter within a virtual machine in the Service Console, open the virtual machine’s confi guration fi le with an editor such as emacs, vi, or nano in order to manually search for the MAC address value or use the cat command piped into a grep command such as: # cat <confi g_fi le_path> | grep [Ee]thernet [0-9]. address or # cat <confi g_fi le_path> | grep [Ee]thernet [0-9].generatedAddress  e <confi g_fi le_path> token is the path to the virtual machine’s confi gura- tion fi le.  e fi rst command will output only lines for virtual network adapters containing a static MAC address and the second command will output only lines for virtual network adapters containing a dynamically generated MAC ad- dress for the specifi ed virtual machine. To determine the MAC address of the physical network adapter bound to the Service Console, use the ifconfi g command and obtain the value from the Marshall_AU3931_C017.indd 362Marshall_AU3931_C017.indd 362 4/13/2006 1:41:52 PM4/13/2006 1:41:52 PM VMware ESX Server Advanced Topics  363 ifconfi g command’s output for eth0, fi eld HWaddr, or simply use the following command: # ifconfi g | grep eth0  e output from the command above should look similar to the following: eth0 Link encap:Ethernet HWaddr 00:1C:03:B1:14:ED  e value following the string token, HWaddr, is the MAC address value of eth0.  e MAC address value of all physical network adapters allocated to the VM- Kernel for use by virtual machines cannot be easily determined because they are never used.  e physical server does not have a valid TCP/IP stack bound to any of the vmnic network adapters, therefore their burned-in MAC addresses are never broadcast to the network. Virtual machines connected to virtual switches that are bound to the vmnic network adapters have a TCP/IP stack bound to the virtual network adapter bridged to the physical network adapter.  e vmnics act like a bridge device in this context, connecting the external network to the vir- tual networks within an ESX Server.  e MAC addresses of the virtual network adapters are broadcast to the network and for those virtual network adapters bound to external networks, their MAC addresses are broadcast to the physical networks to which they are bridged. Promiscuous Mode By default, virtual switches in ESX Server are not allowed to operate in pro- miscuous mode.  is is done for security purposes, reducing the eff ectiveness of using packet sniff er and network analyzer applications from within a virtual machine. In some cases, there may be a legitimate need to enable promiscuous mode for a virtual switch.  is should be done with care. Promiscuous mode can be enabled on virtual switches that are bound to a physical network adapter or a vmnet device. When promiscuous mode is enabled for a virtual switch bound to a physical network adapter, all virtual machines connected to the virtual switch have the potential of reading all packets sent across that network, from other virtual machines as well as any physical machines and other network devices. When promiscuous mode is enabled on a virtual switch not bound to a physical network adapter (one that is instead bound to a vmnet device), all virtual ma- chines connected to the virtual switch have the potential of reading all packets sent across that network, that is, only from other virtual machine connected to the same virtual switch.  ere is no method of permanently enabling promiscu- ous mode for a virtual switch. To enable promiscuous mode for a virtual switch, a value is poked into a special virtual fi le in the /proc fi le system.  is means that the value takes eff ect in memory only and is not persisted. Upon the next reboot of the ESX Server, the value will revert to its default value, which is to not Marshall_AU3931_C017.indd 363Marshall_AU3931_C017.indd 363 4/13/2006 1:41:52 PM4/13/2006 1:41:52 PM 364  Advanced Server Virtualization enable promiscuous mode. Because the necessary virtual fi le in the /proc fi le sys- tem only exists when a virtual switch is connected to either a physical network adapter or a virtual network adapter, promiscuous mode can only be enabled on virtual switches not bound to a physical network adapter when a powered-on virtual machine has a virtual network adapter connected to the virtual switch. If a virtual switch not bound to physical network adapter has no live connec- tions from virtual machines, the necessary /proc fi le does not exist and therefore the value cannot be modifi ed. Virtual switches that do have a physical network adapter bound to it can have its promiscuous mode enabled or disabled at any time.  erefore, one method of persisting a virtual switch to have promiscuous mode enabled is to add the command that enables promiscuous mode to the /etc/rc.local boot script in the Service Console. To determine if promiscuous mode is enabled or disabled, enter the following command in the Service Console using an account with root-level access: # cat /proc/vmware/net/<device>/confi g | grep PromiscuousAllowed  e <device> token represents the name of the network device being queried, either a vmnic, a vmnet, or a bond. For example, to query vmnic0 for its current promiscuous mode state: # cat /proc/vmware/net/vmnic0/confi g | grep PromiscuousAllowed PromiscuousAllowed No  e output from this example displays that promiscuous mode is not enabled for vmnic0. To change the promiscuous mode enabled state for a network device, use the following command: # echo “PromiscuousAllowed <value>” > /proc/ vmware/net/<device>/confi g  e <value> token must be no to disable promiscuous mode or yes to enable promiscuous mode for the specifi ed <device>.  e <device> token represents the name of the network device being queried, either a vmnic, a vmnet, or a bond. In the following example, vmnic0 is queried to determine if promiscuous mode is enabled. Next, a command is issued to enable promiscuous mode for vmnic0. Finally, the command of the original query is executed again to deter- mine if the promiscuous mode state has been changed for vmnic0. # cat /proc/vmware/net/vmnic0/confi g | grep PromiscuousAllowed PromiscuousAllowed No # echo “PromiscuousAllowed yes” > /proc/vmware/ net/vmnic0/confi g Marshall_AU3931_C017.indd 364Marshall_AU3931_C017.indd 364 4/13/2006 1:41:52 PM4/13/2006 1:41:52 PM VMware ESX Server Advanced Topics  365 # cat /proc/vmware/net/vmnic0/confi g | grep PromiscuousAllowed PromiscuousAllowed Yes If a vmnic or bond should have promiscuous mode enabled at all times, the command to enable promiscuous mode for the particular device can be added at the end of the/etc/rc.local boot script.  is fi le can easily be edited using emacs, vi, or nano. VLAN Tagging (Port Groups) Virtual switches in ESX Server support the use of VLANs, Virtual Local Area Networks.  is feature is also referred to as Port Groups in ESX Server. In the networking community, VLANs are very common as they provide a method of abstracting and isolating network segments from each other. VLAN technol- ogy is usually implemented in managed network switches. It is no surprise to discover that in ESX Server, VLANs are implemented as a feature of virtual switches.  e term Port Groups is used synonymously with VLAN Tagging. In this context, the term port refers to a virtual Ethernet port in a virtual switch and is not to be confused with the term port as it is used in TCP/IP. VLAN Tag- ging allows groups of ports in a switch to be bound together to form a virtual local area network, or VLAN.  e groups of switch ports defi ned with the same VLAN ID act as if they were on a dedicated switch and do not see traffi c from other VLANs.  e VLAN Tagging feature in ESX Server allows connections to virtual switches to belong to a VLAN, which can participate in VLANs external to the ESX Server environment in the physical network. By default, the VLAN Tagging feature is enabled in the VMKernel, but is not used until one or more Port Groups have been confi gured. Resource Management ESX Sever provides very rich facilities for resource management of virtual ma- chines, including the Service Console.  ere are several techniques used to con- trol and shape the amount of resources allocated to virtual machines.  ese techniques include:  Shares  CPU affi nity  Min/Max percentages  Min/Max amounts  Network traffi c shaping  e resource management techniques listed above may be used independent- ly or in combination to achieve the desired amount of performance from virtual Marshall_AU3931_C017.indd 365Marshall_AU3931_C017.indd 365 4/13/2006 1:41:52 PM4/13/2006 1:41:52 PM 366  Advanced Server Virtualization machines. Most virtual machines should not require resource tweaking.  e re- source management features of ESX Server are designed to be applied to specifi c virtual machines that have a high sensitivity to performance.  e primary method used to control how much of a particular resource is given to a virtual machine at a particular point in time is the use of shares.  e shares system applies to CPU, memory, and disk resources. By default, all virtual machines are created with an equal number of shares for CPU, memory, and disk.  e default number of shares allocated per resource per virtual machine is 1000. Using this default setting, all virtual machines receive the same amount of resources.  e default value of 1000 is considered to be the normal amount of shares.  e shares system of resource allocation is proportional; therefore if the normal amount of shares is 1000, assigning 2000 shares of a particular re- source for a virtual machine allocates double the amount of that resource for that virtual machine relative to the other virtual machines that have the normal amount of shares (1000). For example, consider an ESX Server with three virtual machines: Vm1, Vm2, and Vm3. Vm1 has 2000 CPU shares, Vm2 has 1000 CPU shares, and Vm3 has 500 CPU shares. Vm1 will receive twice the amount of CPU cycles then Vm2 and four times as many CPU cycles as Vm3. VM3 will receive half as many CPU cycles as Vm2.  e same amount of CPU cycle would be allocated to the virtual machines if the shares allocated were set to the follow- ing values: Vm1 has 200 CPU shares, Vm2 has 100 CPU shares, and Vm3 has 50 CPU shares.  is is due to the proportional or relative nature of the shares resource allocation system. Most ESX Servers run on multiprocessor hardware system such as dual pro- cessor or quad processor servers. It is possible to assign virtual machines to run on specifi c processors.  is feature is called CPU affi nity. By default, virtual machines’ instructions are load balanced across all processors in the server. ESX Server’s scheduler determines which processors will execute particular instruc- tions for virtual machines. Using the CPU affi nity feature, it is possible to con- fi gure a virtual machine to run only on specifi c processors in the system. Using CPU affi nity greatly reduces ESX Server’s fl exibility in the scheduler to provide optimum performance for all virtual machines. Another technique used to control resource allocation to virtual machines is Min/Max percentages. ESX Server uses Min/Max percentages with CPU re- sources. In this scheme, virtual machines can be confi gured to receive a mini- mum and a maximum amount of CPU cycle by the overall percentage of CPU cycles available.  is is often used to guarantee that a virtual machine receives a guaranteed minimum number of CPU cycles in order to avoid CPU starvation issues. Additionally, a virtual machine can be confi gured with a maximum of less than 100 percent to limit the amount of CPU cycles allocated to the virtual machine.  is is often confi gured on very low priority virtual machines to avoid having those virtual machines consume too many CPU cycles.  e Min/Max percentages can be used independently or together on specifi c virtual machines Marshall_AU3931_C017.indd 366Marshall_AU3931_C017.indd 366 4/13/2006 1:41:52 PM4/13/2006 1:41:52 PM VMware ESX Server Advanced Topics  367 as needed. By default, virtual machines are created with a minimum CPU per- centage of 0 percent and a maximum CPU percentage of 100 percent. ESX Server uses the Min/Max amounts technique in addition to shares to control memory allocation for virtual machines. Virtual machines are always confi gured with an amount of memory.  is value is the virtual machine’s maxi- mum amount of memory. Memory is allocated to virtual machines as they re- quire it, based upon their shares, and the state of the virtual machine. Memory can be reclaimed and reallocated dynamically by ESX Server when a virtual machine is idle or frees up a block of previously allocated memory. Some virtual machines may require a minimum amount of memory to be always present. Virtual machines can have a minimum amount of memory allocated to them. Upon powering on the virtual machine, ESX Server will allocate the minimum amount of memory to the virtual machine. By default, virtual machines have a minimum memory value of zero.  e more memory that is allocated as min- imum memory to virtual machines reduces the eff ectiveness of ESX Server’s memory management features. ESX Server uses only the proportional shares technique to manage disk re- sources. Disk resources are measured in terms of disk bandwidth for each physi- cal disk or LUN, each represented by a vmhba.  e disk bandwidth is calculated in consumption units in which each SCSI command equals on consumption unit and the size of the data to be transferred is converted into a proportional number of additional consumption units. Additionally, each virtual machine may, by default, issue up to eight SCSI commands before being preempted by another virtual machine requesting disk access. Network bandwidth resources are managed in a much diff erent manner than other resources. Instead of using the proportional shares or Min/Max meth- ods, network bandwidth is controlled by a pluggable network packet fi lter mod- ule. ESX Server ships and supports only one fi lter module at this time named nfshaper.  is module implements a transmit fi lter that performs network traffi c shaping on outgoing traffi c.  e nfshaper module can be attached and confi g- ured for each virtual machine.  e traffi c shaping feature implemented by the nfshaper module can be used to limit the average bandwidth, peak bandwidth, and the maximum burst size measured in bits per second (bps). Performance Optimization Here are some best practices that can be used to gain optimum performance for virtual machines hosted on an ESX Server:  Ensure that the proper guest operating system type is confi gured for each virtual machine, Ensure that VMware Tools is properly installed and is up to date in each virtual machine. Before placing a virtual machine running Windows into production, defragment all virtual hard drives attached to Marshall_AU3931_C017.indd 367Marshall_AU3931_C017.indd 367 4/13/2006 1:41:52 PM4/13/2006 1:41:52 PM [...]... physical server that is running either Microsoft Windows or a Linux server operating system Then, virtual machines are configured within the software much like a physical server would be An operating system, known as a guest operating system, would then be installed on the virtual machine These servers can be loaded with various guest operating systems including standard Microsoft Windows and Linux operating... Reduce the density of virtual machines running on each ESX Server If there are many virtual machines running on one ESX Server that are consuming and severely competing for CPU, memory, or disk resources, consider reducing the density of virtual machines on the ESX Server by moving some of the virtual machine to another ESX Server Although ESX Server is highly optimized and can run many virtual machines... on the same installation CD-ROM, each product has its own serial number and one cannot be used to install the other Marshall_AU3931_C018.indd 375 3/31/20 06 2:51:53 PM 3 76 Advanced Server Virtualization In addition to versioning the product by host operating system, VMware also further breaks the product down by versioning against the number of processors found within the host server VMware sells these... guest operating systems and their applications If the guest operating system has a small footprint when it comes to resources needed, such as a small Linux machine, then more virtual machines could be executed against the processor If on the other hand, the virtual machine contains a CPU intensive application, such as a Microsoft SQL database, then fewer virtual machines can be executed against the processor... for installation: VMware GSX Server and VMware Management Interface The VMware GSX Server component provides the core functionality of GSX Server; and without it, it is not possible to create and configure virtual machines or use the system as a host server platform for virtualization This component must be installed if the server is going to be a virtualization host server Additionally, the option installs... Installing VMware GSX Server 387 Preparing the Host Operating System The host operating system is the next critical step in building the proper platform for GSX Server The detailed steps involved with installing the host operating system will not be covered in this book It is assumed that a basic level of understanding and experience with installing the server operating system already exists The proper configuration... Complete The complete choice is exactly what it sounds like, a complete installation of all components Therefore, all options are activated and installed The complete installation will set up the following components on the host server: the server software, the VMware Management Interface, the VMware Virtual Machine Console, the VmCOM API and the VmPerl API The complete installation is the default installation... installed To install the component, the Figure 19.4 VMware GSX Server Master Installer—IIS Missing installation must be cancelled by clicking the Cancel button, and then IIS must be installed and properly configured on the host server Once complete, the installation process can be executed again Or to continue the installation without the Management Interface, click the OK button The Management Interface... begin copying files to the host server If the Master Installer detects that the host server has the CD-ROM autorun feature enabled, the screen shown in see Figure 19.7 will prompt for input during the installation Figure 19.7 VMware GSX Server Master Installer Disable CD-ROM Autorun Screen Disabling Autorun will help prevent undesirable interactions between the host server and the virtual machines If the. .. than installing many other types of applications on either operating system This chapter will cover the requirements of the product as well as information on the installation and basic configuration of the physical host server and the host operating system It will then walk through a step-by-step installation of GSX Server Because the Windows and Linux platforms are so significantly different in their installation . machine, then more virtual machines could be executed against the processor. If on the other hand, the virtual machine contains a CPU in- tensive application, such as a Microsoft SQL database, then. to 64 -bit host operating systems and continue to run existing 32-bit operating systems in virtual machines. With the introduction of support for 64 bit guest operating systems within the VMware. would then be installed on the vir- tual machine.  ese servers can be loaded with various guest operating systems including standard Microsoft Windows and Linux operating systems. VMware GSX Server