VMware

VMware Workstation 6.0 Release Notes

Features | Documentation | Knowledge Base | Workstation Community

Release Date: August 28, 2008
Build Number: 109488

VMware Workstation lets you use your virtual machines to run Windows, Linux and a host of other operating systems side-by-side on the same computer. This Release Notes document contains new features, limitations, caveats, security fixes, and general release information.
This document covers the following topics:

What's New in VMware Workstation 6.0.x

This section lists VMware Workstation 6.0.x maintenance releases.

What's New in Workstation 6.0.4

Workstation 6.0.4 provides support for the following operating systems:

  • 32-bit and 64-bit Windows Vista SP1 as host and guest operating systems
  • Microsoft Windows Vista Enterprise
  • Microsoft Windows Vista
  • Microsoft Windows Vista Home Basic
  • Microsoft Windows Vista Home Premium
  • Microsoft Windows Vista Ultimate

Integrated virtual debuggers support most of the Microsoft Windows Vista SP1 operating systems as follows:

  • Eclipse integrated virtual debugger can be hosted on all 32-bit versions of Windows Vista. The debugger supports 32-bit and 64-bit Enterprise, 32-bit Ultimate, and 32-bit Business versions as a guest operating system.
  • Visual Studio integrated virtual debugger can be hosted on all 32-bit and 64-bit versions of these Windows Vista editions. It supports 32-bit and 64-bit Enterprise, Ultimate, and Business editions as a guest.

What's New in Workstation 6.0.3

Workstation 6.0.3 provides support for the following operating systems:

  • 32-bit and 64-bit Ubuntu Linux 7.10 as host and guest operating systems
  • 32-bit and 64-bit Red Hat Enterprise Linux 4.6 as host and guest operating systems
  • 32-bit and 64-bit Asianux Server 3 as a guest operating system
  • 32-bit and 64-bit Turbolinux 10 Server as a guest operating system
Note: The Eclipse Integrated Virtual Debugger is not yet supported on Ubuntu Linux 7.10 and Red Hat Enterprise Linux 4.6 hosts.

What's New in Workstation 6.0.1

VMware Workstation 6.0.1 provides enhanced support for host and guest operating systems. This version adds experimental support for the following operating systems:

  • 32-bit and 64-bit Windows Server 2008 (code name Longhorn) as host and guest operating systems
  • 32-bit and 64-bit SUSE Linux Enterprise Server 10 SP1 as host and guest operating systems
  • 32-bit and 64-bit openSUSE Linux 10.3 as host and guest operating systems
  • 32-bit and 64-bit Turbolinux 10 Server as a guest operating system
This version also support the following operating systems:
  • 32-bit and 64-bit Ubuntu Linux 7.04 as host and guest operating systems
  • 32-bit and 64-bit Red Hat Enterprise Linux 4.5 (formerly called 4.0 Update 5) as host and guest operating systems
  • 32-bit and 64-bit FreeBSD 6.2 as a guest operating system
These following features are also supported in this release:
  • Technical Support for Japanese Product Versions
    For more information, see the Japanese release notes.
    Note: VMware 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.
  • User Interface for Collecting Support Data — You can now click a button in the Workstation Help > About dialog box to gather troubleshooting data for VMware Technical Support. Earlier, you had to run the script from the command line.

What's New in Workstation 6.0

