VMware Workstation 6.5.2 Release Notes

Workstation Version 6.5.2 | 31 March 2009 | Build 156735

Document last updated: April 13, 2009

These release notes cover the following topics:

What's New

Workstation 6.5.2 is a maintenance release that resolves security as well as some known issues. With this release of VMware Workstation, certain new features and support have been added.

Support for New Guest Operating Systems

VMware provides support for the following operating systems for Workstation 6.5.2:

  • Windows Vista Service Pack 1 and Service Pack 2
  • Asianux Server 3.0 Service Pack 1
  • openSUSE 11.1
  • Ubuntu 8.10
  • Ubuntu 8.04 LTS
VMware provides experimental support to the following operating systems for Workstation:
  • Fedora 11
  • FreeBSD 7.1
  • Mandriva Linux 2009
  • Novell SLE11.0
  • Red Hat Enterprise Linux 5.3
  • Red Hat Enterprise Linux 4.8
  • Sun Solaris 10 Update 6
  • Ubuntu 9.04

Refer the Guest Operating System Installation Guide for more information on the support for operating systems.

Support for Intel Microarchitecture (Nehalem)

VMware provides support for Nehalem processors (Intel Microarchitecture) from this release.

Top of Page

Prior Releases of Workstation

Features from the prior releases of VMware Workstation are described in the following Release Notes documents:

Top of Page


Known Issues

The known issues are grouped as follows:

Localization and Internationalization

  • On Linux hosts, if you open a Workstation 5.x or 6.0.x virtual machine that has Japanese characters in the .vmx file name, Workstation 6.5 might exit unexpectedly. Note that newly created virtual machines in Workstation 6.5 usually transfer correctly between Workstation 6.5 Windows and Linux and Mac-Fusion 2.0 hosts when international characters are present. The issue with incorrect transfer occurs only with older virtual machines, created with previous versions of Workstation.
  • If you create a virtual machine on a host with an English locale and then try to open that virtual machine on a Japanese host where the path to the Workstation installation directory contains certain Japanese hanzi characters or other characters that are not in the local encoding (that is, not Japanese), you might not be able to open the virtual machine.
  • If a virtual machine's configuration file (.vmx file) contains characters outside of the ASCII character set and you want to use Workstation 6.5 to open a virtual machine that was created with an older version of another VMware product, such as VMware Fusion 1.1, you must first open the virtual machine with a new version of that other VMware product. For example, open a Fusion 1.1 virtual machine with Fusion 2.0 and then you will be able to open it with Workstation 6.5.

Workstation and Virtual Machine Installation, Upgrade, and Compatibility

  • On Windows hosts, attempts to upgrade from Workstation 6.x to 6.5.x or to uninstall Workstation 6.5.x might fail.
    Workarounds: Try to manually uninstall Workstation a second time. On Windows Vista hosts, temporarily disable UAC and run the upgrade or uninstallation again.
  • On Linux hosts that are running a GL-based X server (Xgl), after you install Workstation, you might not be able to power on a virtual machine until you reboot the host.
  • On virtual machines with a Windows 2000 operating system, if the virtual machine is set to automatically update VMware Tools, the virtual machine is not restarted after the update. You must manually restart the virtual machine to complete the update and start VMware Tools.
  • If you use Avira AntiVir antivirus software on a Windows Vista host, you might have problems running virtual machines.

