VMware Fusion 2 Release Notes

CN 发行说明 | DE Versionshinweise | ES Notas de la versiòn | FR Notes de publication |
IT Note di rilascio | JP リリースノート

VMware Fusion 2.0.3 | 02 APR 2009 | Build 156731

Last Document Update: 15 APR 2009

These release notes cover the following topics:

What's New

VMware Fusion 2.0.3 is a maintenance release of VMware Fusion 2. It is a free upgrade for all VMware Fusion 1 and VMware Fusion 2 customers, and has the following enhancements and fixes for critical customer issues:

  • Resolves an issue where driverless printing stops working for users that run Mac OS X 10.5.6, and installed Apple Mac OS X Security Update 2009-001. The shared printers would disappear from Windows. If you configured your printer differently as a workaround, turn on driverless printing feature again by clicking Virtual Machine > Settings, selecting Printers, and selecting the Enabled check box.
  • Provides experimental support for Mac OS X Snow Leopard Server as a guest operating system. You can now run the latest Snow Leopard Server build (32-bit kernel) released before April 2009 in a virtual machine.
  • Resolves an issue with driverless printing, where the Enabled check box on Virtual Machine > Settings > Printers might get deselected automatically.

Prior Releases of VMware Fusion 2

Features from prior releases of VMware Fusion 2 are described in the release notes for each release. To view release notes for prior releases of VMware Fusion 2, click one of the following links:

Top of Page

Before You Begin

Use the recommended versions of the Mac OS X operating system

For Mac OS X 10.4 (Tiger), use version 10.4.11 or higher. For Mac OS X 10.5 (Leopard), use Mac OS X 10.5.2 or higher.

On VMware Fusion, Leopard provides a richer 3D experience than Tiger.

Installing VMware Fusion 2.0.3 overwrites earlier versions of the application

It is not possible to have multiple versions of VMware Fusion installed at the same time. So if you install VMware Fusion 2.0.3 on a machine that already has VMware Fusion 2.x or 1.x, VMware Fusion 2.0.3 replaces the earlier versions. To revert to an earlier version, you have to reinstall it.

Top of Page