Workstation 6.0 provides the following support:

  • Workstation 6.0 adds experimental support for the following operating systems:
    • 32-bit and 64-bit Red Hat Enterprise Linux 4.5 (Beta, formerly called 4.0 Update 5) as host and guest operating systems
    • 32-bit and 64-bit SUSE Linux Enterprise Server 9 SP4 (Beta) as host and guest operating systems
    • 32-bit and 64-bit Ubuntu Linux 7.04 as a guest operating system
  • This version also supports the following operating systems:
    • 32-bit and 64-bit Windows Vista as host and guest operating systems
    • 32-bit and 64-bit Red Hat Enterprise Linux 5.0 as host and guest operating systems
    • 32-bit and 64-bit Ubuntu Linux 6.10 as host and guest operating systems
    • 32-bit and 64-bit Mandriva Linux 2007 as host and guest operating systems
    • 32-bit and 64-bit Solaris 10 Update 3 as guest operating system
    • 32-bit Novell Netware 6.5 SP5 as guest operating system
  • This version supports the following features:
    • Support for high-speed USB 2.0 devices.
    • Multiple Monitor Support
      At the click of a button, the guest can now span monitors and also reflect the monitor topology — applications, task bars, and so on inside the guest appear as you would expect them to on a multi-monitor system. You can specify how many monitors a virtual machine can detect, regardless of how many monitors are attached to the host. This feature is especially useful if you plan to deploy the virtual machine to a different host after you create it. You can also specify what screen resolution to use.
    • Integrated Virtual Debuggers
      With the Workstation IDE (integrated development environment) plug-ins, software developers are provided with menu items and toolbar buttons in Visual Studio (Windows only) or Eclipse (Windows or Linux) to easily develop and debug programs in virtual machines. Documentation for the virtual debuggers is now included in the Workstation User's Manual.
    • Run Virtual Machines in the Background
      You can now leave virtual machines and teams running in the background when you exit Workstation. On the host, a system tray icon indicates how many virtual machines are running in the background. You can click the icon to open a virtual machine.
    • Virtual Machines Can Act as VNC Servers
      You can set a virtual machine to act as a VNC server without having to install any specialized VNC software in the guest.
    • Continuous State Record/Replay Capabilities (Experimental)
      This feature lets you record all Workstation 6.0 virtual machine activities over a period of time. Unlike Workstation's movie-capture feature, the record/replay feature lets you exactly duplicate the operations and state of the virtual machine throughout the time of the recording. During playback of a recording, you can click a button to record from that point of operation.
    • Automation via Expanded VIX 1.1 API
      The VIX API (formerly known as the Programming API) is now compatible with Workstation 6.0. This API allows you to write scripts and programs to automate virtual machine operations. This release of the API is available in the C language. There are additional language bindings for Perl, COM, and shell scripts (vmrun).
    • Physical-to-Virtual Conversion and Enhanced Import Feature (Windows Hosts Only)
      Included in this release is the Converter Import wizard from the VMware Converter product. Using this wizard enables you to convert a physical Windows machine into a virtual machine, convert a virtual machine from one VMware virtual machine format to another, and convert virtual machines or system images from popular third-party vendors.
    • Appliance View for Virtual Appliances
      Rather than having users see a console view for an appliance, you can configure a new appliance view. It gives you a brief description of the type of server or appliance and provides a link that opens the browser on the guest system and connects to the correct port for the server console.
    • Support for Paravirtualized Linux Kernels
      If you have a VMware VMI (Virtual Machine Interface) 3.0 enabled kernel in a Linux guest operating system, you can now enable paravirtual support in the virtual machine.
    • Virtual Machine Communication Interface (VMCI) (Experimental)
      VMCI provides a faster means of communication among applications running on the host and in virtual machines. The VMCI infrastructure comprises an SDK and drivers for host and guest. This experimental feature is especially suited for users who want to write client-server applications. For more information, view the documentation from the VMCI Developer Resources page. Also see the README file. On Linux hosts, the README file is located in the directory /usr/share/doc/vmware/vmware-vmci/samples. On Windows hosts, it is in the VMCI folder in the Workstation installation directory (for example, C:\Program Files\VMware\VMware Workstation\VMCI).
    • VMware Player 2.0
      The Welcome page for VMware Player provides you the option of browsing to a virtual machine file or downloading a virtual appliance from the Virtual Appliance Marketplace. You can then use the new appliance view when running a virtual appliance. For more information about standalone VMware Player 2.0, see the VMware Player Documentation page.

Known Issues