Smart Cards and Smart Card Readers (Experimental Support)

  • On Windows XP hosts and perhaps other hosts, you might be locked out of the host if you remove a smart card from its reader in order to insert it for logging in to a virtual machine. To avoid this problem, configure the host's smart card removal behavior so that no action is taken when the smart card is removed.
  • If you upgrade from Workstation 6.0.x, or an earlier 6.5 beta release, you might have difficulties logging in to a domain using a smart card. For example, you might see an error such as, The system could not log you on. Your credentials could not be verified.
  • Smart cards that have been tested include ActivIdentity, Gemalto, and Oberthur, including DoD CAC type cards. Smart card readers that have been tested include:
    • Readers with USB interfaces: ActivIdentity USB V2 , Gemplus USB-SW, SCM-SCR-331, HP USB Smartcard Keyboard KUS0133, Advance Card System ACR30, Litronic 215
    • Readers with serial interfaces: Gemplus American Express GCR415, SCM-SCR-131
    • Readers with PCMCIA interfaces: Omnikey CardMan 4040, SCM-SCR-243, Gemplus-PCMCIA
  • Occasionally, a Linux guest might not detect the virtual smart card reader (SCR) due to guest-specific issues even after you successfully connect to the virtual SCR in the Workstation UI

    1. For all Linux guests, update the CCID driver configuration by manually adding the VMware virtual SCR vendor ID, product ID, and friendly name to the /usr/lib/pcsc/drivers/ifd.ccid.bundle/Contents/Info.plist file if they are not present. Add vendor ID 0x0E0F in the ifdVendorID key section, add product ID 0x0004 in the ifdProductID key section, and add VMware Virtual Smart Card Reader in the ifdFriendlyName key section of the Info.plist file.
    2. For Ubuntu 7.10 guests, use a pcscd --hotplug command to force a rescan of the USB bus by pcscd. This resolves a timing problem between udev and libusb in the guest.


  • If you use the TMS GUIMotions plug-in for Borland's Delphi when writing applications that you want to run in virtual machines, the images for 3-D animation are not displayed.
  • If you want to use exclusive mode when running a 3-D game, application, or screen saver, you must first go into full screen mode, then start the 3-D application, and then go into exclusive mode. If you start a 3-D application when you are already in exclusive mode, the virtual machine will go into full screen mode.
  • On some Linux guests, the shut down window does not appear in Unity mode. If you choose System > Quit in a Ubuntu virtual machine while in Unity mode, the shut down window does not appear.
    Workaround: Exit Unity mode, press Tab until the desired button on the shut down window is chosen, and press Enter.
  • On Linux hosts with a Linux guest, you might not be able to use Unity mode to place application windows from different virtual desktops into corresponding virtual desktops on the host. Windows from different virtual desktops on the guest might all be placed in one virtual desktop on the host.
  • On Linux hosts, if you use Unity mode and drag a file from a guest application window to the host, the version of the file on the guest might get moved to the guest's desktop.
  • When you place a virtual machine in Unity mode, Workstation tries to disable the guest screen saver. On some Linux guests, however, the screen saver is not disabled. If a guest's screen saver starts being used when in Unity mode and if you have the guest configured to require authentication to exit the screen saver, you might get locked out of the guest. In such environments, disable the guest screen saver for any Linux virtual machine that will use Unity mode often.
  • To enable use of the Autofit Guest command and the Fit Guest Now command on Windows 95 and Windows 98 guests, you must use the guest's Display Properties settings to change the screen resolution to a higher value than 640 X 480.
  • Turbolinux 10 Server has a problem with switching from XGA (Extended Graphics Array) to VGA (Video Graphics Array) such that the screen becomes black. You encounter this problem at the end of the process of installing the Turbolinux 10 Server operating system. After you click Finish in the installation wizard, the screen becomes black and the system does not reboot.
    Workaround: Manually reboot the guest operating system.
  • Occasionally, on Windows guests, when you try to play a QuickTime video while in full screen mode, you see only a black screen.

Integrated Virtual Debuggers

  • Remote debugging using the Integrated Virtual Debugger for Visual Studio might fail on powered off 32-bit virtual machines.
    Workaround: Power on the virtual machine and start remote debugging mode.
  • On Linux hosts, VMware recommends that you use the bundle installer rather than the RPM installer if you want to use the Integrated Virtual Debugger for Eclipse. The bundle installer gives you the option of specifying the path to Eclipse if the path cannot be found automatically.
  • If a virtual machine is powered off and you use the Integrated Virtual Debugger for Eclipse, you may see the error Guest has only loopback IP address. Ensure that it has a properly configured TCP/IP connection to the host.
    Workaround: Enabled shared folders manually.
  • If you add additional .jar files to the class path of your Eclipse project and launch it inside a Windows virtual machine from within Eclipse then you may not be able to detach and re-attach the Integrated Virtual Debugger for Eclipse from the application.
  • Visual Studio 2005 allows multiple projects to be debugged simultaneously when Start is chosen. However, the Integrated Virtual Debugger for Visual Studio currently supports only one project and one configuration for debugging at any given time. If you select multiple projects as debugging targets, the Integrated Virtual Debugger for Visual Studio only chooses the first one on the list.

