VMware

 

VMware Player 3.1.2 Release Notes

VMware Player Version 3.1.2 | 23 SEP 2010 | Build 301548

Last Document Update: 23 SEP 2010

Check frequently for additions and updates to these release notes.

These release notes cover the following topics:

What's New

VMware Player 3.1.2 is a maintenance release that resolves security as well as some known issues.

Prior Releases of VMware Player

New features from prior releases of VMware Player are described in the release notes for each release, along with existing known issues. To view release notes for the prior release of VMware Player, see VMware Player 3.1.1 and VMware Player 3.1 .

Top of Page

Known Issues

The known issues for VMware Player are grouped by topic in the following sections.

Software Updates

The known issues under this section is only applicable when upgrading from the VMware Player 3.1 release candidate to the current VMware Player 3.1 release.
  • Upgrading VMware Player on non-English versions of Windows Vista and Windows 7 hosts might cause the vmUpdateLauncher.exe program to fail and trigger high CPU and memory usage.
    Workaround: In the %PROGRAMFILES%\VMware\VMware Player directory, replace the vmUpdateLauncher.exe file with the one available on VMware Communities.

Installation, Upgrade, and Compatibility

  • The WDDM graphics driver included in the VMware Player 3.1 release is not compatible with VMware Player 3.0 and earlier releases. To run a virtual machine in an older version of VMware Player, revert to the previous version of the WDDM driver.
    Workaround: Uninstall the current version of VMware Tools and install the previously released version.
  • On Windows hosts, if VMware applications or virtual machines are running under a different user, then the current user might not be able to upgrade VMware Player concurrently.
    Workaround: To upgrade VMware Player, complete the following steps:
    1. Open Windows Task Manager.
    2. Verify that VMware applications or virtual machines are running under a different user.
    3. Switch to that user.
    4. Close all VMware applications and virtual machines.
    5. Switch back and upgrade VMware Player.
    If you do not have the proper permission to switch, contact your system administrator.
  • On Linux hosts, changes to the System proxy settings and Manual proxy settings might take effect after you restart VMware Player.
  • On Windows Server 2008 hosts, if you are not logged in as an Administrative user or your group policy disallows .msi installers, VMware Player and VMware Tools update might fail.
  • In some instances, using Easy Install to create a virtual machine with Kubuntu 10.04 might result in a blank screen after the virtual machine restarts for the first time.
    Workaround: Restart the virtual machine.
  • Installing the Linux version of VMware Player in a directory where the path contains spaces, might cause the OVF Tool to launch incorrectly.
    Workaround: To launch the OVF Tool, implement one of the following workarounds:
    • Install the Linux version of VMware Player in a directory path without spaces.
    • Edit line 23 of the ovftool script to contain the following command: "$OVFTOOL_BIN" "$@".
  • On SUSE 11.2 and possibly other Linux distributions, the sudo command does not preserve the DISPLAY environment, which could cause the VMware Player installer user interface to fail.
    Workaround: To preserve the DISPLAY environment add Defaults env_keep+="DISPLAY" to the /etc/sudoers file.
  • Installing VMware Player in a directory path that contains non-ASCII characters might cause an unsuccessful installation or cause guest application shortcuts to become unresponsive when you try to open them.
    Workaround: Install VMware Player in a directory path containing only ASCII characters.

Top of Page

Display

  • In some cases, entering Unity mode on Windows 7 virtual machines with Aero configured to use more than two monitors could disable migration of Unity windows between monitors.
    Workaround: Exit and reenter Unity mode.
  • Exiting FIFA 08 game on Windows 7 guests and hosts with Aero enabled, might cause the desktop wallpaper to turn black.
  • Running OpenGL applications using full screen view across multiple displays on a Windows XP virtual machine might fail.
  • There are known issues with the ATI Linux driver 10.2. VMware recommends that you use ATI Linux driver 9.11 for the best 3D user experience.
  • On Fedora 13 and Red Hat Enterprise Linux 6 virtual machines, Unity mode might not support maximizing virtual machine application windows.
  • When running Left 4 Dead application, transitioning the virtual machine between console view and full screen mode, might cause the application to display incorrectly.
    Workaround: Restart the application to restore display.

