VMware

VMware Fusion 3 Release Notes

CN 发行说明 | DE Versionshinweise | FR Notes de publication

VMware Fusion 3.0 | 27 OCT 2009 | Build 204229

Last Document Update: 16 NOV 2009


These release notes cover the following topics:

What's New in VMware Fusion 3

VMware Fusion 3 has a large number of enhancements, including:

Optimized for Snow Leopard

  • New 64-bit native core engine leverages power of Snow Leopard.
  • Support for both 32-bit and 64-bit Snow Leopard kernels.

3D Graphics Improvements

  • Support for Windows Aero with WDDM driver for Windows 7 and Windows Vista.
  • DirectX 9.0c with Shader Model 3 support for Windows virtual machines.
  • OpenGL 2.1 support for Windows XP virtual machines.
  • Improved 2D drawing performance in Unity, Single Window, and Full Screen views.

Easy Migration from Windows PCs

  • Integrated Migration Assistant guides you through migrating your PC to a virtual machine.
  • Automatically discover your Windows PC on the same network.
  • Save directly to your Mac the virtual machine that the Migration Assistant creates.

Full Support for Windows 7 Guests

  • Support for Windows Easy Install.
  • Support for Windows Aero, including Flip 3D.
  • Support for DirectX 9.0EX with OpenGL 1.4 with new WDDM graphics driver.
  • Support for 32-bit and 64-bit Windows 7 on Boot Camp partitions.

Performance Improvements

  • New 64-bit native core engine maximizes overall performance.
  • Full support for 4-way SMP.
  • Now automatically expose virtual multi-core CPUs to your virtual machines. This allows some versions of Windows XP, Vista, and Windows 7 to use additional cores.
  • Greatly reduced memory usage when booting up Windows virtual machines.
  • Greatly reduced memory usage when using Windows Vista and later virtual machines.
  • Greatly reduced memory usage when using new Windows XP virtual machines created with Windows Easy Install in Fusion 3.0.

Unity Improvements

  • Always-on Applications Menu on the Mac menu bar. Start guest applications directly from the Applications menu.
  • Windows applications work like Mac applications and work with application-specific Exposé.
  • Run 3D games and 1080p video in Unity view.
  • Access to Windows taskbar tray items in Unity view in the Mac menu bar.
  • Preview window allows you to monitor your virtual machine desktop and resize the window, even in Unity view.
  • Improved responsiveness in Unity view.

VHD Import

  • Download and import free Windows trials from Microsoft.
  • Import VHD virtual disks as VMware virtual machines.

Automatic Updates

  • Built-in software updater that checks, downloads, and installs VMware Fusion updates.

Virtual Machine Library

  • Easy access to common tasks with the Home view. Install guest operating systems, migrate physical PCs, set up a Boot Camp virtual machine, or download virtual appliances.
  • Discover and import virtual machines that Parallels Desktop or Microsoft Virtual PC for Mac create.

Full Screen View Improvements

  • New Full Screen view menu bar gives you full control of your virtual machine, including choosing when the menu bar appears in Full Screen view.
  • Move the full screen view menu bar to any side of the screen to avoid blocking guest user interface elements such as taskbars in Windows, the desktop menu in Linux, or the menu bar in Mac OS X Server guests.
  • Smooth animated transition when entering and exiting Full Screen view.

Multiple Display Improvements

  • Multiple-display Full Screen view with better performance for monitor layouts larger than 4096 pixels wide or 4096 pixels high on most Macs.
  • Multiple-display Full Screen view and multiple-display Unity view that work with WDDM in Windows 7 and Windows Vista guests.

Other UI Improvements

  • Cancelable Resume.
  • Live, smooth resize when resizing a virtual machine window.
  • Access the Virtual Machine Library from the VMware Fusion Dock icon.

Shared Folders and Mirrored Folders Improvements

  • Automatically hide common hidden Windows files in a shared folder, for example, Thumbs.db, $RECYCLE.BIN, and so on.
  • Open Microsoft Outlook attachments with Mac applications.
  • Improved compatibility with third-party applications including WLW, Office 2007, and so on.

Copy and Paste, Drag and Drop Improvements

  • Copy and paste images between a Windows or Linux virtual machine and the Mac.
  • Copy and paste formatted text (RTF) between a Linux virtual machine and the Mac.
  • Drag images between Windows applications and Mac applications.
  • Drag Microsoft Outlook attachments from a Windows virtual machine to the Mac.
  • Drag files in a virtual machine directly onto Mac applications.

Full Support for Mac OS X Leopard Server and Snow Leopard Server as Guests

  • Support for Mac OS X 10.6 Snow Leopard host.
  • Support for Mac OS X Server 10.6 Snow Leopard virtual machines running the 64-bit kernel (K64).
  • Now boots from virtual EFI for maximum compatibility with Mac OS X.

Keyboard Improvements

  • Faster performance with Remapped Keys.
  • Automatically recognizes European keyboards. Sending keys like @, {, }, and others to Windows works just like it does on the Mac.

