VMware Player 2.5.1 Release Notes
These release notes cover the following topics:
VMware Player Version 2.5.1 | 21 NOV 2008 | Build 126130
Last Document Update: 21 NOV 2008
Check frequently for additions and updates to these release notes.
- Japanese localization — A localized version of VMware Player is now available in Japanese for Windows hosts.
- Smart card support for Linux guests — Smart cards are now experimentally supported with Linux guests.
- Unity mode on Linux guests — Although support for Unity mode on Linux guests is still experimental,
repainting of application windows is much improved.
- 3-D graphics — Additional improvements have been made to improve 3-D performance on Windows XP guests.
Prior Releases of VMware Player
Features from the prior releases of VMware Player are described in the VMware Player 2.5.0 release notes.
Top of Page
The known issues are grouped as follows:
Localization and Internationalization
On Linux hosts, if you open a VMware Player 1.x or 2.0.x virtual machine that has Japanese characters in the .vmx file name,
VMware Player 2.5 might exit unexpectedly.
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 VMware Player 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 VMware Player 2.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 VMware Player 2.5.
VMware Player and Virtual Machine Installation, Upgrade, and Compatibility
On Windows hosts, attempts to upgrade from VMware Player 2.x to 2.5.1 or to uninstall VMware Player 2.5.x might fail.
Workarounds: Try to manually uninstall VMware Player a second time. On Windows Vista hosts, temporarily disable UAC and run the upgrade
or uninstallation again.
On Linux hosts that are running GL-based X server (Xgl), after you install VMware Player, you might not be able to power on a
virtual machine until you reboot the host.
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 VMware Player 2.0.x, or an earlier 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 VMware Player UI.
- 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.
- 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 Delphi when writing applications that you want to run in virtual machines, the images for 3-D
animation are not displayed.
- On some Linux guests, the shut down window does not appear in Unity view. If you choose System > Quit in an Ubuntu virtual machine while in
Unity view, the shut down window does not appear.
Workaround: Exit Unity view, 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 view 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.
When you place a virtual machine in Unity view, VMware Player 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 view 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 view often.
Occasionally, on Windows guests, when you try to play a QuickTime video while in full screen mode, you see only a black screen.
The VM streaming feature is not implemented with HTTP redirects for this release.
You may also view a list of
knowledge base articles related to VMware Player 2.5.
Top of Page