VMware

 

VMware Workstation 6.5.1 Release Notes

Workstation Version 6.5.1 | 21 NOV 2008 | Build 126130

Last Document Update: 21 NOV 2008

Check frequently for additions and updates to these release notes.

These release notes cover the following topics:

What's New

With this release of VMware Workstation, the following new features and support have been added:

  • Japanese localization — A localized version of Workstation is now available in Japanese for Windows hosts.
    Note: Technical Support services for Workstation are currently delivered in English. Japanese-speaking support engineers are available in a limited capacity during the operating hours of the local support center. For more information, see VMware local language support.
  • 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.

Workstation 6.5.1 is also a maintenance bug fix release. See Resolved Issues.

Top of Page

 

Prior Releases of Workstation

Features from the prior release of Workstation are described in the Workstation 6.5.0 release notes

Top of Page

 

Known Issues

The known issues are grouped as follows:

Localization and Internationalization

  • On Linux hosts, if you open a Workstation 5.x or 6.0.x virtual machine that has Japanese characters in the .vmx file name, Workstation 6.5 might exit unexpectedly. Note that newly created virtual machines in Workstation 6.5 usually transfer correctly between Workstation 6.5 Windows and Linux and Mac-Fusion 2.0 hosts when international characters are present. The issue with incorrect transfer occurs only with older virtual machines, created with previous versions of Workstation.
  • 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 Workstation 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 Workstation 6.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 Workstation 6.5.

Workstation and Virtual Machine Installation, Upgrade, and Compatibility

  • On Windows hosts, attempts to upgrade from Workstation 6.x to 6.5.1 or to uninstall Workstation 6.5.x might fail.
    Workarounds: Try to manually uninstall Workstation a second time. On Windows Vista hosts, temporarily disable UAC and run the upgrade or uninstallation again.
  • On Linux hosts that are running a GL-based X server (Xgl), after you install Workstation, you might not be able to power on a virtual machine until you reboot the host.
  • On virtual machines with a Windows 2000 operating system, if the virtual machine is set to automatically update VMware Tools, the virtual machine is not restarted after the update. You must manually restart the virtual machine to complete the update and start VMware Tools.
  • 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 Workstation 6.0.x, or an earlier 6.5 beta 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 Workstation UI

    Workarounds:
    1. 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.
    2. 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.

Display

  • If you use the TMS GUIMotions plug-in for Borland's Delphi when writing applications that you want to run in virtual machines, the images for 3-D animation are not displayed.
  • If you want to use exclusive mode when running a 3-D game, application, or screen saver, you must first go into full screen mode, then start the 3-D application, and then go into exclusive mode. If you start a 3-D application when you are already in exclusive mode, the virtual machine will go into full screen mode.
  • On some Linux guests, the shut down window does not appear in Unity mode. If you choose System > Quit in a Ubuntu virtual machine while in Unity mode, the shut down window does not appear.
    Workaround: Exit Unity mode, 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 mode 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.
  • On Linux hosts, if you use Unity mode and drag a file from a guest application window to the host, the version of the file on the guest might get moved to the guest's desktop.
  • When you place a virtual machine in Unity mode, Workstation 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 mode 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 mode often.
  • To enable use of the Autofit Guest command and the Fit Guest Now command on Windows 95 and Windows 98 guests, you must use the guest's Display Properties settings to change the screen resolution to a higher value than 640 X 480.
  • Turbolinux 10 Server has a problem with switching from XGA (Extended Graphics Array) to VGA (Video Graphics Array) such that the screen becomes black. You encounter this problem at the end of the process of installing the Turbolinux 10 Server operating system. After you click Finish in the installation wizard, the screen becomes black and the system does not reboot.
    Workaround: Manually reboot the guest operating system.
  • Occasionally, on Windows guests, when you try to play a QuickTime video while in full screen mode, you see only a black screen.

