\nVMware Player 3.1 Build 261024 Final + Serial
\nVMware Server 2.0.2 Build 203138 Final + Serial
\nVMware VIX API 1.9 Build 261024 Final + Serial
\nVMware Workstation 7.1 Build 261024 Final + Serial
\nVMware Workstation 7.1.2 is a maintenance release that includes the following new features, adds support for newly released operating systems, addresses customer reported problems, and resolves security issues.
\n•Added Microsoft Visual Studio 2010 support for Integrated Virtual Debugger´s live debugging mode.
\n•Addressed issues that occur when running Windows 7 SP1 Beta, RHEL 6.0 Beta, and Fedora 13 in a virtual machine. Each of these operating system versions are in the development phase. They have known issues and are not fully supported in this release.
\n•NAT networking includes several performance improvements.
\n•VMware Workstation 7.1.2 has been tested with the new free standalone VMware vCenter Converter 4.3. VMware vCenter Converter allows you to convert a single machine or an entire datacenter into virtual machines and supports Windows 7. To download VMware vCenter Converter, see https://www.vmware.com/tryvmware/?p=converter.
\n•Easy Install now supports older versions of the CentOS operating system.
\n•Added Windows 2008R2 and Apache Server 2.2.15 support for ACE Management Server.
\nPrior Releases of Workstation
\nNew features from prior releases of VMware Workstation are described in the release notes for each release, along with existing known issues. To view release notes for the prior releases of VMware Workstation, see VMware Workstation 7.1.1 and VMware Workstation 7.1.
\nTop of Page
\nThe known issues for VMware Workstation are grouped by topic in the following sections.
\n•Installation, Upgrade, and Compatibility
\n•Integrated Virtual Debuggers
\nThe known issue under this section is only applicable when upgrading from the VMware Workstation 7.1 release candidate to the current VMware Workstation 7.1 release.
\n•Upgrading VMware Workstation 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.
\nWorkaround: In the %PROGRAMFILES%\\VMware\\VMware Workstation directory, replace the vmUpdateLauncher.exe file with the one available on VMware Communities.
\nInstallation, Upgrade, and Compatibility
\n•The WDDM graphics driver included in the VMware Workstation 7.1 release is not compatible with VMware Workstation 7.0 and earlier releases. To run a virtual machine in an older version of VMware Workstation, revert to the previous version of the WDDM driver.
\nWorkaround: Uninstall the current version of VMware Tools and install the previously released version.
\n•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 Workstation concurrently.
\nWorkaround: To upgrade VMware Workstation, complete the following steps:
\n1.Open Windows Task Manager.
\n2.Verify that VMware applications or virtual machines are running under a different user.
\n3.Switch to that user.
\n4.Close all VMware applications and virtual machines.
\n5.Switch back and upgrade VMware Workstation.
\nIf you do not have the proper permission to switch, contact your system administrator.
\n•On Linux hosts, changes to the System proxy settings and Manual proxy settings might take effect after you restart VMware Workstation.
\n•On Windows Server 2008 hosts, if you are not logged in as an Administrative user or your group policy disallows .msi installers, VMware Workstation and VMware Tools update might fail.
\n•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.
\nWorkaround: Restart the virtual machine.
\n•Installing the Linux version of VMware Workstation in a directory where the path contains spaces, might cause the OVF Tool to launch incorrectly.
\nWorkaround: To launch the OVF Tool, implement one of the following workarounds:
\n?Install the Linux version of VMware Workstation in a directory path without spaces.
\n?Edit line 23 of the ovftool script to contain the following command: \"$OVFTOOL_BIN\" \"$@\".
\n•On SUSE 11.2 and possibly other Linux distributions, the sudo command does not preserve the DISPLAY environment, which could cause the VMware Workstation installer user interface to fail.
\nWorkaround: To preserve the DISPLAY environment add Defaults env_keep+=\"DISPLAY\" to the /etc/sudoers file.
\n•Installing VMware Workstation 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.
\nWorkaround: Install VMware Workstation in a directory path containing only ASCII characters.
\nTop of Page
\n•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.
\nWorkaround: Exit and reenter Unity mode.
\n•Exiting FIFA 08 game on Windows 7 guests and hosts with Aero enabled, might cause the desktop wallpaper to turn black.
\n•Running OpenGL applications using full screen view across multiple displays on a Windows XP virtual machine might fail.
\n•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.
\n•On Fedora 13 and Red Hat Enterprise Linux 6 virtual machines, Unity mode might not support maximizing virtual machine application windows.
\n•When running Left 4 Dead application, transitioning the virtual machine between console view and full screen mode, might cause the application to display incorrectly.
\nWorkaround: Restart the application to restore display.
\nIntegrated Virtual Debuggers
\n•When you restart an Integrated Virtual Debugger live debugging session for a Visual Basic project in a virtual machine using Microsoft Visual Studio 2008 or 2010, the Remote Debug Monitor instance might become unresponsive.
\nWorkaround: In Microsoft Visual Studio 2008, manually stop the msvsmon.exe process in the guest. When a prompt appears to confirm whether you want to use the existing Remote Debug Monitor instance, select No and continue with the live debugging session. For Microsoft Visual Studio 2010, restart the Visual Studio 2010 program.
\n•On Ubuntu 10.04 hosts, debugging with the Eclipse C/C++ Remote Debugging plug-in might fail with the error message \"/usr/bin/xterm: can\'t execvp /mnt/hgfs/gdbserverDirectory/gdbserver: Protocol error\".
\n•Live debugging mode does not work on encrypted virtual machines.
\n•Running a virtual machine on a Linux host with grsecurity patches might cause the host to restart unexpectedly.
\n•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.
\nWorkaround: To suspend the Fedora 13 guest, apply a policy file greater than selinux-policy-3.7.19-57.fc13.
\n•Attempting to restore a virtual machine snapshot on a host with Diskeeper 2010 installed might fail.
\nWorkaround: Upgrade to Diskeeper 2010 version 14.0.898.0 or later.
\n•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\".
\n•Using fast user switching might cause unpredictable behavior in the Windows virtual machine, including problems with the mouse and with CPU usage.
\nWorkaround: Allow the Windows guest operating system to start and reach an idle state before you log in to the first user account.
\n•Printer device might not work on Ubuntu 10.04 hosts.
\nWorkaround: Manually configure the network or USB printer to print from the virtual machine.
\n•Converter does not support virtual disk size that exceeds 950GB.
\nWorkaround: Change the disk size value to 950GB.
\n•Record/replay might not function properly if the virtual machine has a serial port configured to serial<port_number>.fileType = thinprint setting.
\nTop of Page
\nThe following sections list the resolved issues in VMware Workstation 7.1.2.
\n•VMware Workstation 7.1.2 addresses an installer security issue
\nThe VMware Workstation 7.x installer loads an index.htm file located in the current working directory on which VMware Workstation 7.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.
\nThe Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3277 to this issue.
\n•Third party libpng updated to version 1.2.44
\nA 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.
\nThe 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.
\nInstallation, Upgrade, and Compatibility
\n•In some cases copying an index.htm file into the same directory as the VMware Workstation 7.1.1 installer executable on Windows hosts might cause the VMware Workstation installer user interface to fail.
\n•On Linux hosts, if the screen saver becomes active during the VMware Workstation software update process, the update might fail.
\n•When downloading software updates via a slow Internet connection, you might receive a timeout error resulting in an unsuccessful download.
\n•Currently available pre-release versions of OpenSUSE 11.3 might not work properly with Easy Install.Display
\n•To improve user experience when using Unity mode on Windows Vista and Windows 7 virtual machines, VMware Workstation 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\".
\n•Rebooting an Ubuntu 10.04 host after installing VMware Workstation, might cause the System Tools option under the Application menu to disappear.
\n•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.
\n•Enabling Aero on hosts with Intel Integrated Graphics processing unit might cause display issues in a virtual machine.
\n•On Windows hosts, you might experience some usability issues while attempting to interact with Fedora 13 virtual machine applications in Unity mode.
\n•On Fedora 13 virtual machines, dragging guest applications along the edges of the guest display might cause the mouse functions to become unresponsive.
\n•In some instances, virtual machines suspended in VMware Workstation 7.x might not resume in Workstation 6.0 or earlier versions.
\n•On Japanese version of Windows, using non-ASCII characters to name the host might cause the Start menu to not show in Unity mode.
\n•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.
\n•If your host system has three parallel ports you might not be able map them non-sequentially.
\n•On Ubuntu guests, the vmware-user component of VMware Tools might become unresponsive after Autologon is enabled on the guest and cause drag and drop or copy and paste operations to fail.
\n•USB devices with vendor ID 0x1366 might be identified as being manufactured by Asahi KASEI instead of SEGGER.
\n•Pressing the Ctrl+Alt+Enter keys on an ACE virtual machine running in kiosk mode might cause the keyboard to become unresponsive.
\n•PCI devices cannot be added back into encrypted ACE virtual machines if removed accidentally by non-ACE Administrators. To fix this issue, only ACE Administrators can add or remove PCI devices to ACE virtual machines after entering the Admin mode password.
\n•Dragon Medical 10.1 from Nuance might not run with more than one core on Windows 7 Ultimate 64-bit guests.
\n•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.
\n•On some Windows guests, the volume control keys and a few other multimedia keys might not work in a virtual machine.
\n•Error that occurs in NetBIOS forwarding in NAT leads to an incorrect resolution of the virtual machine WINS name.
\n•Recording or replaying some 3D applications with record/replay might cause memory allocation failures.
\n•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.