Virtual Hard Disk Improvements

  • Mount a suspended virtual machine's virtual disks as read-only Mac volumes.

Networking Improvements

  • Select a specific network adapter for bridged networking.
  • Support for IPv6 in bridged networking.
  • Override the Ethernet MAC address of the virtual adapter.

Shared Smart Card

  • Access supported CAC or PIV smart cards from the Mac and a Windows virtual machine at the same time.

Top of Page

Resolved Issues

VMware Fusion 3 includes a fix for Snow Leopard users for an issue in which permissions of the Applications folder were reset to Read Only on every reboot.

Other VMware Fusion 3 Documentation

System Requirements for VMware Fusion

Minimum System Requirements
The minimum system requirements for installing and using VMware Fusion are:

  • Any Mac with an Intel processor
  • 1GB of RAM, 2GB recommended
  • 700MB of free disk space for VMware Fusion, and at least 5GB of free disk space for each virtual machine
  • Mac OS X version 10.5.8 or later; Mac OS X version 10.6 Snow Leopard or later
  • Operating system installation media (disk or disk image) for virtual machines

Note: You must have enough memory to run Mac OS X, plus the memory required for each guest operating system and for applications on the Mac and in the virtual machine. See your guest operating system and application documentation for their memory requirements.

System Requirements for Aero and Unity View Performance
The following list describes the recommended minimum hardware required to provide Windows Vista and Windows 7 Aero functionality in Unity view without performance issues.

  • Intel Core Duo 2.2GHz or better CPU
  • NVIDIA GeForce 8800 GT, ATI Radeon HD 2600, or better GPU
    Note: Intel GMA 950 and X3100 GPUs do not support OpenGL 2.0, and do not support Aero
  • Graphics Memory 256MB
  • Host System Memory 2GB
  • Guest Allocated Memory 1GB

Top of Page

Before You Begin

Use the recommended versions of the Mac OS X operating system.
Important: VMware Fusion now requires Mac OS X 10.5 ("Leopard") or later. It will not install on Mac OS X 10.4 ("Tiger").

Installing VMware Fusion 3 will overwrite 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 3 on a machine that already has VMware Fusion 2.x or 1.x, the VMware Fusion 3 version replaces the earlier version. This change does not affect your virtual machines.
If you want to revert to version 2.x or 1.x, you will need to reinstall it.

WDDM is the Windows Display Driver Model for Vista and Windows 7. This is a new feature for VMware Fusion, and development has focused on Aero-specific support and stability. Other 3D games or applications might work, or might experience problems ranging from graphic corruption to crashes. Be sure to save any work in progress before experimenting with 3D games and applications.

Installation Notes

VMware Tools
In order to make the download of VMware Fusion smaller, the VMware Fusion "light" installer (VMware-Fusion-<version-build>-light.dmg) comes bundled only with VMware Tools for Windows and Mac OS X. When you install VMware Tools for another operating system, you will be prompted to let VMware Fusion download VMware Tools from VMware's web site.

If you prefer to download a version of VMware Fusion bundled with all the VMware Tools packages, download the full VMware Fusion installer (VMware-Fusion-<version-build>.dmg or VMware-Fusion-<version-build>.iso).

McAfee Antivirus Products for Mac
There is an incompatibility between certain McAfee Mac antivirus products and VMware Fusion that can cause truncated virtual hard disk files (.vmdk) when you power off your Mac. This can happen with McAfee VirusScan for Mac 8.6.1, McAfee VirusScan for Mac 9.0, and McAfee Security for Mac 1.0.

This problem does not arise if you exclude your virtual machines from McAfee virus scans.

To prevent the virus scanner from scanning your virtual machine directory, take these steps.

  1. On your Mac, open your Applications folder and launch VirusScan.
  2. Click Preferences in the VirusScan for Mac window.
  3. Click More Options.
  4. Select Click lock to make changes.
  5. Select Exclude specific disks, files and folders, and click Add within the Excluded File or Folder section.
  6. Select the Virtual Machines folder within your Documents folder or the location that you store your virtual machines.
  7. Lock your changes and close the window.
The virtual machines will be excluded from being scanned.

Note: The incompatibility relates only to McAfee antivirus products running on the host Mac. Installing McAfee VirusScan Plus in your Windows virtual machines does not affect their virtual hard disks. VMware recommends running antivirus software in your virtual machines.

PC Migration Notes

VMware Fusion Migrate Your PC
The Migrate Your PC feature enables you to migrate an existing Windows PC into a VMware Fusion virtual machine. The feature supports Windows PC operating systems from Windows 2000 SP4 (with all critical patches) to Windows 2008 Server (not including R2). You can migrate a PC to a Mac running Mac OS X 10.5.7.

The VMware Fusion Migration Agent installer must be downloaded from the VMware web site and installed on the source PC. The installer is located at: http://www.vmware.com/go/pc2mac/.
(md5 checksum: 7d25bf73545ae58534720d501adb3177)