Integrated Virtual Debuggers

  • Remote debugging using the Integrated Virtual Debugger for Visual Studio might fail on powered off 32-bit virtual machines.
    Workaround: Power on the virtual machine and start remote debugging mode.
  • On Linux hosts, VMware recommends that you use the bundle installer rather than the RPM installer if you want to use the Integrated Virtual Debugger for Eclipse. The bundle installer gives you the option of specifying the path to Eclipse if the path cannot be found automatically.
  • If a virtual machine is powered off and you use the Integrated Virtual Debugger for Eclipse, you may see the error "Guest has only loopback IP address. Ensure that it has a properly configured TCP/IP connection to the host."
    Workaround: Enabled shared folders manually.
  • If you add additional .jar files to the class path of your Eclipse project and launch it inside a Windows virtual machine from within Eclipse then you may not be able to detach and re-attach the Integrated Virtual Debugger for Eclipse from the application.
  • Visual Studio 2005 allows multiple projects to be debugged simultaneously when Start is chosen. However, the Integrated Virtual Debugger for Visual Studio currently supports only one project and one configuration for debugging at any given time. If you select multiple projects as debugging targets, the Integrated Virtual Debugger for Visual Studio only chooses the first one on the list.

Miscellaneous Issues

  • On Windows hosts, if you make a linked or full clone of a virtual machine and then try to map the virtual disk files of the original virtual machine and the clone to drive letters on the host, only the first mapping succeeds. Because both disks have the same signature, you can map only one of the disks at a time.
  • If your host system freezes when you are running a virtual machine and you must force a reboot, you might need to manually remove stale lock files from the virtual machine. When you try to power on the virtual machine, you might receive a message that the virtual machine is locked, and you are prompted to take ownership of the virtual machine. If the attempt to take ownership fails, manually delete the .lck files and restart Workstation before powering on the virtual machine.
  • If you use File > Open or File > Import to convert a virtual machine or system image that contains a Windows NT 3.x, Windows ME, Windows 98, or Windows 95 operating system, you might see the following warning: Cannot configure the source image. You can ignore this message. These operating systems are supported only experimentally. You might need to modify the configuration of the destination virtual machine before using it.
  • Occasionally, when you use File > Import to convert a Symantec backup or Norton Ghost image (.sv2i files) with volume resizing, the operation stops responding.
    Workaround: First, try again. If the issue persists, try again without volume resizing.
  • The File > Open and File > Import commands have several limitations for StorageCraft ShadowStore images (.spf files) and Symantec Backup Exec System Recovery images (.sv2i files). The limitations are:
    1. No support for dynamic disks.
    2. Images relating to the backup of the same machine must be in the same folder, with no other images placed there.
    3. All the volumes in the disk up to the active and system volumes must be backed up. (For example, say there are 4 partitions (1-4) on a disk, and partition 2 is the active volume and partition 3 is the system volume. Volumes 1-3 must be backed up.)
    4. If it is an incremental image, up to 16 incremental backups are supported.
    In addition, for StorageCraft images, there is no support for systems with logical drives if the logical drive is also a system/active volume.

You may also view a list of knowledge base articles related to Workstation 6.5.

Top of Page

 

Resolved Issues

The following issues were fixed in this release of Workstation:

  • Although VMware does not support replaying recordings of virtual machine execution that you created with previous versions of Workstation, it is now possible to do so. When you attempt to play a recording created with Workstation 6.5.0 (release version), a Replay Compatibility dialog box appears, prompting you to choose from the following options:

    • Replay in Test Mode - Plays the recording. If you choose this option, the Replay Compatibility dialog box will also appear again the next time you attempt to play the recording.
    • Overwrite Version - Plays the recording as in test mode but acts like a "Don't display this message again" check box. If you choose this option, the Replay Compatibility dialog box will not appear the next time you attempt to play this recording.
    • Go Live - Acts like a Cancel button and cancels playing the recording.
  • On Windows XP guests, if you have the version control system CVSNT installed, VMware Tools might crash. If this happens, you must uninstall either CVSNT or VMware Tools. Without VMware Tools installed, you cannot use such features as Unity mode and cut-copy-paste and drag-and-drop of text and files between the virtual machine and the host computer. (Bug 320159)
  • If you configure a Red Hat Enterprise Linux 5 virtual machine to automatically update VMware Tools, the guest might freeze during the automatic update process. (Bug 323969)
  • If you have the Integrated Virtual Debugger for Visual Studio installed, Visual Studio sometimes crashes when you open a project. (Bug 333862)