1,798
edits
Changes
no edit summary
== Supported Linux Distributions ==
Whilst VMware Server 2.0 is capable of running on a variety of different Linux distributions, only a subset are officially supported as outlined in the following table. Note that unless otherwise stated, these operating systems are supported in both 32-bit and 64-bit versions:
<table border="1" cellpadding="5" cellspacing="0" id="E3B" style="border-collapse: collapse; border-color:#cccccc; border-style: solid; border-width: 1px; margin-bottom:20px">
Although not officially listed as a supported operating system, VMware Server 2.0 will also run on CentOS Linux 5.0 and 5.1 since these are essentially re-branded versions of the corresponding Red Hat Enterprise Linux versions.
Note that unless otherwise stated, the above operating systems are supported in both 32-bit and 64-bit versions. One other key issue to be aware of is that VMware Server 2.0 will only support 64-bit ''guest'' operating systems on host computers with either Intel EM64T VT or AMD64 D or newer processors.
== VMware Server 2.0 and Unsupported Linux Distributions ==
Host-only networking will similarly require a name and an unused private subnet which may be entered manually or automatically identified by the configuration script. Once the network configuration process is complete, ''vmware-config.pl'' will load the VMware Server network kernel module (vmnet) into the running kernel of the host operating system.
The next step of the configuration involves defining how the VMware Server management interface console will be accessed, both for local and remote administrationpurposes. VMware Server 2.0 differs from previous releases of the product in that the management interface is entirely browser based so both local and remote administration tasks will be performed using a web browser. The first option to configure is the port through which the VMware Server environment will be accessed from remote systems. The default is port 902. Finally, the HTTP and secure HTTPS access ports need to be specified. By default these are 8222 and 8333 respectively. Therefore, if the host system has an IP address of 192.168.2.21, then the management interface would be accessed securely by entering 192.168.2.21:8333 in a browser URL field. Different ports may, of course, be specified if required, for example to avoid conflict with other applications or to accommodate firewall restrictions. Next is the designation of a user to act as the administrator of the VMware Server environment. When prompted, enter 'y' to configure a different administrator and provide the name of the user to be given administrative access to the VMware Server system. This users name and system password will subsequently be used to gain access to the management console. Once the administrator has been assigned, specify the location for the virtual machine files and, finally, enter the serial number, of the form XXXXX-XXXXX-XXXXX-XXXXX recorded at the beginning of this chapter to unlock the VMware Server software. With VMware Server configured, follow the instructions to install the optional VMware VIX API packages, using the defaults offered. Finally, ''vmware-config.pl'' will start up the VMware Server 2.0 services, presenting output similar to the following (depending on which network options were selected): <pre>Starting VMware services: Virtual machine monitor [ OK ] Virtual machine communication interface [ OK ] VM communication interface socket family: [ OK ] Virtual ethernet [ OK ] Bridged networking on /dev/vmnet0 [ OK ] Host-only networking on /dev/vmnet1 (background) [ OK ] DHCP server on /dev/vmnet1 [ OK ] Host-only networking on /dev/vmnet8 (background) [ OK ] DHCP server on /dev/vmnet8 [ OK ] NAT service on /dev/vmnet8 [ OK ] VMware Server Authentication Daemon (background) [ OK ] Shared Memory Available [ OK ]Starting VMware management services: VMware Server Host Agent (background) [ OK ] VMware Virtual Infrastructure Web AccessStarting VMware autostart virtual machines: Virtual machines [ OK ] The configuration of VMware Server 2.0.0 build-110949 for Linux for this running kernel completed successfully.</pre>