Before migrating, you must set the power options on your Windows physical PC so that your monitor and hard disks do not turn off automatically and that your system does not go to standby.

  1. In the Control Panel, click Power Options.
  2. On the Power Schemes panel, set Turn off monitor, Turn off hard drives, and System standby to Never.

Before migrating, you must set a password on your Windows physical PC if it doesn't already have one.
The Migrate Your PC feature requires that the Windows physical PC have a password. You enter the password in the Migration Assistant on your Mac in order to start the migration. If your physical PC does not have a password set, go to User Accounts in the Control Panel and create one.

If you migrate over a wireless connection, set your physical PC's screensaver to wait longer than the migration will take.
The simplest method is to set the wait to 9999.

  1. Right-click on the PC desktop and select Properties.
  2. Select the Screen Saver tab, set Wait to 9999, and click OK.

You cannot use the Migrate Your PC feature on a PC with a web server running on TCP port 443.
This includes users who have installed Microsoft's IIS web server, Apache, or another web server. Users who have installed Visual Studio will also be affected, since it installs Microsoft IIS by default.

You cannot run your PC and a migrated virtual machine at the same time if the PC is a member of an Active Directory domain.
If you migrate your PC to a VMware Fusion virtual machine, and your PC is a member of an Active Directory domain, you cannot run both the original PC and the migrated virtual machine at the same time because they present the same computer name and system identifier (SID) to the network.
Workaround: change the SID of the migrated virtual machine.

  1. Migrate your PC to a VMware Fusion virtual machine.
  2. After migration completes, but before powering on the migrated virtual machine, shut down the source PC. You want only one machine visible to the network at a time until you change the SID.
  3. Start the migrated virtual machine in VMware Fusion.
  4. Download a utility that can change the SID of your virtual machine. One such utility is NewSID ( http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx).
  5. Change the SID of the migrated virtual machine.
Tools such as NewSID can cause problems when migrating servers running SQL Server, as discussed here: http://kendalvandyke.blogspot.com/2009/01/changing-machine-sid-with-newsid-breaks.html.

The installer for the PC Migration Agent is currently in English only.
If you are using a version of VMware Fusion in a language other than English, when you install the PC Migration Agent on the physical PC, the installer is in English. The installed PC Migration Agent, however, is in the language in which you are working.
To use the English-language installer, click the button highlighted by default to get to the second panel, the "End User License Agreement" panel. Click I accept the terms of the License Agreement, and click the default buttons for the remainder of the installer panels.

Top of Page

Tips and Tricks

For tips and tricks on how to use the VMware Fusion interface and for answers to technical questions, see the FAQ: http://www.vmware.com/products/fusion/resources/faqs.html.

The VMware Fusion documents section of VMware Communities also contains much useful information: http://communities.vmware.com/community/vmtn/desktop/fusion?view=documents.

Known Issues with VMware Fusion

Installation Issues

  • VMware Fusion installation fails if a broken version of MacFUSE already exists on your Mac.
    If your installation of VMware Fusion fails with the message, The following install step failed: run postupgrade script for MacFUSE. Contact the software manufacturer for assistance, it is the result of an unsuccessfully installed version of MacFUSE already on the Mac that left a faulty symlink. To work around this problem you can either install VMware Fusion without MacFUSE or remove the faulty symlink before installing VMware Fusion with MacFUSE.

    To confirm the symlink is faulty, look at the Kind displayed in the Get Info window for the fusefs.fs file.
    1. In the Finder, go to //Library/Filesystems.
    2. Right-click on the file fusefs.fs to display the Get Info window.
      —If the Kind is Alias, the symlink is faulty.
      —If the Kind is File System Plug-in, the symlink is OK.

    To install VMware Fusion without installing MacFUSE:
    1. Restart the installer.
    2. On the Installation Type panel, click Customize to go to the Custom Install pane.
    3. Deselect MacFuse, click Install, and continue with the installation.

    To install VMware Fusion with MacFUSE:
    1. In the Finder, go to //Library/Filesystems.
    2. Delete or rename the file fusefs.fs.
    3. Restart the installer and continue with a Standard Install.
  • Installation can stall with the message, Please insert the "<username>" disc to continue installation if the installer is in a FileVault volume.
    If you have downloaded the VMware Fusion installer to a FileVault volume on a Mac running Mac OS X 10.5, a bug in the Apple installer can cause it to look for a non-existent disc. This does not occur on Macs running Mac OS X 10.6.

    Workarounds for Mac OS X 10.5:
    • Install from a location outside the FileVault volume (put the installer outside the FileVault home directory, or into its own disk image).
    • Install using a different user account that does not use FileVault.
  • You must update VMware Tools manually when you upgrade VMware Fusion from version 2.0.5 to VMware Fusion 3.
    For VMware Tools, automatic updates or updates from within a virtual machine do not work if you are upgrading from VMware Fusion 2.0.5 to VMware Fusion 3. This means that you cannot update VMware Tools from the guest by clicking Update Tools in the VMware Tools Properties dialog. To do a manual update, select Virtual Machine > Install VMware Tools from the VMware Fusion menu bar.


  • Users upgrading VMware Tools for Windows from VMware Fusion 3.0 beta or release candidate builds may receive warnings about unsigned drivers.
    VMware Fusion 3.0 beta and release candidate builds of VMware Tools installed two unsigned drivers (PVSCSI and LSI SCSI) by default. When installing or upgrading unsigned drivers, Windows might display a warning message.

    When upgrading VMware Tools to the generally available VMware Fusion 3.0 or later versions, these unsigned drivers will be upgraded, causing Windows to display a warning. To work around this, uninstall then reinstall VMware Tools.


  • You might have to reconfigure your virtual CD/DVD drive after installing VMware Tools.
    After you have upgraded VMware Tools in a Linux guest, VMware Fusion ejects the Tools installer ISO image from the CD/DVD device. However, you might have to reconfigure your virtual CD/DVD drive before you can use the physical CD/DVD device again.


  • 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.


  • 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.


  • Cannot install VMware Tools in a Mac OS X Server virtual machine if there is a CD already connected.
    Having a CD connected to the virtual machine interferes with VMware Fusion being able to install VMware Tools. Before you select Install VMware Tools, make the Mac OS X Server guest eject all CDs, for example by drag-and-dropping the CD icons on your guest desktop to the guest Trash icon.


  • Before installing VMware Tools on an openSUSE 11.x guest, you must uninstall a number of rpms from the guest.
    If you want to install VMware Tools onto a guest running openSUSE 11.x, you must first uninstall the open-vmware-tools, open-vmware-tools-gui, and vmware-kmp-default rpms before you can successfully install VMware Tools.

    You can remove those packages by running the following command as root

    $ rpm -e open-vmware-tools open-vmware-tools-gui vmware-kmp-default

    Or you can use the Software Management application in YaST:
    1. Open YaST.
    2. Click on the Software button located on the left side of the YaST window (optional, but helpful).
    3. Find and click Software Management.
    4. Remove the packages.

