VMware Workstation 7.1.5 Release Notes
These release notes cover the following topics:
VMware Workstation Version 7.1.5 | 04 OCT 2011 | Build 491717
Last Document Update: 05 OCT 2011
Check frequently for additions and updates to these release notes.
VMware Workstation 7.1.5 is a maintenance release that resolves some security issues and known problems. Highlights of VMware Workstation 7.1.5 functionality include:
- Support for Ubuntu 11.04 as a guest operating system
- Resolved customer-reported USB device issues
- Improved virtual printing for Linux guests
- ACE Management Server updates for performance and security
Workstation 7 now also accepts Workstation 8 license keys.
VMware Workstation 7.1.5 is a free update for all VMware Workstation 7 users.
Prior Releases of Workstation
Known problems from prior releases of VMware Workstation are described in the release notes for each release. To view release notes for the prior releases of VMware Workstation, see VMware Workstation 7.1.4, VMware Workstation 7.1.3, VMware Workstation 7.1.2, VMware Workstation 7.1.1, and VMware Workstation 7.1.
The following sections list the resolved issues in VMware Workstation 7.1.5.
Other Resolved Issues
ThinPrint printers might not have been visible in Linux guests. With VMware Workstation 7.1.5, you can use ThinPrint printers to print in Linux guests.
The networking inside the guest did not restore correctly after resuming a suspended virtual machine with an Ubuntu 10.10 or later guest operating system.
In a Windows guest, saving a file using Visual Studio 2008 SP1 on VMware Shared folders failed. Attempting to save the file resulted in the following error:
The operation could not be completed. The process cannot access the file because it is being used by another process.
As a workaround, you could save under another file name, using the Save As option. This sharing violation also resulted in Visual Studio builds failing on Shared Folders.
On a Windows host, if you held down a key in a Unity window, moved the mouse out of the Unity window, and clicked elsewhere in the host, the key press continued repeatedly inside the Unity window.
Occasional data corruption occurred when transferring large amounts of data to USB devices from virtual machines running Windows 7.
After switching between guest consoles in quick switch and full screen modes, motion grab was disabled and an extra click was required to get back into the virtual machine.
Some USB mobile network cards were not recognized by the host when the VMware USB arbitration service was running.
When the host disk containing the virtual machine was full, powering on the virtual machine might have failed with the following
incorrect error message:
The Printer is out of paper.
The message now correctly states that the disk is full.
Some USB Human Interface Devices (HID) could not connect automatically if the
.vmx file contained the following line:
usb.autoConnect.device1 = "vid:<vid> pid:<pid>"
After a Windows 7 guest went into screen saver mode, you could not wake up the guest when you clicked inside the virtual machine. This problem occurred only when the following screen saver and power plan settings were selected or enabled:
- In Screen Saver Settings, a screen saver was enabled, the idle time was set, and On resume, display logon screen was selected.
- In Power Options, the Balanced plan was selected and the Turn off the display and Put the computer to sleep plan settings were set to the same timeout value as the screen saver idle time.
A Windows virtual machine with a Windows XP display driver model (XPDM) driver installed might have crashed due to a
vmx_fb.dll error and failed with a blue screen.
Top of Page
The known issues for VMware Workstation are grouped by topic in the following sections.
The 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.
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.
Workaround: In the %PROGRAMFILES%\VMware\VMware Workstation directory, replace the vmUpdateLauncher.exe file with the one available on VMware Communities.
Installation, Upgrade, and Compatibility
Having percent signs (%) in the VMware Workstation installation folder path might lead to failure of Workstation installation.
Workaround: Do not include percent signs (%) in the VMware Workstation installation folder path.
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.
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 Workstation concurrently.
Workaround: To upgrade VMware Workstation, complete the following steps:
If you do not have the proper permission to switch, contact your system administrator.
- Open Windows Task Manager.
- Verify that VMware applications or virtual machines are running under a different user.
- Switch to that user.
- Close all VMware applications and virtual machines.
- Switch back and upgrade VMware Workstation.
On Linux hosts, changes to the System proxy settings and Manual proxy settings might take effect after you restart VMware Workstation.
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.
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 Workstation 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 Workstation 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 Workstation installer user interface to fail.
Workaround: To preserve the DISPLAY environment add Defaults env_keep+="DISPLAY" to the /etc/sudoers file.
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.
Workaround: Install VMware Workstation in a directory path containing only ASCII characters.
Top of Page
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.
Integrated Virtual Debuggers
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.
Workaround: 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.
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".
Live debugging mode does not work on encrypted virtual machines.
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.
Record/replay might not function properly if the virtual machine has a serial port configured to serial<port_number>.fileType = thinprint setting.
Full screen switch mode is no longer supported, but it is still documented in the Workstation User's Manual.
Disregard the documentation.
Top of Page