Known Issues


  • Enabling 3D acceleration on systems with new chipsets and running 3D applications within VMware Fusion might cause your virtual machine to fail
    Enabling 3D acceleration on the Mac Pros and iMacs released in March 2009 that ship with the new ATI Radeon HD 4850 and 4870 chipsets might cause VMware Fusion to fail.
    Workaround: Turn off 3D acceleration by deselecting Accelerate 3D Graphics in Virtual Machine > Settings > Display when the virtual machine is powered off.

  • VMware Tools installation fails in German and French language Parallels 4 virtual machines
    Installation of VMware Tools might fail in German and French language Parallels 4 virtual machines that have file sharing enabled. VMware Tools might display the error message Error 1606. Could not access network location \\.psf\Home\Documents.
    Workaround: Uninstall Parallels 4 Tools and then install VMware Tools.

  • Cannot install Ubuntu 8.10 32-bit guest operating system on the new Mac Pro with Quad-core Nehalem processors
    The installation of the Ubuntu 8.10 32-bit guest operating system on a new Mac Pro with Quad-core Nehalem processors will fail with a message The CPU has been disabled by the guest operating system.
    Workaround: add two lines to the VMX configuration file of the Ubuntu 8.10 virtual machine by using the following steps.
    1. Navigate to the Mac folder where the virtual machine is located. The default is your Home folder > Documents > Virtual Machines.
    2. Right click on the Ubuntu 8.10 virtual machine package and select Show Package Contents.
    3. In a text editor open the file named <virtual machine name>.vmx, and add the following lines to the file:
    4. Save the file.
    5. Power up the Ubuntu virtual machine again.
  • Latest Snow Leopard seed does not install as a guest operating system on the Nehalem Mac Pro
    The installation fails with the error message, Virtual machine kernal stack fault (hardware reset).
  • VMware Fusion UI fails while importing a Parallels 4 virtual machine
    While importing a Parallels 4 virtual machine or Parallels server virtual machine, VMware Fusion UI might close with an error The application vmware quit unexpectedly, if the Parallels virtual machine’s system disk is not labeled 0:0 (the default value).
    Workaround: Set the Parallels 4 virtual machine’s system disk value as 0:0 (default) as follows:

    1. Select Configure from the Virtual Machine menu.
    2. Select Hard Disk in the left navigation bar.
    3. Select the Show advanced settings check box.
    4. Select 0:0 in the Location box.
  • VMware Tools is not automatically installed after using Linux Easy Install for Red Hat Enterprise Linux 5.2
    Workaround: Select Install VMware Tools from the Virtual Machine menu to start manual installation of VMware Tools, and follow the instructions in VMware Fusion Help topic "Installing or Upgrading VMware Tools in a Linux Virtual Machine from the Command Line with the Tar Installer.
  • Standby mode causes a Boot Camp virtual machine to go into a non-responsive state
    After your Boot Camp virtual machine enters standby state either triggered by Windows power management settings or by selecting Stand by from the Start > Shut down menu, it might become non-responsive.
    Workaround: Disable Windows power management in your Boot Camp virtual machine.
  • Registry corruption message after importing Parallels Desktop 4 with Windows 2003 or Windows XP 64-bit operating system
    After importing a Parallels Desktop 4 virtual machine with the Windows Server 2003 or Windows XP 64-bit operating system, you might see the following message upon the first login: Registry hive (file:SYSTEM) has been corrupted and has been recovered. Some data may have been lost. This message does not indicate registry corruption or data loss.
  • Unable to install VMware Tools NIC driver on Microsoft Vista Enterprise SP1 32-bit Boot Camp virtual machine
    Installation of VMware Tools NIC driver on Microsoft Vista Enterprise SP1 32-bit Boot Camp virtual machine might fail if you reinstall the Boot Camp partition with another operating system and start up the Boot Camp virtual machine from the Virtual Machine Library.
    Workaround: Remove the existing Boot Camp virtual machine from ~/Library/Application Support/VMware Fusion/Virtual Machines. Start the Boot Camp virtual machine again and install VMware Tools.
  • Display-related issues with Google Earth
    The opening display of Google Earth appears fractured, and lines appear textured.
    There is no workaround for this issue.
  • Key mapping issues with Ctrl and Shift
    If you assign additional functions to Shift and Ctrl keys by using key mapping, performing multiple selections in a virtual machine might fail.
    Workaround: Remove key mappings for key combinations that contain modifier keys. Alternatively, you can disable all keyboard remapping.
  • Cannot display images in the GUIMotions plug-in
    If you use the TMS GUIMotions plug-in for Borland's Delphi when writing applications that you want to run on virtual machines, the images for 3D animation are not displayed.
    There is no workaround for this issue.
  • Do not install VMware Fusion 2 and CheckPoint SecureClient on the same Mac
    When both VMware Fusion 2 and SecureClient VPN applications are installed on one Mac, the Mac OS X stops responding while booting or shutting down.
    If you encounter this issue, use the following workaround to boot your Mac in Safe Mode and remove one of the applications:
    1. Make sure the Mac is powered off.
    2. Press the power button.
    3. Press and hold the Shift key immediately after you hear the startup tone (but not before).
    4. Release the Shift key when you see the gray Apple and a progress indicator.
    5. Uninstall SecureClient or VMware Fusion.
    6. Reboot the Mac.
  • Upgrading a virtual machine's virtual hardware might trigger many notifications about PCI-to-PCI bridges being detected
    On some virtual machines created in or ported to VMware Fusion 1, when you upgrade the virtual machine to hardware version 7 in VMware Fusion 2, you see the New Hardware Found wizard at the reboot. This is because hardware version 7 comes with an additional 32 PCI-to-PCI bridge devices. Usually the drivers for them are silently installed, but on some systems, upgrading a virtual machine's virtual hardware might trigger Windows to show many notifications about PCI-to-PCI bridges being detected. It's not a loop; there are just a lot of new ones.
    Workaround: Click OK on the New Hardware Found dialog and allow them to be installed. Once all 32 PCI-to-PCI bridges are installed, the dialogs will not show up again.
  • PCI-to-PCI bridges fail to install following upgrading a virtual machine's hardware
    In certain circumstances, you might have a corrupted Windows XP driver database in the virtual machine, and the PCI-to-PCI bridges fail to install after you upgrade the virtual machine's hardware. When this happens, the New Hardware Found dialog appears every time you reboot and log in. When you try to install the drivers, the install fails.

    Workaround for Windows XP: Rebuild Windows device driver database as follows:
    1. Start the virtual machine and log in.
    2. Before clicking anything in the New Hardware Found wizard, go to Start > Run, launch cmd.exe.
    3. In the CMD window, type the following commands:
      cd \windows\inf
      del infcache.1
    4. Click Next in the New Hardware Found wizard. All the PCI-to-PCI bridges should install now.
  • DVD players fail or display an alert when you attempt to play a DVD
    Because of certain driver issues, DVD players like Windows Media Player 11 do not work with VMware Fusion 2.
    Workaround: Use VLC Player.
  • Slow boot time for virtual machine when drive letters are mapped to nonexistent locations
    When Windows drive letters are mapped to nonexistent locations, the boot time is significantly slower (physical Windows systems have the same issue).
    Workaround: Unmap unused drive letters by right clicking on Start > My Computer, selecting Disconnect Network Drives, and then disconnecting the troublesome drives.
  • Slow boot of Boot Camp virtual machines caused by a bug in Apple's Boot Camp software
    A slow boot of a Boot Camp virtual machine can be caused by Apple kbdmgr.exe. This is a bug in Apple's Boot Camp software.
    Workaround: Click Start > Run, then enter msconfig. Click on Startup, and disable kbdmgr.exe. (If you need Apple's keyboard extensions when rebooting into Boot Camp, then re-enable kbdmgr.exe before rebooting.)
  • Slow boot time for virtual machines imported in VMware Fusion 1 and then upgraded to Hardware Version 7 with VMware Fusion 2
    Windows Vista or Windows Server 2008 virtual machines that are imported from Parallels or Virtual PC boot extremely slowly if you upgrade them to Hardware Version 7.
    Workaround: Shut the virtual machine down and downgrade to Hardware Version 6 by clicking: Virtual Machine > Downgrade Virtual Machine.
  • Do not disable USB 2.0 support for a Mac OS X Server virtual machine
    If you plug a USB device into a host machine when you are running a Mac OS X 10.5.5 virtual machine on which USB 2.0 support is disabled the virtual machine might fail. In this situation, VMware Fusion displays the message The device was unable to connect to its ideal host controller when you plug in the USB device, and displays the message The CPU has been disabled by the guest operating system when you click OK to close the previous message. If this happens, go to the USB Devices panel of the Settings window for this virtual machine, and select Enable USB 2.0 support.

Top of Page