User Interface Issues

  • VMware Fusion does not support Bridged networking to a VPN.
    If you attempt to connect to a VPN with Bridged networking in a virtual machine, it might result in a "/dev/vmnet0 is not running" error. If this message appears, lower the network priority of the VPN service on the host. You can do this in System Preferences > Network.


  • When you create a Windows 7 virtual machine, Windows 7 Aero is not immediately enabled.
    Aero is not enabled the first time you start up a Windows 7 virtual machine. To enable Aero, right-click on the desktop, click Personalize, and select one of the Aero themes available in the window.


  • Putting a Mac OS X Server guest to sleep causes the virtual machine to become unresponsive.
    The default setting for Mac OS X Server is for it to never sleep. However, if you change the setting or use Apple > Sleep, the virtual machine becomes unresponsive.

    Workaround: Shut down the virtual machine and restart it, and make sure System Preferences is set to prevent sleeping: In the Energy Saver window, set the Put the computer to sleep when it is inactive for: slider to Never. Do not use Apple > Sleep.


  • The Applications menu might appear blank.
    In some cases, the Applications menu that VMware Fusion puts in the menu bar can appear unpopulated. Workaround: Select Virtual Machine > Settings, click Applications, and change Show applications menu in menu bar from Always to Never and back again.


  • Copy-and-paste or drag-and-drop for images is limited by the size of the internal buffer.
    The size limitation for image copy-and-paste or drag-and-drop is the internal buffer size, not the actual image file size. As a result, you might not be able to move an image file that is smaller than the limit of 4MB because the internal buffer exceeds that limit.


  • Copy-and-paste or drag-and-drop for formatted text containing images does not work in a number of cases.
    Because of different protocols, copy-and-paste or drag-and-drop of formatted text containing images or other non-text elements can result in only the formatted text being moved, without the elements.


  • Enabling 3D acceleration on Mac OS X 10.5.7 systems with ATI chipsets and running 3D applications within VMware Fusion might cause your virtual machine to fail.
    Workaround: Upgrade to Mac OS X 10.5.8.


  • QuickTime video might not work in Full Screen view.
    Occasionally, on Windows guests, when you try to play a QuickTime video in Full Screen view, you see only a black screen or jumbled graphics.


  • Virtual machine window might revert to using a single display after you switch to Full Screen view with multiple displays.
    When you switch to Full Screen view with multiple displays, in some instances the virtual machine window might revert back after 10 seconds to using a single display, and you may observe a few rendering artifacts during this process. Workaround: Wait 30 seconds and retry switching to Full Screen view.


  • While running a virtual machine in Full Screen view, switching Spaces desktops away from the virtual machine might result in an unexpected switch back to the virtual machine.
    This occurs if the menu option View > Full Screen Title Bar > Always Hide is selected. To work around this issue, press Command-Control-Return to exit Full Screen view, then select the menu option View > Full Screen Title Bar > Automatically Show and Hide.


  • Multiple displays might be mirrored in Full Screen view.
    If you have a Windows Vista or Windows 7 virtual machine in Full Screen view with Use All Displays in Full Screen enabled, when powering on the virtual machine the secondary display might mirror the contents of the primary display rather than being an extension of it.

    Workaround: Change to Single Window view and return to Full Screen view, after which Full Screen view operates correctly.


  • With Aero enabled, Windows Explorer stops responding when you resize the virtual machine window under certain conditions.
    In a Windows 7 virtual machine with Aero enabled, changing the size of the window along with changing the view mode can in some cases result in slow operation followed by the message, Windows Explorer is not responding.

    Workaround: Selecting Check for a solution and restart the program in the message window brings the virtual machine operation back to normal without information loss. If this issue happens often, disable Aero.


  • A virtual machine's window might become gray or black and unresponsive when exiting Unity view.
    Workaround: Suspend and resume the virtual machine. It should display properly. If not, quit or force quit VMware Fusion, and restart.


  • Do not upgrade or uninstall VMware Tools in Unity view.
    Upgrading or uninstalling VMware Tools while you are working in Unity view can result in garbled windows at the completion of the process.

    Workaround: If you find yourself in this situation, restart the virtual machine.


  • Disable screen saver and sleep before using Unity view in Ubuntu or Red Hat Enterprise Linux.
    Having a screen saver or sleep enabled when in Unity view in these two operating systems results in the virtual machine powering off at the idle time out.


  • An unexpected message appears after you select Show/Hide Taskbar in Unity or Use All Displays in Full Screen in certain situations.
    You might be presented with the message A configuration state change operation is already in progress. Your changes will not be saved if a number of conditions exist prior to you selecting Show/Hide Taskbar in Unity or Use All Displays in Full Screen from the View menu. This can happen if you have reverted to a snapshot that was taken in a view mode different than the view mode that is the current state of your virtual machine. For example, while you are using VMware Fusion in Full Screen view, you revert to a snapshot taken in Single Window view and then try to select one of the menu items.

    Workaround: Suspend and resume the virtual machine.


  • 3DMark fails to run with 3DMark error: "DirectX error message . . ."
    If the resolution of a display mode in a virtual machine is larger than that of the Mac, VMware Fusion resizes the window down to fit in the Mac display. This can cause an error message when you open 3DMark, although if you then quit and reopen 3DMark it launches fine. If you use 3DMark, have a host resolution that is larger than the display mode being set by any of the 3DMarks.


  • Overlapping windows have redraw issues in Exposé.
    Overlapping windows in Exposé have redraw issues with only the top most non-overlapping windows showing correctly.


  • vmrun soft power operations might become unresponsive.
    Soft power operations with the vmrun utility (suspend, stop, or reset commands with the soft parameter) occasionally become unresponsive if a snapshot occurs during the power operation.

    You have a choice of workarounds for automated vmrun scripts.
    • Put a timer in the script to exit when a soft-power operation takes too long.
    • Disable Autoprotect (rolling snapshots) on the pertinent virtual machines for the duration of the script.
    • Use hard power operations instead of soft power operations (do not specify the soft parameter).

  • Editing the default suspend script in VMware Tools can cause the virtual machine to become stuck in the suspend state the next time you attempt to suspend it.
    VMware recommends that you do not edit the default suspend script suspend-vm-default.bat. An incorrect script can cause the virtual machine to become stuck in the suspend state. If you are not able to edit the default script back to its original content, you can restore it by uninstalling and reinstalling VMware Tools.