Miscellaneous Issues

  • USB TenKey does not work properly on Virtual Machine
    When you are using a USB TenKey numeric keypad with numlock feature and if you enable the Use enhanced virtual keyboard option in the virtual machine, the data entered is corrupted.
    Workaround: Disable Use enhanced virtual keyboard option and Show all USB input devices option.
  • Virtual machine streaming does not work when VMDK file is larger than 2GB
    When the virtual machine disks (VMDK) file of a virtual machine is larger than 2GB, streaming fails on the virtual machine with the following error:
    VMware Player unrecoverable error: (vmx)
    Failed to initialize streaming disks: Http I/O failure after all retry attempts (5)

    This issue is found on Workstation and Player with virtual machines running the following guest operating systems:
    • Ubuntu 8.04 32-bit
    • openSUSE 11.1
    • Windows Vista
    • RHEL 5.2 Server 64-bit
    Workaround: Convert the VMDK file to 2GB sparse or flat files. Alternatively, install a Web server that supports hosting files larger than 2GB.
  • Xserver stops with an error when installing VMware tools on Ubuntu 9.04 virtual machine
    While installing VMware tools on a virtual machine that is running Ubuntu 9.04, the following warning and error messages appear:
    Warning: unable to close filehandle CHILD properly.
    Fatal server error: no screens found;

    After installing VMware Tools and rebooting the virtual machine, Xserver stops working and displays the following error: Ubuntu is running in low-graphics mode.
  • Easy install with CD or DVD fails on Workstation for certain Linux guest operating systems
    Easy-install with a CD or DVD for certain Linux guest operating systems fails on Windows hosts. This issue occurs on the following guest operating systems:
    • Ubuntu 9.04 Desktop 32-bit
    • RHEL 5.3 Server 32-bit
    • RHEL 4.8 AS 32-bit and 64-bit
    • RHEL 4.8 WS 32-bit
    Workaround: Install these guest operating systems using ISO files instead of a CD or DVD on Windows hosts.
  • Replay control dialog box does not open for RHEL 4.8 guest operating system
    When you try to use the Record and Replay feature for virtual machines running RHEL 4.8 as the guest operating system, the replay control dialog box does not appear.
    Workaround: Record and Replay using the Snapshot Manager. To use the Snapshot Manager, select Snapshot > Snapshot Manager from the menu in the virtual machine.
  • Unable to invoke vi editor when using KDE on Mandriva 2009.0
    When you try to edit VMware Tools scripts from vmware-toolbox by using KDE on the Mandriva 2009.0 guest operating system, vi editor cannot be invoked, and the following error appears in the console:
    <unknown program name>:KuniqueApplication: Cannot find the D-Bus session server
    <unknown program name>:KuniqueApplication: Pipe closed unexpectedly.

    • Perform export DBUS_SESSION_BUS_ADDRESS= before invoking vmware-toolbox.
    • Start konsole from the menu and log in as root su - and run vmware-toolbox.
  • Virtual machine in root directory with virtual disk in a subdirectory does not work properly for snapshots
    If a Windows virtual machine is in root directory with virtual disk in a subdirectory, after taking a snapshot, the virtual machine cannot be powered on, cloned, cannot edit the settings, and other operations related to added virtual disk fail.
    Workaround: If a virtual machine is in a root directory, keep all its virtual disks in the same directory or move the virtual machine to a non-root directory.
  • If your host system freezes when you are running a virtual machine and you must force a reboot, you might need to manually remove stale lock files from the virtual machine. When you try to power on the virtual machine, you might receive a message that the virtual machine is locked, and you are prompted to take ownership of the virtual machine. If the attempt to take ownership fails, manually delete the .lck files and restart Workstation before powering on the virtual machine.
  • If you use File > Open or File > Import to convert a virtual machine or system image that contains a Windows NT 3.x, Windows ME, Windows 98, or Windows 95 operating system, you might see the following warning: Cannot configure the source image. You can ignore this message. These operating systems are supported only experimentally. You might need to modify the configuration of the destination virtual machine before using it.
  • Occasionally, when you use File > Import to convert a Symantec backup or Norton Ghost image (.sv2i files) with volume resizing, the operation stops responding.
    Workaround: First, try again. If the issue persists, try again without volume resizing.
  • The File > Open and File > Import commands have several limitations for StorageCraft ShadowStore images (.spf files) and Symantec Backup Exec System Recovery images (.sv2i files). The limitations are:
    1. No support for dynamic disks.
    2. Images relating to the backup of the same machine must be in the same folder, with no other images placed there.
    3. All the volumes in the disk up to the active and system volumes must be backed up. (For example, say there are 4 partitions (1-4) on a disk, and partition 2 is the active volume and partition 3 is the system volume. Volumes 1-3 must be backed up.)
    4. If it is an incremental image, up to 16 incremental backups are supported.
    In addition, for StorageCraft images, there is no support for systems with logical drives if the logical drive is also a system/active volume.