This section describes the known issues found in Workstation 6.0.x releases.

  • You might not have the correct permissions to Workstation on a Windows Vista host, if you log in as a different user and do not enter the serial number at the installation time. You must enter the serial number at the installation time to ensure that you have the right permissions configured.
  • If you run the Workstation installer on a Windows Vista host in order to use the Change option, you must first turn off UAC (user account control). Otherwise, the wizard immediately displays the Finish dialog box and you receive an error message.
  • On Windows Vista hosts, if you uninstall Workstation from the Control Panel, you might see a user account control prompt that warns you about an unidentified program requires access to your computer.
    You can safely click Allow.
  • On Windows Vista hosts, if you start Workstation without administrative privileges, power on a virtual machine, exit Workstation with the virtual machine running in the background, and then start Workstation with administrative privileges, you cannot access the virtual machine.
    Workaround:
    You must run Workstation either always with administrative privileges or always without.
  • On Windows hosts, if you run Virtual Network Editor without administrative privileges, you might see inaccurate information.
    On Windows Vista hosts, you must be logged in as a member of the Administrators group and either disable UAC (user account control) or start the Virtual Network Editor by right-clicking it the Start menu and choosing Run as Administrator.
  • Sometimes when upgrading VMware Tools in Vista guests, you might see warnings about files being in use.
    Workaround:
    Click Ignore to allow the upgrade to continue.
  • On Windows Vista guests, to open the VMware Tools control panel, you must be logged in as an Administrator user.
  • If you are upgrading to Workstation 6.0.1/ACE 2.0.1 main release from Workstation 6.0.1/ACE 2.0.1 beta release, upgrade VMware Tools on Windows guests by uninstalling and then reinstalling VMware Tools through Workstation 6.0.1.
  • For Windows 95 virtual machines created with Workstation 4.5 or ACE 1.0, upgrades of VMware Tools are sometimes incomplete.
    Workaround:
    Uninstall and reinstall VMware Tools using Workstation 6.0.
  • The display turns black when switching from XGA (Extended Graphics Array) to VGA (Video Graphics Array) in Turbolinux 10 Server operating system.
    While installing Turbolinux 10 Server operating system, after clicking Finish in the installation wizard, the screen turns black and the system stops rebooting.
    Workaround:
    Manually reboot the guest operating system.
  • If you install Workstation on a Windows 2003 Server host, Workstation help is not displayed correctly until you enable JavaScript.
    This is because, on Windows 2003 Server, JavaScript is disabled by default in Internet Explorer.
    Workaround:
    1. In Internet Explorer browser, select Tools > Internet Options.
      The Internet Options window opens.
    2. Select the Security tab.
    3. Click the Custom Level.
      The Security Settings window opens.
    4. Go to Scripting > Active Scripting, and select Enable.
  • If you attempt to exit Workstation and run a virtual machine in the background when recording an activity on that virtual machine using the record/replay feature, the virtual machine might stop functioning. Always stop recording before running a virtual machine in the background.
  • Do not attempt to play recordings of virtual machine activity that you made with an earlier version of Workstation.
    On Linux hosts, doing so might cause Workstation to exit unexpectedly.
  • When the virtual floppy drive is connected to the physical floppy drive on the host, the guest might not recognize floppy disk changes.
    Workaround:
    Connect the virtual floppy drive to the physical floppy drive while a floppy disk is in the physical drive.
  • Workstation fails to install on 64-bit Linux hosts unless 32-bit compatibility libraries are installed in host.
    Some 64-bit Linux host operating systems don't install 32-bit compatibility libraries by default. Workstation runs on 64-bit systems, but needs the 32-bit compatibility libraries installed. When you try to install Workstation on a 64-bit Linux host without the 32-bit compatibility libraries, an error message similar to the following might appear:
    /usr/bin/ldd: line 171: /lib/ld-linux.so.2: No such file or directory
    Workaround:
    Install a 32-bit compatibility package for your Linux distribution. The name of the 32-bit compatibility package varies across distributions. For example, for Ubuntu, you must install the ia32-libs and ia32-libs-gtk packages. See your distribution's documentation or Web site to determine the 32-bit compatibility package for your distribution.
  • Workstation does not run on Red Hat Enterprise Linux 5 if the Xen kernel is installed.
    Workaround:
    To use Workstation, you must install the Red Hat Enterprise Linux kernel without Xen.
  • On Mandrake 10.0 guests, dragging and dropping files from guest to host does not work.
  • If you share a folder between a Linux host and a Windows guest, the Windows guest might not be able to access symbolic links.
    Symbolic links appear as regular files on Windows guests, but the links are not followed when you attempt to open them.
  • On Windows Vista hosts, if you want to use File > Import to create a virtual machine from a physical machine, you must start Workstation by right-clicking the desktop icon and choosing Run as administrator.
  • On Windows Vista hosts, if you try to use File > Import to create a virtual machine from a Windows Vista machine, which is not supported, the import fails. All subsequent attempts to use the File > Import feature also fail until you restart the machine.
    This issue occurs only if the very first import you try is a Windows Vista physical machine. This can happen if you choose to import a physical machine and then use the default setting, which is the local machine.
    Workaround:
    Restart the ufad-ws60 service. This can be done by an Administrative user at the command line, with the following command: net stop ufad-ws60 & net start ufad-ws60. You can also use the Services Manager to restart the VMware Agent Service entry. Rebooting also works.
  • If you use File > Import to create a virtual machine from a remote Windows 2000 physical machine and specify an ESX server as the destination, you might see an error message that displays VMware Converter installation failed.
    The resulting virtual machine might not power on successfully. Also, the VMware Converter Agent, which gets installed on the remote machine during the import process, does not get automatically uninstalled. To manually uninstall the VMware Converter Agent, use the Add/Remove Programs item in the remote physical machine's Control Panel. You can also reboot the machine.
  • Using File > Import to convert a physical machine to a virtual machine does not work if the source physical machine is running Windows NT.
  • Using File > Import to convert a physical machine to a virtual machine does not work if the source physical machine has VMware Converter installed on 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.
  • If you use File > Import to convert a virtual machine, some of the configuration properties from the source might be lost.
    For example, a generic SCSI device or shared folder might be removed.
  • On hosts that use a Windows 2000 Professional SP4 operating system, occasionally, you won't be able to use File > Import to create a virtual machine from a physical machine.
    The following error message appears: Unable to determine guest operating system. This error occurs when the msdos.sys file is either not present or not accessible.
  • The File > Open and File > Import commands have several limitations for StorageCraft ShadowStore images (.spi 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.
  • Visual Studio 2005 allows multiple projects to be debugged simultaneously when Start is chosen. However, the Visual Studio Integrated Virtual Debugger currently supports only one project and one configuration for debugging at any given time.
    If you select multiple projects as debugging targets, the Visual Studio Integrated Virtual Debugger only chooses the first one on the list.
  • The Eclipse Integrated Virtual Debugger plug-in might fail on 32-bit Red Hat Enterprise Linux hosts that run Eclipse 3.3.
Known Issues on Japanese Systems
  • On Japanese systems, if Workstation is installed in a directory whose name ends with a Japanese 5c character (the backslash character in ASCII), and then if you run a virtual machine in the background, you might not be able to restore it by right-clicking the system tray.
    Workaround:
    Start Workstation, display the sidebar, and click the virtual machine in the Powered-On list.
  • On Japanese hosts that use Windows Vista, if you attempt to use File > Import option to convert a Virtual PC image of a Windows 2003 Enterprise Edition machine to a virtual machine, the resulting virtual machine might not boot or might fail to blue screen.
  • If you attempt to use File > Import to convert a remote Japanese Windows 2000 Pro SP4 physical machine to a virtual machine, the import fails.
  • You cannot use File > Open to convert a StorageCraft image to a virtual machine if the filename or path contains non-ASCII characters.
  • The VMware VIX API and other SDKs, such as the Virtual Machine Communication Interface, have not been localized for this release.
    Also, the documentation for these SDKs is available only in English.
  • The Eclipse Integrated Virtual Debugger Is Not Localized for This Release.
    Also, the documentation for the Eclipse Integrated Virtual Debugger and the Visual Studio Integrated Virtual Debugger is available only in English.

Resolved Issues

This section describes the issues resolved in Workstation 6.0.x releases.

Fixed in 6.0.5 | Fixed in 6.0.4 | Fixed in 6.0.3 | Fixed in 6.0.2 | Fixed in 6.0.1 | Fixed in 6.0

Workstation 6.0.5

Workstation 6.0.5 addresses the following security issues:

  • Setting ActiveX killbit
    Starting from this release, VMware has set the killbit on its ActiveX controls. Setting the killbit ensures that ActiveX controls cannot run in Internet Explorer (IE), and avoids security issues involving ActiveX controls in IE. See the KB article 240797 from Microsoft and the related references on this topic.
    Security vulnerabilities have been reported for ActiveX controls provided by VMware when run in IE. Under specific circumstances, exploitation of these ActiveX controls might result in denial-of-service or can allow running of arbitrary code when the user browses a malicious Web site or opens a malicious file in IE browser. An attempt to run unsafe ActiveX controls in IE might result in pop-up windows warning the user.
    Note: IE can be configured to run unsafe ActiveX controls without prompting. VMware recommends that you retain the default settings in IE, which prompts when unsafe actions are requested.
    Earlier, VMware had issued knowledge base articles, KB 5965318 and KB 9078920 on security issues with ActiveX controls.
    To avoid malicious scripts that exploit ActiveX controls, do not enable unsafe ActiveX objects in your browser settings. As a best practice, do not browse untrusted Web sites as an administrator and do not click OK or Yes if prompted by IE to allow certain actions.
    The Common Vulnerabilities and Exposures has assigned the names CVE-2008-3691, CVE-2008-3692, CVE-2008-3693, CVE-2008-3694, CVE-2008-3695, CVE-2007-5438, and CVE-2008-3696 to the security issues with VMware ActiveX controls.
  • Update to FreeType
    FreeType 2.3.6 resolves an integer overflow vulnerability and other vulnerabilities that can allow malicious users to run arbitrary code or might cause a denial-of-service after reading a maliciously crafted file. This release updates FreeType to its latest version 2.3.7.
    The Common Vulnerabilities and Exposures has assigned the names CVE-2008-1806, CVE-2008-1807, and CVE-2008-1808 to the issues resolved in FreeType 2.3.6.
  • Update to Cairo
    Cairo 1.4.12 resolves an integer overflow vulnerability that can allow malicious users to run arbitrary code or might cause a denial-of-service after reading a maliciously crafted PNG file. This release updates Cairo to its latest version 1.4.14. The Common Vulnerabilities and Exposures has assigned the name CVE-2007-5503 to the issue resolved in Cairo 1.4.12.

Workstation 6.0.4

Workstation 6.0.4 resolves the following issues:

  • Virtual machines fail unexpectedly after a Symantec virus definition update from version 213 to version 220.
  • If you attempt to power on a virtual machine that is hosted on IBM IntelliStation Z Pro, the host fails displaying a blue screen.
  • When you attempt dial-up using some USB-ISDN modems with a virtual machine, you get a cable not plugged in error.
  • On Ubuntu 6.06 guests (which use X.org 7.0), upgrading VMware Tools from the version installed with Workstation 6.0.0 fails.
  • On Ubuntu 7.x guests, after you install VMware Tools, the vmxnet driver is not being used.
  • On Ubuntu 7.10 guests, the Ubuntu Network Manager sometimes erroneously reports that there is no network connection, even though one exists and the VMware Tools vmxnet networking driver is loaded and working properly.
  • On Ubuntu 8.04 hosts (which use kernel 2.6.24), when you install Workstation, the vmnet module does not build.

Security Fixes

  • On Windows hosts, if VMCI is enabled, a guest can run arbitrary code in the context of the VMX process on the host. This is a compiler-dependent vulnerability. The Common Vulnerabilities and Exposures assigned the CVE number CVE-2008-2099 to this issue.
  • A security vulnerability related to the host-guest file system (HGFS) might cause a buffer overflow. The Common Vulnerabilities and Exposures assigned the CVE number CVE-2008-2098 to this issue.

Workstation 6.0.3

Workstation 6.0.3 resolves the following issues:

  • On openSUSE Linux 10.3 hosts, USB devices cannot be used in a virtual machine unless you plug the USB device in to the host before powering on the virtual machine.
  • With Workstation 6.0.2 the iPhone might be seen as a camera device by a Windows guest but iTunes did not list the device in its device list. In Workstation 6.0.3, the iPhone is usable and visible in iTunes for Windows guests.
  • On 64-bit Windows Vista hosts, if the guest has a USB controller, and you attempt to connect or disconnect a USB device, occasionally the guest fails to blue screen with the USBPROT.SYS error.
  • For Windows guests, if a filename inside a shared folder includes any extended ASCII characters (that is, characters whose ASCII code is above 128), then you cannot view any of the files in the shared folder. The folder looks empty when you access it from the guest operating system. The value of such characters might not be converted to UTF-8.
  • For Windows guests, if you configure the virtual machine to connect to a specific physical floppy drive instead of using auto-detect, and if you then start the virtual machine without having a floppy disk in the drive, you might see a Windows - No Disk error message.
  • On Windows guests, you cannot access files that are cached for offline access. If you have set up the system to mount a network drive and enable the option to cache files for offline access, you might not be able to access the files unless the remote server is available.
  • On Linux guests that use X.Org Server 1.3, which includes Fedora Core 7 guests, you receive the following error message when installing VMware Tools: Detected X.org 1.3. No drivers for X.org version 1.3.
  • On some 64-bit Windows hosts, the host sometimes fails when starting up a Linux virtual machine that has paravirtual kernel support enabled.
  • If you install Workstation on a Linux host that uses kernel version 2.6.23 or higher, the necessary kernel modules are not built. As a result, Workstation is installed but cannot start.
  • On Windows Vista hosts and Windows guests, if you swap the left and right mouse button functions, as many left-handed people do, dragging and dropping files does not work correctly.
  • Occasionally, Windows guest fails when you use the multiple-monitor feature and view streaming video. This issue might arise if you have two monitors arranged one on top of another and you launch a media player from the secondary monitor.
  • In some Linux guest operating systems, the mouse pointer becomes unusable after you install VMware Tools.
  • Hardware breakpoints set in applications that run inside guest operating systems are lost occasionally.

Security Fixes

  • On Windows hosts, if you configure and enable a shared folder, it is possible for an attacker to write arbitrary content from a guest system to arbitrary locations on the host system (CORE-2007-0930).
  • An internal security audit determined that a malicious user might attain the local system privileges. The user might make the authd process connect to a named pipe that is opened and controlled by the malicious user. (Foundstone CODE-BUG-H-001) The malicious user might also successfully impersonate authd and attain privileges under which authd is running.
  • This release updates the libpng library version to 1.2.22 to remove various security vulnerabilities.
  • This release updates the OpenSSL library to address various vulnerabilities to denial-of-service attacks and buffer overflows. The Common Vulnerabilities and Exposures assigned the following names to these issues: CVE-2006-2940, CVE-2006-2937, and CVE-2006-4343.
  • Workstation 6.0.2 allowed anonymous console access to the guest by means of the VIX API. Workstation 6.0.3 disables this feature. The Eclipse Integrated Virtual Debugger and the Visual Studio Integrated Virtual Debugger prompt the user for account credentials to access a guest.

Workstation 6.0.2

Workstation 6.0.2 resolves the following issues:

  • Hosts with AMD Duron processors might not be able to power on virtual machines. This issue occurs when Duron processors that are based on Athlon do not have Intel SSE (Streaming SIMD Extensions).
  • Ubuntu 7.04 virtual machines sometimes power off unexpectedly if paravirtual kernel support is enabled.

Workstation 6.0.1

Workstation 6.0.1 resolves the following issues:

  • If you attempt to install a guest operating system by using a PXE boot with ZENworks Imaging, the installation process stops responding.
  • Occasionally, graphics are not displayed correctly in the guest. For example, bitmap graphics in edit mode in PowerPoint, graphs in Quicken, and graphic elements in Microsoft Word might not appear at all.
  • On Linux hosts, the Favorites list might get erased if you exit Workstation and manually choose to run some virtual machines in the background.
  • On Windows Vista hosts, you might not be able to view or select physical disk partitions when creating a virtual machine.
  • If you use multiple monitors and manually configure the display resolution in the guest operating system to a combined size that is larger than the guest that VRAM supports, the guest might fail or display blue screen.
  • On Windows hosts, if you want to create and run applications with the VMCI SDK, you must rename vmci.dll to crosstalk.dll.
  • To start a virtual machine in quick switch mode, on Windows hosts, you can use the command-line option -m with vmware.exe. Earlier, this option was available only on Linux hosts.

Security Fixes

  • This release fixes an issue that prevents VMware Player from launching. This issue is accompanied by the error message VMware Player unrecoverable error: (player) Exception 0xc0000005 (access violation) has occurred. This issue might result in a security vulnerability from some images stored in virtual machines downloaded by the user.
  • This release fixes several security vulnerabilities with the VMware DHCP server that might enable a malicious Web page to gain system-level privileges.
    The Common Vulnerabilities and Exposures assigned the following names to these issues: CVE-2007-0061, CVE-2007-0062, and CVE-2007-0063.
    Thanks to Neel Mehta and Ryan Smith of the IBM Internet Security Systems X-Force for discovering and researching these vulnerabilities.
  • This release fixes a security vulnerability that might allow a malicious remote user to exploit the IntraProcessLogging.dll library file to overwrite files in a system.
    The Common Vulnerabilities and Exposures assigned the following name to this issue: CVE-2007-4059.
    Thanks to the Goodfellas Security Research Team for discovering and researching these vulnerabilities.
  • This release fixes a security vulnerability that might allow a malicious remote user to exploit the library file vielib.dll to overwrite files in a system.
    The Common Vulnerabilities and Exposures assigned the following names to this issue: CVE-2007-4155.
    Thanks to the Goodfellas Security Research Team for discovering and researching these vulnerabilities.
  • This release fixes a security vulnerability that might allow a guest operating system user with administrative privileges to cause memory corruption in a host process, and thus potentially run arbitrary code on the host.
    The Common Vulnerabilities and Exposures assigned the following name to this issue: CVE-2007-4496.
    Thanks to Rafal Wojtczvk of McAfee for identifying and reporting this issue.
  • This release fixes a security vulnerability that might allow a guest operating system user without administrator privileges to cause a host process to stop responding or exit unexpectedly, making the guest operating system unusable.
    The Common Vulnerabilities and Exposures assigned the following name to this issue: CVE-2007-4497.
    Thanks to Rafal Wojtczvk of McAfee for identifying and reporting this issue.
  • This release fixes a security vulnerability in which Workstation starts registered Windows services such as the Authorization service with bare (unquoted) paths, such as c:\program files\vmware\.... Applications and services in Windows must be started with a quoted path. This vulnerability might allow a malicious user to escalate user privileges.
    Thanks to Foundstone for discovering this vulnerability.

Workstation 6.0

Workstation 6.0 resolves the following issues:

  • On Linux guests that have SELinux enabled, accessing shared folders (/mnt/hgfs) fails with kernel Oops error messages.
  • In guests running Red Hat Enterprise Linux 5.0 or Ubuntu Linux 6.10 (or any Linux guests that use X.org X Windows system versions 7.1 or higher) the Workstation 5.5.x VMware Tools installer does not install drivers for X Windows, and consequently the mouse does not perform correctly. The version of VMware Tools included with Workstation 6.0 does install the correct drivers.
  • Workstation 6.0 supports USB for Solaris guests.

Knowledge Base Articles

If you encounter any of the issues listed below, click the appropriate link or go to the VMware knowledge base and enter the article number as your search term.

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