Guest Operating System Issues

  • In certain cases you cannot log in following a reboot in a Windows XP virtual machine because you cannot enter a password.
    Occasionally, you are prevented from logging back in to a Windows XP virtual machine because you cannot enter anything in the password field. If this happens, press Control-Alt-Delete, which brings up the Log On to Windows dialog box. You can type the password in this dialog box and log in. See the Microsoft article on this issue: http://support.microsoft.com/kb/917556.


  • In some cases, the virtual machine window can become black if you disable 3D acceleration.
    If you have high resolution set in your Windows Vista or Windows 7 guest operating system (1600x1200 and above), the virtual machine window can become black if you turn off 3D. To work around this problem, set your virtual machine's VRAM to at least 32MB when 3D is turned off. You set the VRAM in the virtual machine's configuration file (.vmx).
    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 Vista or Windows 7 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 line to the file:
      svga.vramSize = "33554432"
    4. Save the file.
    5. Power up the virtual machine again.

  • Cannot install Ubuntu 8.10 32-bit guest operating system on Mac Pros with Quad-core Nehalem processors
    The installation of the Ubuntu 8.10 32-bit guest operating system on a 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:
      monitor.virtual_exec="hardware"
      monitor.virtual_mmu="software"
    4. Save the file.
    5. Power up the Ubuntu virtual machine again.


  • Install Novell Linux Desktop 9 using text mode only.
    Do not use the graphical installation program to install Novell Linux Desktop 9. This fails. When installing Novell Linux Desktop 9, use the text mode.


  • Install Red Hat Linux 7.0 using text mode only.
    Do not use the graphical, mouse-based installation program to install Red Hat Linux 7.0. This can fail into a black screen. When installing Red Hat Linux 7.0, use the text mode for installation.


  • Assigning low memory to a Windows NT 4.0 virtual machine can result in it failing when VMware Tools is installed.
    If you create a virtual machine with Windows NT 4.0 SP6a as the guest operating system, set the guest's RAM to at least 128MB. Otherwise, the virtual machine can fail with an 0x0000001E (0x800000003,.... KMODE_EXCEPTION_NOT_HANDLED message.


