VMware Server 1.0.x Release Notes
Knowledge Base |
VMware Server Community |
Release Date: October 27, 2009
Build Number: 203137
VMware Server is a free virtualization product for Microsoft Windows and Linux servers that enables you to provision new server capacity by partitioning a physical server into multiple virtual machines. This Release Notes document contains new features, limitations, caveats, security fixes, and general release information.
The Release Notes document covers the following topics:
What's New in VMware Server 1.0.x
This section lists all maintenance releases of VMware Server 1.0.x.
What's New in Version 1.0
This release provides the following support:
Support for 32-Bit and 64-Bit Operating Systems
- Support for SUSE Linux 10.1 as host and guest operating systems
- Support for 32-bit Ubuntu 6.x as host and guest operating systems
- Support for 32-bit Sun Solaris 10.x as guest operating systems
- Support for 32-bit and 64-bit FreeBSD 6.0 as guest operating systems
- Experimental support for Red Hat Enterprise Linux 3.0 Update 8 and Red Hat Enterprise Linux 4.0 Update 4
- Experimental support for 64-bit Ubuntu 6.x as host and guest operating systems
- Experimental support for 64-bit Sun Solaris 10.x as guest operating systems
- Support for all guest operating systems supported by Workstation 5.5
- Support for all host operating systems supported by VMware GSX Server 3.2
Other Key Features
- Support for taking and reverting to snapshots in the background.
- Experimental support for two-way Virtual Symmetric Multiprocessing (Virtual SMP). This lets you assign two virtual processors to a virtual machine on any host machine that has at least two logical processors.
- Support for using and upgrading legacy virtual machines.
- Ability to configure virtual hardware devices, including serial and parallel ports, DVD/CD-ROM drives, floppy drives, and sound drivers (Linux only) to be automatically detected.
VMware Products Supported by VMware Server
- Support for using the VMware Server Console to connect to and configure VMware GSX Server 3 hosts as well as to run virtual machines on VMware GSX Server 3 hosts.
- Support for vCenter Server version 1.4 to manage virtual machines running on VMware Server.
- Support for VMware Virtual Machine Importer version 1.5 to import virtual machines from Microsoft Virtual Server and Virtual PC as well as Symantec LiveState recovery system images.
- Support for VMware DiskMount Utility to mount a Microsoft Windows host file system as a separate drive without connecting to the virtual disk from within a virtual machine.
VMware APIs Included with VMware Server
- The Programming API (previously called C API)
- The VmCOM API (Windows hosts only)
- The VmPerl API
For more information on the features included in VMware Server 1.0, see the VMware Server Virtual Machine Guide. Refer the Known Issues section for additional information.
Installing on a Computer with a Different VMware Product
VMware Server cannot be installed on the same host as VMware Workstation, VMware Server, VMware Player, or VMware ACE. You cannot have multiple versions of VMware Server installed on the same host. Uninstall these VMware products before you install VMware Server. On a Windows host, use the Add/Remove Programs control panel. For a Linux host, see your product manual for the commands needed to uninstall the product.
Creating Virtual Machines
You can create new virtual machines in VMware Server, and use vCenter Server 1.4 to manage them. VMware Server creates virtual machines that are compatible with VMware Workstation 5.x. You must use the VMware Server Console to create and configure virtual machines. You cannot use the VMware Management Interface to create and configure virtual machines.
Note: When you create a new virtual machine, the wizard offers options for 64-bit versions of some guest operating systems. To determine whether your host computer can support a 64-bit guest, see Hardware and Firmware Requirements for 64-Bit Guest Operating Systems (KB 1901).
Using VMware Virtual Machine Importer
This product lets you import virtual machines from Microsoft Virtual Server and Virtual PC as well as Symantec LiveState recovery system images. To access the VMware Virtual Machine Importer from the VMware Server Console, choose File > Import. You can access the VMware Virtual Machine Importer only from the host machine.
Installing Guest Operating Systems
VMware Server supports guest operating systems supported by VMware Workstation 5.5 as well as other guest operating systems. For a list of supported guest operating systems and information about how to install them, see the Guest Operating System Installation Guide. You can also use virtual appliances downloaded from the Virtual Appliances Center of the VMware Technology Network.
Installing the Latest Version of VMware Tools
If you use existing virtual machines—either virtual machine created in a different VMware product or virtual machine created in an earlier release of VMware Server—install the version of VMware Tools included in this release (select Install VMware Tools from the virtual machine) for enhanced performance of guest operating systems.
Installing the VMware APIs
VMware Server supports the VMware scripting APIs and the Programming API (previously called C API). The scripting APIs include the VmCOM API (Windows hosts only) and the VmPerl API. You can install the APIs on any client machine. For more information about the VMware APIs, go to VMware APIs and SDKs Documentation.
The following issues are known to occur in VMware Server 1.0.x:
- On host machines with 64GB of RAM, running Windows Server 2003, an attempt to start a virtual machine in VMware Server causes the host machine to quit unexpectedly.
Limit Windows memory to 63GB:
If this does not work, limit Windows memory to 32GB:
- If your host machine is running a 64-bit version of Windows Server 2003, add /burnmemory=1024 to the boot.ini file.
- If your host machine is running a 32-bit version of Windows Server 2003, add /MAXMEM=64512 to the boot.ini file.
- If your host machine is running a 64-bit version of Windows Server 2003, add /burnmemory=32768 to the boot.ini file.
- If your host machine is running a 32-bit version of Windows Server 2003, add /MAXMEM=32768 to the boot.ini file.
- The VMware Server Console included with VMware Server 1.0.2 build 39867 cannot modify virtual machine configurations for VMware Server 1.0, VMware Server 1.0.1, or GSX Server 3 virtual machines.
Upgrade to VMware Server version 1.0.3 or higher. The VMware Server Console included with VMware Server 1.0.3 and higher versions manages VMware Server 1.0, 1.0.1, 1.0.2, and GSX Server 3 virtual machines.
Fixed in 1.0.10 |
Fixed in 1.0.9 |
Fixed in 1.0.8 |
Fixed in 1.0.7 |
Fixed in 1.0.6 |
Fixed in 1.0.5 |
Fixed in 1.0.4 |
Fixed in 1.0.3 |
Fixed in 1.0.2 |
Fixed in 1.0.1
This section provides the details of the issues resolved in various versions of VMware Server.
VMware Server 1.0.10
Server 1.0.10 addresses the following security and known issues:
- New: Exception handling privilege escalation on guest operating system
This release addresses a security vulnerability in exception handling. Improper setting of the exception code on page faults might allow for local privilege escalation on the guest. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-2267 to this issue.
Disk stress test fails with data corruption error
WLK DiskStress test fails with data corruption error on LSI Logic virtual device.
VMware Server 1.0.9
Server 1.0.9 addresses the following security issues:
- New: Host code execution vulnerability from a guest operating system
A critical vulnerability in the virtual machine display function might allow a guest operating system to run code on the host. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-1244 to this issue.
Updated vm-support script
Improved data collection when the vm-support script is run by the administrator on request of VMware support or its support partners. The file that contains the SSL keys for communication between VMware Server and other applications, is no longer collected. For more details, see 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 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.
VMware Server 1.0.8
Server 1.0.8 addresses the following security issue:
VMware Addresses Privilege Escalation on Guest Systems Running 32-Bit or 64-Bit Operating Systems
VMware products emulate hardware functions and create the possibility to run guest operating systems.
A flaw in the CPU hardware emulation might allow the virtual CPU to incorrectly handle the trap flag. Exploitation of this flaw might lead to a privilege escalation on guest operating systems.
An attacker needs a user account on the guest operating system and have the ability to run applications.
The Common Vulnerabilities and Exposures project has assigned the name CVE-2008-4915 to this issue.
VMware Server 1.0.7
Server 1.0.7 addresses the following security issues:
Security Fix for VMware ISAPI Extension
Internet Server Application Programming Interface (ISAPI) is an API that extends the functionality of Internet Information Server (IIS). VMware uses ISAPI extensions in its Server product.
One of the ISAPI extensions provided by VMware is vulnerable to a remote denial-of-service. By sending a malformed request, IIS might shut down. IIS 6.0 restarts automatically. However, IIS 5.0 does not restart automatically when its Startup Type is set to Manual.
The Common Vulnerabilities and Exposures project has assigned the name CVE-2008-3697 to this issue.
Setting ActiveX killbit
From this release, VMware has set the killbit on its ActiveX controls. Setting the killbit ensures that ActiveX controls cannot run in Internet Explorer (IE), and avoids security issues involving ActiveX controls in IE.
See the KB 240797 from Microsoft and the related references on this topic.
Security vulnerabilities have been reported for ActiveX controls provided by VMware when run in IE. Under specific circumstances, exploitation of these ActiveX controls might result in denial-of-service or can allow running of arbitrary code when the user browses a malicious Web site or opens a malicious file in IE browser. An attempt to run unsafe ActiveX controls in IE might result in pop-up windows warning the user.
IE can be configured to run unsafe ActiveX controls without prompting. VMware recommends that you retain the default settings in IE, which prompts when unsafe actions are requested.
Earlier, VMware had issued knowledge base articles, KB 5965318 and KB 9078920 on security issues with ActiveX controls.
To avoid malicious scripts that exploit ActiveX controls, do not enable unsafe ActiveX objects in your browser settings. As a best practice, do not browse untrusted Web sites as an administrator and do not click OK or Yes if prompted by IE to allow certain actions.
The Common Vulnerabilities and Exposures project has assigned the names CVE-2008-3691, CVE-2008-3692, CVE-2008-3693, CVE-2008-3695, CVE-2007-5438, and CVE-2008-3696 to the security issues with VMware ActiveX controls.
Security Fix for Local Privilege Escalation on Host System
This release fixes a privilege escalation vulnerability in host operating systems. Exploitation of this vulnerability allows users to run arbitrary code on the host system with elevated privileges.
The Common Vulnerabilities and Exposures project has assigned the name CVE-2008-3698 to this issue.
Update to Freetype
FreeType 2.3.6 resolves an integer overflow vulnerability and other vulnerabilities that can allow malicious users to run arbitrary code or might cause a denial-of-service after reading a maliciously crafted file. This release updates FreeType to its latest version 2.3.7.
The Common Vulnerabilities and Exposures project has assigned the names CVE-2008-1806,
CVE-2008-1807, and CVE-2008-1808 to the issues resolved in Freetype 2.3.6.
VMware Server 1.0.6
Server 1.0.6 resolves the following issues:
- Virtual machines fail unexpectedly after a Symantec virus definition update from version 213 to version 220.
- Previous versions of VMware Server allowed using the VIX API from the guest operating system. With VMware Server 1.0.6, this is no longer allowed by default. This feature can be enabled in VMware Server 1.0.6 by setting a new parameter in the configuration (.vmx) file: vix.inGuest.enable="TRUE"
VMware Server 1.0.5
Server 1.0.5 addresses the following security issues:
- A security vulnerability in OpenSSL 0.9.7j might make it possible to forge an RSA key signature. VMware Server 1.0.5 upgrades OpenSSL to version 0.9.7l to avoid this vulnerability.
RSA Signature Forgery (CVE-2006-4339)
- An internal security audit determined that a malicious user might attain Local System privileges. The user might make the authd process connect to a named pipe that is opened and controlled by this malicious user. In this situation, the malicious user might successfully impersonate authd and attain privileges under which authd is running.
- An internal security audit determined that a malicious user might exploit a non-secure pipe object to escalate privileges or create a denial-of-service attack.
- This release updates the libpng library version to 1.2.22 to remove various security vulnerabilities.
- A vulnerability in VMware Workstation running on Windows allowed complete access to the host's file system from a guest machine. This access included the ability to create and modify executable files in sensitive locations.
- The authd process read and honored the vmx.fullpath variable in the user-writable file config.ini, creating a security vulnerability.
- The config.ini file can be modified by non-administrator to change the VMX launch path. This creates a vulnerability that can be exploited to escalate a user's privileges.
VMware Server 1.0.4
Server 1.0.4 resolves the following issues:
- In previous releases, when a virtual machine configuration (.vmx) file contained the line serialX.HardwareFlowControl="TRUE", the modem-control signals were not handled properly. In this release, modem-control signals are strictly passed through between the virtual and the physical serial port.
- This release fixes an issue that caused Fedora Core 7 to fail with an assert when issuing SCSI commands that have illegal targets. This issue is not clearly exploitable by a normal user.
- This release fixes an issue that might cause Linux virtual machines with VMI-enabled kernels to run very slowly after being rebooted repeatedly.
- This release fixes an issue that might cause a virtual machine to fail at power on when using a sound card with more than two mixer channels on a Windows 32-bit host.
- This release fixes an issue that might cause a 64-bit Solaris 10 virtual machine to fail at power on after being updated with Solaris Update Patch 125038-04.
- This release fixes an issue that results from a conflict between Linux guest operating systems with kernel version 2.6.21 and RTC-related processes on the host. This issue causes the virtual machine to stop unexpectedly.
- This release fixes an issue that caused the hostd to quit unexpectedly in virtual machines with a corrupted snapshot.
- This release fixes an issue that prevented virtual machines running Fedora Core 7 from properly recognizing LSI Logic SCSI devices.
- This release fixes an issue that prevented the VMware vmmon module from being built correctly on hosts running Linux with kernel version 2.6.20-rc1.
- This release fixes an issue that prevented the VMware vmnet module from building correctly on hosts running Linux with kernel versions higher than 2.6.21.
- This release fixes an issue that might corrupt the guest's memory on hosts running Linux with kernel versions higher than 2.6.21.
- When a user attempts to access a virtual machine through the Windows remote VMware Service Console, and the user does not have write permission on the virtual machine configuration (.vmx) file, the display is blank with no indication of the actual issue. This release displays an error message to advise the user that access to write is required to connect to the virtual machine with the VMware Service Console.
- This release fixes an issue with virtual machines running Red Hat Linux 7.1, kernel version 2.4.2. This issue causes the guest operating system to stop responding during the installation of VMware Tools, after the user selects the default display size.
- This release fixes an issue that prevented VMware Player from launching. This issue was accompanied by the error message VMware Player unrecoverable error: (player) Exception 0xc0000005 (access violation) has occurred. This issue might result in a security vulnerability from some images stored in virtual machines downloaded by the user.
Server 1.0.4 resolves the following security issues:
- This release fixes a security vulnerability that might allow a guest operating system user with administrative privileges to cause memory corruption in a host process, and thus potentially run arbitrary code on the host. The Common Vulnerabilities and Exposures assigned the following name to this issue: CVE-2007-4496.
Thanks to Rafal Wojtczvk of McAfee for identifying and reporting this issue.
- This release fixes a security vulnerability that might allow a guest operating system user without administrator privileges to cause a host process to stop responding or exit unexpectedly, making the guest operating system unusable. The Common Vulnerabilities and Exposures assigned the following name to this issue: CVE-2007-4497.
Thanks to Rafal Wojtczvk of McAfee for identifying and reporting this issue.
- This release fixes several security vulnerabilities in the VMware DHCP server that might enable a malicious Web page to gain system-level privileges.
The Common Vulnerabilities and Exposures assigned the following names to these issues: CVE-2007-0061, CVE-2007-0062, and CVE-2007-0063.
Thanks to Neel Mehta and Ryan Smith of the IBM Internet Security Systems X-Force for discovering and researching these vulnerabilities.
- This release fixes a security vulnerability that might allow a malicious remote user to exploit the library file IntraProcessLogging.dll to overwrite files in a system.
The Common Vulnerabilities and Exposures assigned the following name to this issue: CVE-2007-4059.
Thanks to the Goodfellas Security Research Team for discovering and researching these vulnerabilities.
- This release fixes a security vulnerability that might allow a malicious remote user to exploit the library file vielib.dll to overwrite files in a system.
The Common Vulnerabilities and Exposures assigned the following names to this issue: CVE-2007-4155.
Thanks to the Goodfellas Security Research Team for discovering and researching these vulnerabilities.
- This release fixes a security vulnerability in which VMware
Server was starting registered Windows services such as the Authorization service with bare (unquoted) paths, such as c:\program files\vmware\.... Applications and services in Windows must be started with a quoted path. This vulnerability might allow a malicious user to escalate user privileges.
Thanks to Foundstone for discovering this vulnerability.
- This release fixes an issue that might cause user passwords to be printed in clear text in some VMware Server logs.
VMware Server 1.0.3
Server 1.0.3 resolves the following issues:
- This release fixes an issue with VMware Tools that caused the guest to run out of memory.
- VMware Server 1.0.3 fixes a bug introduced in the VMware Server version 1.0.2 VIX API. As a result of this bug, if Vix_ReleaseHandle (vmhandle) and VixHost_Disconnect (hosthandle) are called, a failure occurs in (VixHost_Disconnect). This failure is accompanied by the following error message:
VMware Server Error:
VMware Server unrecoverable error: (app)
ASSERT /build/mts/release/bora-39867/pompeii2005/bora/lib/vmdb/vmdbCtx.c:487 bugNr=23952
A log file is available in /tmp/vmware-mark/vix-3749.log. Please request support and include the contents of the log file.
To collect files to submit to VMware support, run vm-support.
The support will respond on the basis of your support entitlement.
- Virtual machines can be put in various states of suspension, as specified by the ACPI power management standard. When returning from a sleep state (S2) to the run state (S0), the virtual machine process (VMX) collects information about the last recorded running state for the virtual machine. Under some circumstances, VMX read state information from an incorrect memory location. This issue might be used to cause a successful denial-of-service attack where the virtual machine must be rebooted.
The Common Vulnerabilities and Exposures assigned the name CVE- 2007-1337 to this issue.
Thanks to Tavis Ormandy of Google for identifying this issue.
- Some VMware products support storing configuration information in VMware system files. Under some circumstances, a malicious user might instruct the virtual machine process (VMX) to store malformed data, causing an error. This error might enable a successful denial-of-service attack on guest operating systems.
The Common Vulnerabilities and Exposures assigned the name CVE-2007-1877 to this issue.
Thanks to Sungard Ixsecurity for identifying this issue.
- Some VMware products manage memory in a way that fails to gracefully handle some general protection faults (GPF) in Windows guest operating systems. A malicious user might use this vulnerability to stop Windows virtual machines. While this vulnerability might allow an attacker to stop a virtual machine, it is possible to escalate privileges or escape virtual containment.
The Common Vulnerabilities and Exposures assigned the name CVE-2007-1069 to this issue.
Thanks to Ruben Santamarta of Reversemode for identifying this issue.
- In a 64-bit Windows guest on a 64-bit host, debugging local programs can create system instability. Using a debugger to step into a syscall instruction might corrupt the virtual machine's register context. This corruption produces unpredictable results, including corrupted stack pointers, kernel bugchecks, or VMX process failures.
The Common Vulnerabilities and Exposures assigned the name CVE-2007-1876 to this issue.
Thanks to Ken Johnson for identifying this issue.
VMware Server 1.0.2
Server 1.0.2 resolves the following issues:
- This release fixes certain memory leaks in VMware Tools on Windows guests.
- This release enhances the vm-support script capability. The vm-support script that collects log files and other system information, in this release, collects the bootloader configuration file.
- This release includes improved support for Intel family F processors.
- This release includes support for Intel Rockton processors.
- This release fixes a bug, which under rare conditions, caused a failure when many virtual machines were booting under a heavy load.
- This release includes prebuilt modules for VMware Tools for SUSE SLES 10.
- This release fixes a bug, which sometimes caused an assertion failure when calling VixVM_Open on an unregistered virtual machine.
- Starting with this release, guest.commands.allowAnonRootGuestCommandsOnHost and guest.commands.allowAnonRootGuestCommands settings cannot be included in the .vmx file. To apply the settings to all virtual machines on
the host, you must include these settings in the global configuration file $LIBDIR/settings or CommonAppData\settings.ini.
- Kernel modules in this release build on 2.6.18 kernels and Debian's 2.6.17 kernels.
- HGFS in this release builds on 2.6.18-rc1 kernels.
- This release fixes a bug that occasionally caused a failure when uninstalling VMware Server just after resuming a Windows host system.
- This release fixes a bug that occasionally causes failure in 64-bit Windows Server 2003 Enterprise Edition hosts with SP1.
- This release fixes a bug that occasionally causes direct-execution errors in virtual 8086 (VM86) mode when running 16-bit DOS applications in a Windows guest. This release prevents direct execution errors that are caused by the sysenter instruction being improperly handled, and thus enables DOS applications to run properly.
- In this release, CD-ROM and DVD-ROM emulation work correctly in Vista guests.
- In this release, Vmnet compilation works correctly for bridged networking on 2.6.18 or higher kernels.
- This release fixes a bug, which under rare conditions, caused guest memory to become corrupted.
- Second and subsequent snapshots no longer contain the absolute path to the base .vmdk file. This release allows the virtual machine to be moved to another machine.
- This release fixes a bug, which under rare conditions, caused a system panic with Sun Fire 4100 hardware on a Red Hat 4 64-bit guest.
- This release fixes a bug that occasionally caused Windows guests with dual vmxnet adapters to lose network connectivity.
- This release fixes a bug that occasionally caused a core dump when opening and powering on a FreeBSD 6.0 guest and invoking VMware Tools.
- VMware Server 1.0.2 correctly uses 2-CPU licenses instead of 8-CPU licenses on quad core machines.
- This release fixes a bug that occasionally caused Red Hat Enterprise Linux 3 U5 virtual machines to stop responding.
- This release fixes a security issue that might allow a malicious user to stop Windows guest operating systems. The Common Vulnerabilities and Exposures project has assigned the name CVE-2007-1069 to this issue. Rubén Santamarta of Reversemode discovered a vulnerability in the way that VMware delivered general protection faults (GPF) to Windows guest operating systems, which is fixed in this release.
- This release fixes a security issue with the configuration program vmware-config, which might set incorrect permissions and umask on SSL key files. Local users might have been able to obtain access to the SSL key files. The Common Vulnerabilities and Exposures project has assigned the name CVE-2006-3589 to this issue.
Note: The affected files include /usr/bin/vmware-config.pl and /usr/bin/vmware-config-mui.pl.
- RunProgramInGuest was performed as system process in Windows guests. In this release, it functions as the user process running it with that user's permissions.
VMware Server 1.0.1
Server 1.0.1 resolves the following issues:
- Performance issue on 64-bit Windows hosts with Intel EM64T processors.
- Rare Windows host system failure that might occur on a system with SMP virtual machines, or during heavy network traffic, or after long periods of continuous operation.
- Ctrl+T opens the Virtual Network Editor.
Knowledge Base Articles
If you encounter any of the issues below, click the appropriate link or go to the VMware Knowledge Base and enter the article number as your search item.
Scripting API Known Issues
Use 32-bit VMware VmCOM API on 64-bit Microsoft Windows guest operating system (KB 2018)
Programming API Known Issues
For information on known issues for the VMware Programming API, refer the Programming API 1.0 Release Notes.
References to Other Documentation