VMware Server 2.0.1

VMware heeft buildnummer 156745 van zijn virtualisatie software Server 2.0.1 uitgebracht. Dit pakket doet zijn werk onder Linux en Windows en is in staat om via een virtuele machine diverse besturingssystemen op de hostcomputer te laten draaien. Voor de gast computer kan je gebruikmaken van verschillende BSD-varianten, diverse Linux-distributies, Solaris en Windows. Voor meer informatie verwijzen we jullie door naar deze pagina en deze handleiding in pdf-formaat. De lijst met veranderingen voor versie 2.0.1 ziet er als volgt uit:

What’s New
Server 2.0.1 is a maintenance release that resolves security as well as some known issues. With this release of VMware Server, certain new features and support have been added.
Support for New Guest Operating Systems
VMware provides support for the following operating systems for Server 2.0.1:

  • Asianux Server 3.0 Service Pack 1
  • CentoOS 4.7
  • CentOS 5.2
  • Windows Essential Business Server (EBS) and Small Business Server (SBS) 2008
  • Windows Small Business Server 2003 Service Pack 2
  • Windows XP Service Pack 3
  • Windows Vista Service Pack 1

Security Fixes:

  • VMnc codec heap overflow vulnerabilities
    The VMnc codec assists in record and replay of sessions which are records of the dynamic virtual machine state over a period of time. Two heap overflow vulnerabilities might allow a remote attacker to execute arbitrary code on VMware hosted products. For an attack to be successful, the user must visit a malicious Web page or open a malicious video file. The Common Vulnerabilities and Exposures project has assigned the names CVE-2009-0909 and CVE-2009-0910 to these issues.
  • A VMCI privilege escalation on Windows-based hosts or Windows-based guests
    The Virtual Machine Communication Interface (VMCI) provides fast and efficient communication between two or more virtual machines on the same host and between a virtual machine and the host operating system. A vulnerability in vmci.sys might allow privilege escalation on Windows-based machines. This might occur on Windows-based hosts or inside Windows-based guest operating systems. Current versions of ESX Server do not support the VMCI interface and hence they are not affected by this vulnerability. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1147 to this issue.
  • A remote denial-of-service vulnerability in authd for Windows-based hosts
    A vulnerability in vmware-authd.exe might cause a denial-of-service condition on Windows hosts. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-0177 to this issue.
  • Updated vm-support script
    This release improves data collection when the vm-support script is run by the Server administrator on request of VMware support or its support partners. The file that contains the SSL keys for communication between Server and vCenter and other applications is no longer collected. For more details, see the KB article Data Security Best Practices – SSL keys for communicating with VirtualCenter and other applications (KB 1008166).
  • Windows-based host privilege escalation in hcmon.sys
    A vulnerability in an I/O Control (ioctl) function in hcmon.sys might be used to escalate privileges on a Windows-based host. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1146 to this issue. New releases of hosted products address a denial-of-service problem described in CVE-2008-3761, which can only be exploited by a privileged Windows account.
  • Denial-of -service vulnerability in a virtual device
    A vulnerability in a guest virtual device driver might allow a guest operating system to cause the host and consequently any virtual machine on that host to fail. The Common Vulnerabilities and Exposures project has assigned the name CVE-2008-4916 to this issue.

Miscellaneous Fixes:

  • Mount installer option mounts current CD-ROM image instead of VMware Tools installer image
    If a CD-ROM image is mounted to a virtual machine with VMware Tools installed, the Mount installer option in the Web UI incorrectly mounts the CD-ROM image instead of the VMware Tools image. The issue is resolved in this release.
  • Unable to install the latest version of VIX API on Server 2.0.x
    You cannot install VMware VIX API 1.6.2 of due to an issue with the MSI installer for VIX API. This issue is resolved in this release.
  • The default VI Web Access HTTP connection port is 8222 and the default HTTPS port is 8333. If you use these defaults, or any values other than 80 (HTTP) and 443 (HTTPS), you must specify the port number when you connect to VMware Server using VI Web Access. You must also allow connection to these ports through your firewall. An example URL to connect to VI Web Access is http://server_host:8222 If you want to use ports 80 (HTTP) and 443 (HTTPS), override the default values during installation. Note: If you are running IIS or Apache web server on the default ports, specify alternate HTTP and HTTP ports when prompted by the Windows installer or vmware-config.pl. Alternatively, stop IIS’s default Web site or any other Web site running on these ports. On Linux, shut down Apache or any other application using these ports and make sure they are not configured to restart automatically. This issue is resolved in this release.

VMware Server 2.0 Tips and Tricks


Hierbij sommige  Tips & Tricks van VMWare Server 2.0

1. Use a web browser (Firefox and Internet Explorer are the two officially supported ones) to
connect to http://yourserver:8222 or https://yourserver:8333 if you selected the default
ports during installation/configuration.

2. If you manage from a Windows client then the VI (Virtual Infrastructure) client is also
available which is what is used to manage ESX/ESXi and Virtual Center too. It is available at

3. The VI Client cannot add USB devices to VMs running at hardware versions greater than 4 –
version 7 is required for USB 2.0 support.

4. Specify yourserver:8333 for the connection in the VI Client.

5. The credentials you specify to logon are admin credentials that you would use on the host
even without VMware installed – VMware does not introduce any credentials/accounts

6. The admin account you use must have a password defined for it or you will not be able to

7. The remote console is a locally installed application which will be installed when the console
tab is first clicked onto.

8. For remote management through firewalls, VPNs or over SSH tunnels, port 902 is also used as well as 8222/8333. Note that during Linux configuration; you may have selected a
different port from 902 as sometimes it can be statically detected as being in use.

9 .Backing up VMs can be achieved in a number of ways:
a. If the VM is not powered up then simply copy all of its files to another location.
b. If the VM is running, take a snapshot and then copy the base disk file(s) to another
location (*.vmdk except *-00001*.vmdk). A new VM can then be constructed using
this disk. Note that you can only have a single snapshot.
c. In a Windows VM, use a VSS (Volume Shadow copy Service) aware backup tool to
create a backup that can then be restored using the same tool to a bare VM.
d. On a Windows host, use a VSS aware backup tool to backup the files that constitute
the VM.

10. If a VM fails to power on and was not shut down properly, check for .lck files/folders and
remove them if they exist as long as the VM definitely is not running.

11. Server 2.0 stores VMs in datastores – a default datastore is created which is calle
“[standard]” and will map to the root of the folder you select during installation.

12. VMs can be run from external USB drives by defining a datastore for the mount point.

13. Remote datastores can also be added – NFS for Linux hosts and CIFS/SMB for Windows.

Bekijk HIER de volledige PDF met Tips & Tricks van VMWare Server 2.0

Translate »