File and Application Sharing Issues

  • Add Shared Folders only from the Settings panel on a Mac running Mac OS X 10.6 (Snow Leopard).
    On a Mac OS X 10.6 Snow Leopard host, if you add shared folders using the Applications menu or using Virtual Machine > Shared Folders, VMware Fusion can fail when you try to navigate to that shared folder. To add shared folders, use Virtual Machine > Settings.


  • If you have Microsoft Outlook on your Windows guest, sharing or mirroring your Mac's Documents folder results in it becoming the default location for Outlook attachments and other data.
    In a virtual machine with Outlook installed, if you enable shared folders for ~/Documents, VMware Fusion creates an Outlook Temp folder within it and sets it up in the Windows registry as the Outlook temp folder. This makes it easier to open attachments from both the host and the guest.


  • Shared folders might appear hung if mapped to the host root directory while the host has many mounted drives.
    You can select the / (root) level on the host when selecting a shared folder. This might cause problems when trying to browse if the host has many mapped or mounted drives. This problem exists because Windows tries to read every directory before presenting it to the user. If the response time from the mapped or mounted share is slow, shared folders and the host become very sluggish or unresponsive. The more drives that are mapped/mounted, the longer it will take to display the list of directories under the shared folder directory.

    Workaround: Disconnect or unmount drives, or map your shared folder at least one level down from root. For example /Users rather than /.


  • Old .host alias for Shared Folders might still appear under My Network Places in Windows after upgrade to Beta 2.
    With VMware Fusion Technology Preview, the UNC name path for Shared Folders is changed from \\.host\Shared Folders to \\vmware-host\Shared Folders. If you used shared folders in a previous release, you might still see the .host alias in My Network Places after upgrading to Beta 2. If you select Shared Folders on .host and try to use it, you get a message that it cannot be found. Workaround: Delete the alias by right clicking on it and selecting delete.


  • You might get a "File cannot be opened by the host" message when you attempt to open an Outlook attachment in a virtual machine with an application on your Mac.
    If you enable ~/Documents as a shared folder while Outlook is running in the virtual machine, an Outlook attachment cannot immediately be opened with an application on the Mac. Workaround: Restart Outlook.


  • VMware Fusion does not support mirrored folders and other guest-host integration features when the guest user account is a roaming user profile.
    If you are logged in under a roaming user profile you can select to mirror folders in VMware Fusion, but no mirroring takes place. VMware Fusion does not display an alert when this happens. Other problems include not setting default URL handlers inside the virtual machine or to launch an application in the Mac from the virtual machine.


  • Default applications don't work if application sharing is not enabled in VMware Fusion preferences.
    Setting default applications in the VMware Fusion preferences Default Applications pane will not work if application sharing has not been set in the Settings window for a virtual machine. Make sure that the Sharing settings for the virtual machine have the checkbox Allow the virtual machine to open applications on your Mac enabled. Otherwise, the default applications set for handling URLs in the virtual machine won't be modified, and will not open links on the Mac.


  • If a proxy application is no longer available in a virtual machine, it might still be assigned to open files or URL types on the host Mac.
    If you uninstall an application in the virtual machine that has been assigned a role in the host, attempting to launch the proxy application from the host can power on the virtual machine, but VMware Fusion does not display an alert that the application is not available. If you revert to a snapshot of the virtual machine that doesn't have the application, the same thing happens. Uninstalling VMware Tools might have this result as well.


  • Sometimes VMware Fusion does not open a file or link with a default application.
    There are a number of cases where VMware Fusion, by design, does not open a default application and presents an alert stating "file on the host cannot be opened from inside of guest." VMware Fusion does not open files or links if the proxy application set on the host points to within the same virtual machine where the request originated. Also, VMware Fusion presents the alert if no application exists on the host that can open the file in the virtual machine.


  • Working offline messages and synchronization error messages can appear if mirrored folders is enabled.
    Using mirrored folders might, in some cases, cause Windows to incorrectly view a folder as an inaccessible network share and assume it is offline. This results in failed attempts to synchronize data or messages about no longer being connected to a drive.

    Workaround: Open a Windows Explorer window, Choose Tools > Folder Options and click the Offline Files tab. Deselect Enable Offline Files and restart the virtual machine.


  • The Applications menu does not provide access to the standard folders listed there for Windows 2000 Server.
    In some cases, choosing the My Computer, My Documents, My Network Places, or Printers items in the Applications menu does not display the corresponding window.


  • Default browser set in a virtual machine prevents any other browser from being a choice in default applications.
    In certain cases, having a particular application set as your default browser prevents other browser applications from being able to be seen as a choice for handling any of the common protocols, like http, https, ftp, and so on.