Miscellaneous

  • Running a virtual machine on a Linux host with grsecurity patches might cause the host to restart unexpectedly.
  • Running a script event as root to suspend Fedora 13 or Red Hat Enterprise Linux 6 Beta 2 guest operating systems might not suspend the guests.
    Workaround: To suspend the Fedora 13 guest, apply a policy file greater than selinux-policy-3.7.19-57.fc13.
  • Attempting to restore a virtual machine snapshot on a host with Diskeeper 2010 installed might fail.
    Workaround: Upgrade to Diskeeper 2010 version 14.0.898.0 or later.
  • On Ubuntu 10.04 hosts, powering on a virtual machine with ThinPrint enabled might fail with the error message "thnuclnt: relocation error: /lib/tls/i686/cmov/libnss_files.so.2: symbol strcmp, version GLIBC_2.0 not defined in file libc.so.6 with link time reference".
  • Using fast user switching might cause unpredictable behavior in the Windows virtual machine, including problems with the mouse and with CPU usage.
    Workaround: Allow the Windows guest operating system to start and reach an idle state before you log in to the first user account.
  • Printer device might not work on Ubuntu 10.04 hosts.
    Workaround: Manually configure the network or USB printer to print from the virtual machine.
  • Converter does not support virtual disk size that exceeds 950GB.
    Workaround: Change the disk size value to 950GB.

Top of Page

Resolved Issues

The following sections list the resolved issues in VMware Player 3.1.2.

Security Fixes

  • VMware Player 3.x addresses an installer security issue
    The VMware Player 3.x installer loads an index.htm file located in the current working directory on which VMware Player 3.x is being installed. This might enable attackers to display a malicious file if they manage to get their file onto the system prior to installation.

    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3277 to this issue.
  • Third party libpng updated to version 1.2.44
    A buffer overflow condition in libpng is addressed that could potentially lead to code execution with the privileges of the application using libpng. Two potential denial of service issues are also addressed in the update.

    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-1205, CVE-2010-0205, and CVE-2010-2249 to these issues.

Installation, Upgrade, and Compatibility

  • In some cases copying an index.html file into the same directory as the VMware Player 3.1.1 installer executable on Windows hosts might cause the VMware Player installer user interface to fail.
  • On Linux hosts, if the screen saver becomes active during the VMware Player software update process, the update might fail.
  • When downloading software updates via a slow Internet connection, you might receive a timeout error resulting in an unsuccessful download.
  • Currently available pre-release versions of OpenSUSE 11.3 might not work properly with Easy Install.

Display

  • To improve user experience when using Unity mode on Windows Vista and Windows 7 virtual machines, VMware Player disables Aero when entering Unity mode and re-enables it when you exit Unity mode. To override the disabling of Aero, open the vmx configuration file and add unity.allowCompositingInGuest="TRUE".
  • Rebooting an Ubuntu 10.04 host after installing VMware Player, might cause the System Tools option under the Application menu to disappear.
  • On Linux hosts, the Cycle to Next/Previous open VM button might not appear consistently in the VMware Player full screen toolbar.
  • Attempting to power on a Windows 7 virtual machine named using non-ASCII characters on Ubuntu 10.04 hosts might cause display issues in the Unity mode Start menu.
  • Enabling Aero on hosts with Intel Integrated Graphics processing unit might cause display issues in a virtual machine.
  • On Windows hosts, you might experience some usability issues while attempting to interact with Fedora 13 virtual machine applications in Unity mode.
  • On Fedora 13 virtual machines, dragging guest applications along the edges of the guest display might cause the mouse functions to become unresponsive.
  • On Japanese version of Windows, using non-ASCII characters to name the host might cause the Start menu to not show in Unity mode.

Miscellaneous

  • The DNS server information might not refresh when the virtual machine switches between multiple NICs, such as wired and wireless. Thus, leading to a failure in looking up hosts with their DNS names when the guest is using NAT.
  • If your host system has three parallel ports you might not be able map them non-sequentially.
  • On Ubuntu guests, the vmware-user component of VMware Tools might become unresponsive after Autologon is enabled on the guest and cause the drag and drop or copy and paste operations to fail.
  • USB devices with vendor ID 0x1366 might be identified as being manufactured by Asahi KASEI instead of SEGGER.
  • Dragon Medical 10.1 from Nuance might not run with more than one core on Windows 7 Ultimate 64-bit guests.
  • On Windows 7 guests, you must run a New Hardware scan from the Device Manager menu for Logitech USB audio devices to be recognized. USB devices disconnected from the guest might still appear to be connected in the guest, and the guest might not allow you to reconnect them.
  • On some Windows guests, the volume control keys and a few other multimedia keys might not work in a virtual machine.
  • Error that occurs in NetBIOS forwarding in NAT leads to an incorrect resolution of the virtual machine WINS name.
  • On Linux hosts, launching a virtual machine application shortcut that includes either non-ASCII characters or a long path might not work on the first attempt.
  • Top of Page