VMware Player 3.0.1 Release Notes

VMware Player Version 3.0.1 | 18 FEB 2010 | Build 227600

Last Document Update: 18 FEB 2010

Check frequently for additions and updates to these release notes.

These release notes cover the following topics:

What's New

VMware Player 3.0.1 is a maintenance release that resolves some known issues. This release of VMware Player adds the following new support:

New Support for 32-Bit and 64-Bit Operating Systems  

    Operating System

    Host and Guest Support

    Windows 2008 R2 Host and guest
    Windows Vista SP2 Host and guest
    Ubuntu 9.10 Host and guest
    RHEL 5.4 Host and guest
    CentOS 5.4 Guest
    Oracle Enterprise Linux 5.4 Guest

Prior Releases of Workstation

Features from the prior releases of VMware Player are described in VMware Player 3.0 Release Notes.

Known Issues

The known issues for VMware Player are grouped by topic in the following sections.

Installation, Upgrade, and Compatibility

  • When you upgrade VMware Player from a previous VMware Player release on a Windows Vista and Windows 7 host, one of the vmnet host virtual adapters might not be properly configured with a static IP address. After rebooting, ipconfig displays the adapter IP address as 169.x.x.x, instead of 192.168.x.x.
    Workaround: Use the Diagnose feature on Windows 7. Complete the following steps on the Windows 7 host:
    1. Select Start > Control Panel > Network and Internet > Connections.
    2. Right-click the VMware Network Adapter from the list and select Diagnose.
  • You can install VMware Player 3.0 only on hosts with CPUs that include physical address extension (PAE) support.
  • On Windows Vista and Windows 7 hosts, you must run VMware Player as an administrator to Easy Install a Linux virtual machine when using a physical CD. During this process the user interface might be unresponsive for several minutes.
  • On Linux hosts, attempting to reinstall the same version of VMware Player over an existing version does not work, because all the components already exist on the host.
    Workaround: To reinstall the same version of VMware Player, uninstall VMware Player, select Yes to save your configuration files, and reinstall.
  • You cannot map a virtual disk if the VMware Player installation path contains characters from a non-system language. In this case, the error message Failed to initialize library for mounting and unmounting virtual disks appears and the Utilities > Map option becomes unavailable.
    Workaround: Install VMware VMware Player 3.0 in a directory path that contains only characters from a local-system language.


  • The WDDM graphics driver included with VMware Player 3.0 is only compatible with virtual machines configured to use the latest virtual hardware version. Check the virtual hardware version if you are experiencing issues with Unity, running multiple monitors, or using Autofit on Windows Vista and Windows 7 guests.
  • Running Windows Media Player with visualizations in full screen mode on a Windows XP virtual machine might result in a blue screen while transitioning the virtual machine between full screen and console views.
  • Windows 7 virtual machines running on Linux hosts might experience display issues when using more than two monitors.
  • Attempting to Remote Desktop Protocol (RDP) to a Windows XP host running a Windows 7 virtual machine in Aero mode might cause the virtual machine to become unresponsive.
    Workaround: To use RDP, disable Aero mode in the guest.
  • When running 3D applications, any changes to the host display resolution including locking and unlocking the host, might cause the application to display incorrectly.
    Workaround: Restart the application to restore the 3D graphics.
  • The Flowerz screen saver on a Windows XP guest fails to display on Windows XP and Linux hosts.
  • To run your Windows 7 and Windows Vista virtual guests at resolutions of 1600x1200 and higher without 3D acceleration enabled, you must increase your VRAM size to at least 32MB. To modify the guest VRAM size edit the svga.vramSize property in the virtual machine .vmx file. For example, svga.vramSize = 33554432(32MB).

Top of Page

VMware Tools

  • If your virtual DVD/CD-ROM device is set to the Use physical drive option, when you upgrade VMware Tools on a Linux guest the virtual device switches to Use ISO image option. After the VMware Tools installation is complete, the virtual device might not switch back to the original state.
    Workaround: Manually set the virtual device to the Use physical drive option.
  • Attempting to shrink a virtual disk through VMware Tools causes the virtual machine to fail with the error message Lock rank violation. This problem occurs after the shrink preparation process is complete, after you answer Yes to the prompt Do you want to shrink the disk(s)?
  • Assigning low memory to a Windows NT 4.0 SP6a virtual machine might cause VMware Tools installation to fail with the error message 0x0000001E (0x800000003,.... KMODE_EXCEPTION_NOT_HANDLED.
    Workaround: Set the virtual machine memory to at least 128MB for a Windows NT 4.0 SP6a virtual machine.


  • Copy and paste or drag and drop of formatted text containing images might not work across different operating systems.
  • You cannot copy and paste or drag and drop content that exceeds the internal buffer limit of 4MB.
  • Copying and pasting files from the host to an Outlook email message or compressed folder in the guest and vice versa might fail.
    Workaround: Copy files from host to the guest desktop first and then paste the files from the guest desktop into the Outlook email message or compressed folder.
  • The virtual machine might fail when you run games in a Windows guest on an OpenSUSE 11 host, with the following error messages:
    • vmware-vmx: pcm_pulse.c:275: pulse_write: Assertion `pcm->last_size >= (size * pcm->frame_size)' failed.
    • Unexpected signal: 6.
    • vmware-vmx: pthread_mutex_lock.c:294: __pthread_mutex_lock: Assertion `robust || (oldval & 0x40000000) == 0' failed.
    Workaround: Disable PulseAudio on the OpenSUSE 11 host or upgrade from OpenSUSE 11 to 11.1.
  • When non-ASCII characters are used in the install path, the TMP/TEMP environment variable(s), or the user name that is associated with the VMware Agent Service, the Import or Export wizard displays the message Unable to connect to VMware Converter Agent on the local machine, and VMware Agent Service does not start.
    Workaround: Use Converter Standalone 4.0.1, or change the TMP/TEMP environment variable(s) and run VMware Agent Service as a user whose name does not include non-ASCII characters.
    To change to a different account, go to services.msc and select VMware Agent Service > Properties > Log On. Change Log on as from Local System account (the default value) to a different account.

Resolved Issues

  • On VMware Player 3.0, multiple core vCPU support does not work on Windows 7. As a result, Windows 7 Home Premium, Home Basic, and Starter editions which support a single CPU with multiple core can not use more than one vCPU in the virtual machine.
  • Importing a Windows 7 XP Mode virtual machine fails if you install VMware Player in a directory path that contains non-ASCII characters.
  • In some instances, if you choose not to download VMware Tools automatically, the virtual machine becomes unresponsive when you install VMware Tools manually using VM > Install VMware Tools.
  • In some instances on Red Hat Enterprise Linux 5.3 hosts, when you create a virtual machine the Next button in the Select a Disk Type dialog box is disabled.
  • On Red Hat Enterprise Linux 5.3 guests, printers configured on the host do not appear in the guest.

Top of Page