Application Issues

  • Internet Explorer in Vista virtual machine can't find the path to a file on the Mac host.
    If you attempt to open an HTML file on the Mac host using Internet Explorer 7 in a Vista guest (either by setting the file to open with Internet Explorer as a shared application or by double-clicking on the file in a shared folder from the virtual machine), Internet Explorer launches, but displays an alert saying it can't find the path to the file. This is the result of the Vista/Internet Explorer default security settings. To make opening the file work, "Protected Mode" must be disabled for the local intranet zone, and \\vmware-host needs to be added to the list of safe sites.

    Workaround:
    1. Open Internet Explorer, go to Tools > Internet Options.
    2. Click the Security tab and select the Local intranet zone (not Internet).
    3. Click Sites, then Advanced, type \\vmware-host and click Add, then Close and OK.
    4. Back in the Local intranet settings, deselect Enable Protected Mode.
    5. Click OK, and accept the warning, "The current security settings will put your computer at risk," by clicking OK again.
    6. Close Internet Explorer to apply the change.

    Internet Explorer will now open files from \\vmware-host correctly.


  • Do not run VMware Fusion concurrently with Heroes of Might and Magic V on a Mac with Snow Leopard K64.
    Your Mac can spontaneously reboot in this situation.


  • Some games with SecuROM copy protection might refuse to install with VMware Fusion.


  • Parts of the application window for Google SketchUp remain on the desktop after you quit the application.
    After quitting Google SketchUp, the SketchUp toolbar remains on the desktop, and the guest cursor remains the one for whatever tool Sketchup was using last. Workaround: Enable hardware acceleration within SketchUp. From the SketchUp menu bar, select Window > Preferences > OpenGL, and select Use hardware acceleration.


  • Altium Designer Winter 09 edition can fail if 3D acceleration is enabled in VMware Fusion.
    On a Mac with an NVIDIA 7300 GPU, Altium Design Winter 09 Edition can fail with a vmglPanic if 3D acceleration is enabled.
    Workaround: Disable 3D acceleration in Virtual Machine > Settings > Display.


  • QuickBooks cannot save a company data file on a shared or mirrored folder.
    When you attempt to save a new company data file to a shared or mirrored folder, QuickBooks reports error -6176, 0 "QuickBooks cannot get the network address of the server". To have QuickBooks recognize the shared or mirrored folder as legitimate, you must add the folder to the hosts file.
    1. In the guest operating system, go to \Windows\System32\drivers\etc.
    2. Open the hosts file.
    3. Add the line 127.0.0.1 vmware-host and save.
    Note: This can sometimes create undesired behavior: opening a file in the guest instead of failing when shared folders are not functioning, or it can cause a login dialog to appear under some circumstances.


  • Galactic Civilizations II fails or becomes unresponsive when it starts to load.
    This problem can occur on Macs running Mac OS X 10.5.8, but does not appear on Macs running Mac OS X 10.6 Snow Leopard. Solution: Upgrade to Snow Leopard.


  • Running certain 3D games and applications with ATI X1900 can cause your Mac to become unresponsive.
    Games known to cause issues with the ATI X1900 include Shin Megami Tensei and Portal. This occurs both with Mac OS X 10.5.8 and 10.6.


  • Running the 3DMark2001 SE Dragothic test can cause the virtual machine to freeze if certain conditions exist.
    On a Mac with an ATI Radeon HD 2600 and running Mac OS X 10.5.8, a virtual machine might freeze with an error message if you have run the Dragothic test in conjunction with another test. Running Dragothic by itself does not have this issue.


  • Flowerz screen saver on your virtual machine can fail.