You may also view a list of knowledge base articles related to Workstation 6.5.

Top of Page


Resolved Issues

The following issues are resolved in Workstation 6.5.2:

Security Fixes

  • 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.
  • 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.
  • 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.
  • A VMCI privilege escalation on Windows-based hosts or guests
    Virtual Machine Communication Interface (VMCI) is an infrastructure that provides fast and efficient communication between a virtual machine and the host operating system and between two or more virtual machines on the same host. 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. To correct this vulnerability on Windows-based hosts, see Virtual Machine Communication Interface (VMCI) privilege escalation on Windows-based Workstation, Player, ACE and Server (KB 1009826).
    The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1147 to this issue.
  • VMnc codec heap overflow vulnerabilities
    The VMnc codec assists in record and replay sessions. Record and replay records 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.


  • Creating ACE package fails on Windows virtual machines
    Creating ACE package fails with the error Tools is out of date, on virtual machines running Windows NT, Windows 9x and Windows Millennium Edition. This issue is resolved in this release.
  • Unable to install the latest version of VIX API on Workstation 6.5.0
    On Workstation 6.5.0, you cannot install VMware VIX API 1.6.2 due to an issue with the MSI installer for VIX API. This issue is resolved in this release.
  • Unable to connect to PPTP VPN using VMware NAT on Microsoft Windows guest operating systems
    When you try to open a PPTP VPN connection by using VMware NAT with Microsoft XP Service Pack 2, the following error appears:
    Disconnected. 619 connect to the remote machine could not be established.
    The issue is found on Cisco 1841 VPN and other PPTP VPN connections, and is applicable to all supported versions of Microsoft Windows host machines. This issue is resolved in this release.
  • Workstation displays wrong message after installing the latest version of VMware Tools
    After installing the latest version of VMware Tools and rebooting the guest operating system, Workstation displays the following message on the status bar:
    Your version of VMware Tools is out of date.
    This issue is resolved in this release.
  • Novell SLES 11 Beta is displayed as not supported when installing VMware Tools
    Virtual machines running the Novell SUSE Linux Enterprise Server 11 Beta operating systems as guests display the following warning message while installing VMware Tools:
    WARNING: Cannot determine dependencies of kernel module 'vmxnet'.
    This issue is resolved in this release.
  • vsock fails to load using load-vmware on Linux kernel 2.6.26 and later
    If CONFIG_MODVERSIONS is defined, vsock does not load when you run load-vmware command as the Module.symvers is missing on Linux kernels 2.6.26 and later. This issue is resolved in this release.
  • In Workstation, Google Earth displays extra lines for the country borders
    In Workstation, Google Earth displays extra yellow lines to draw the country borders, when the Direct3D Acceleration option is enabled.
    This issue is resolved in this release.
  • Unable to invoke vi editor from VMware Tools on SLES11 guest operating system
    When you try to edit VMware Tools scripts from vmware-toolbox window on SUSE Linux Enterprise Server 11 (SLES11), the following error appears in the console:
    Cannot edit script because the vi editor was not found
    This issue is resolved in this release.
    To edit vmware-tools scripts:
    1. Launch VMware Tools and select the Scripts tab.
    2. Select Custom script option and click Edit.
  • Only the first attempt succeeds when mapping original and cloned virtual disk files to drive letters
    On Windows hosts, if you make a linked or full clone of a virtual machine and then try to map the virtual disk files of the original virtual machine as well as of the clone to drive letters on the host, only the first mapping succeeds. Because both disks have the same signature, you can map only one of the disks at a time. This issue is resolved in this release.

Knowledge Base Article

This section lists the VMware Knowledge Base article published in this release.

Certain Linux virtual machines do not play sound after installing VMware Tools (KB 1009485)