VMware

 

VMware Player 3.1.1 Release Notes

VMware Player Version 3.1.1 | 12 AUG 2010 | Build 282343

Last Document Update: 12 AUG 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.1 is a maintenance release that resolves some known issues.

Prior Releases of VMware Player

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 .

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 are only applicable when upgrading from VMware Player 3.1 release candidate to the current VMware Player 3.1 release. The following known issues have been fixed in the current release.
  • When you install or uninstall the release candidate version of VMware Player 3.1 on a Windows host, some of the network or USB device drivers might not work properly.
    Workaround: Before you install or uninstall VMware Player, make a list of drivers in the Device Manager. Install or uninstall VMware Player and manually reinstall the network or USB device drivers that are not working or might be missing.
  • 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.
  • On Linux hosts, if the screen saver becomes active during the VMware Player software update process, the update might fail.
    Workaround: Disable your screen saver before initiating the VMware Player software update process.
  • When downloading software updates via a slow Internet connection, you might receive a timeout error resulting in an unsuccessful download.
    Workaround: Download VMware Player 3.1 from the VMware Web site and manually install the product.

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.
  • Currently available pre-release versions of OpenSUSE 11.3 might not work properly with Easy Install.
  • 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

  • On Linux hosts, the Cycle to Next/Previous open VM button might not appear consistently in the VMware Player full screen toolbar.
  • 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 Windows Vista and Windows 7 virtual machines in Unity mode, using the mouse to perform graphic or text editing tasks might result in a delay in rendering the edits.
    Workaround: Disable Aero mode in the virtual machine.
  • 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 and Red Hat Enterprise Linux 6 virtual machines, Unity mode might not support maximizing virtual machine application windows.
  • On Fedora 13 virtual machines, dragging guest applications along the edges of the guest display might cause the mouse functions to become unresponsive.
  • 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.
  • 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

  • Running a virtual machine on a Linux host with grsecurity patches might cause the host to restart unexpectedly.
  • 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.
  • 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

Resolved Issues

VMware Player 3.1.1 release resolves the following issues:
  • In some cases upon starting a virtual machine, the USB arbitration service might fail to start on systems that do not have a device identified as USBFDO-0 and prevent the use of USB devices in the virtual machine. The following error message appears, "Host USB device connections disabled". For this release, the USB arbitration service is updated to start whenever a USB device exists even if no devices meet this criteria.
  • When a host system failure occurs during a virtual machine disk operation, attempting to power on the virtual machine or mount the virtual disk using the VMware Disk Mount utility causes the following error messages to appear, " Cannot open the disk... The specified virtual disk needs repair" and "Error reading volume information. Please select another disk file". There is no data lost during this process. VMware Player 3.1.1 fixes this issue and enables virtual machine operations to resume.
  • Mapping a virtual disk with multiple partitions to a drive on the host machine and enabling write access only succeeds if you are mounting the first partition. This update enables other partitions to be successfully mounted and accessible to the host operating system.