Virtual Machine Import Issues

  • Some device drivers are not installed in the Windows XP SP3 virtual machine imported from VHD Test Drive.
    Microsoft has optimized the Windows image for the virtual machine IE6-XPSP3 in order to minimize the download time. As part of that optimization, drivers for various devices, including USB 2.0 controllers and the sound device, were omitted from the image. These devices have been disabled in the virtual machine because the driver files are unavailable.


  • VMware Fusion UI fails while importing a Parallels Desktop 4 virtual machine.
    While importing a Parallels Desktop 4 virtual machine or Parallels server virtual machine, the 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 Desktop 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.
  • 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.


  • Slow boot time for virtual machines imported in VMware Fusion 1, then upgraded to Hardware Version 7 with VMware Fusion 2 or later.
    Windows Vista or Windows Server 2008 virtual machines that were 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 from the menu: Virtual Machine > Downgrade Virtual Machine.


  • VMware Fusion doesn't run a new Boot Camp partition in certain cases.
    If you create a Boot Camp partition on a Mac that previously had a Boot Camp partition that you deleted, VMware Fusion can't run the new Boot Camp partition. This is because VMware Fusion has retained some files relating to the previous partition.

    To work around this problem
    1. Quit VMware Fusion and go to ~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp
    2. Delete Boot Camp
    3. Restart VMware Fusion and run the installer for the new partition

  • Flat Hard-Disk Image Cannot Be Imported.
    VMware Importer does not import Virtual PC virtual machines with any flat hard-disk images. If you attempt to import such a virtual machine, VMware Importer reports that the virtual disk is corrupt.


  • Reconfiguring the CPUs on an imported virtual machine results in an error.
    Some virtual machines imported from Microsoft Virtual PC or Parallels Desktop for Mac will not work with more than one CPU, so don't customize the import by changing the Processor configuration to two. Changing the CPU setting to two virtual processors while importing a virtual machine results in an error when you start up the virtual machine. You see the message, "The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this time." If you get this error, go to the Settings pane and change the Processors setting back to one virtual processor.


  • Using the Boot Camp partition as a virtual machine can, in a few rare instances, result in a 07B failure when the virtual machine is booted.
    If this happens, boot into Boot Camp natively, immediately hold down F8 and select boot into last known good state. This will restore the functionality of your Boot Camp partition only in native mode.


  • Slow boot time for virtual machine when drive letters are mapped to nonexistent locations.
    When Windows drive letters are mapped to non-existent 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, 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, then disable kbdmgr.exe. (If you need Apple's keyboard extensions when rebooting into Boot Camp, then re-enable kbdmgr.exe before rebooting.)


PC Migration Issues

  • Sound might not work in certain virtual machines migrated from physical PCs.
    If you use the Migrate Your PC feature to create a virtual machine from a physical PC running some Windows Vista or Windows XP Professional operating systems, sound might not work because of the lack of a sound device.

    Workaround: Add a sound device.
    1. Power off the virtual machine.
    2. Choose Virtual Machine > Settings to open the Settings window.
    3. In the Removable Devices section, select Sound.
    4. Click Add Sound Device and close the window.
    5. Power on the virtual machine and reinstall VMware Tools.

  • The PC Migration Agent dialog appears on a newly imported virtual machine, and in some cases stretches across the window.
    The PC Migration Agent needs to be running for VMware Fusion to migrate the physical PC. As a result, it gets migrated along with the other software, and because it is set to run at start up, it runs when you open your virtual machine for the first time. Deselect Run the Migration Agent every time I start my PC, click Exit on the Agent, and reboot the virtual machine.

    For some Windows XP and Windows 2003 operating systems, the PC Migration Agent dialog stretches across the virtual machine window. Click Exit on the Agent and reboot the virtual machine. When the agent appears again, VMware Tools will have run, so the dialog should no longer be stretched. You can deselect Run the Migration Agent every time I start my PC now.

Device Issues

  • DVD players fail or display an alert when you attempt to play a DVD.
    Because of certain driver issues, DVD players like Microsoft Media Player 11 do not work with VMware Fusion. Other players, like PowerDVD, are designed not to run in a virtual machine. Workaround: Use VLC Player.


  • Buggy PCSC framework (Apple problem ID 7151374) can cause VMware Fusion to fail when powering on a virtual machine.
    On Mac OS X, PCSC framework is installed by default. Because of a PC/SC Lite bug, VMware Fusion can fail during a virtual machine power-on. VMware Fusion partially works around this bug by deleting a redundant pcscd.pub file on the system. However, if you have installed libpcsc-lite in a custom directory, VMware Fusion can't detect this file and you must delete the file manually using root privileges.


  • Printing cannot be enabled if the virtual machine has more than one serial port configured already.
    If you have already added two or more serial ports to a virtual machine, you cannot enable a printer on the Printers panel of the VMware Fusion Settings window.


  • Enabling or disabling printers for a running virtual machine does not take effect immediately.
    Selecting or deselecting the Enabled check box on the Printers sheet in Settings does not add or remove printers if the virtual machine is running. To change the setting for printers and have it take effect, you must power off the operating system in the virtual machine, make the change, and power the operating system back on.


  • You cannot mount a virtual disk on a virtual machine in a Mac OS X 10.6 Snow Leopard host with 64-bit kernel.
    If you try to use VMDKMounter on a 64-bit kernel Mac OS X 10.6 host, you get an alert stating The VMware fuse daemon failed to start. Currently, MacFUSE does not work with 64-bit kernels.


  • VMDKMounter mounts NTFS hard disks as read-only.
    VMDKMounter depends on the Mac OS X file system support to mount virtual disk volumes. By default, Mac OS X comes with read-write support for FAT and HFS+ formatted volumes, and read-only support for NTFS formatted volumes.

    To add read-write support for NTFS volumes, you can install NTFS-3G separately. Note that installing NTFS-3G may prevent Startup Disk from recognizing your Boot Camp partition, as well as cause files with non-English names to be unreadable.

    If you do install NTFS-3G, you can boot into Boot Camp: you will need to hold down the Option key at startup.