VMware

VMware Fusion 3.1.3 Release Notes

VMware Fusion 3.1.3 | 31 MAY 2011 | Build 416484


These release notes cover the following topics:

What's New

VMware Fusion 3.1.3 is a maintenance release that resolves some known issues and includes improved functionality. It is a free upgrade for all VMware Fusion 3.x users.

Highlights of VMware Fusion 3.1.3 include:

  • Microsoft Windows 7 Service Pack 1: Support for Windows 7 SP1 32-bit & 64-bit.
  • Ubuntu: Support for Ubuntu 10.10 and 11.04 32-bit & 64-bit.
  • Microsoft Office: Fixed a problem opening attachments in Outlook 2010.
  • Video: Updated Windows WDDM driver with stability improvements.
  • File access: Improved reliability accessing shared files on the Mac.
  • Internet: Fixed slow first page loading in Internet Explorer 8.
  • USB: Improved handling of smartphones including the Nokia N8.

Prior Releases of VMware Fusion 3

Features from prior releases of VMware Fusion are described in the release notes for each release, along with existing known issues. In addition, the release notes contain information on system requirements and installation. To view release notes for prior releases of VMware Fusion 3.1, click the following links:

Resolved Issues

This release resolves the following issues:

  • The Samsung Galaxy S phone with Android 2.1 is not recognized in an OS X host or in a Windows 7 guest.
  • Previously, to use a Logitech HD Webcam C510 in a Windows 7 virtual machine, you had to include the quirks line (Usb.quirks.device0 = "0x046d:0x081d skip-reset") as a configuration option in the virtual machine configuration (.vmx) file. Now, you no longer need to include the quirks line in the .vmx file.
  • When you connect a Nokia N8 phone to a Windows XP guest and attempt to connect to it by using the Nokia Ovi Suite, the phone does not stay connected to the guest. The Windows Device Manager in the Windows XP guest reports This device cannot start. (Code 10).
  • You cannot connect USB 2.0 devices to FreeBSD guests.
  • When you use Suspend Guest and Resume Guest to suspend and resume an Ubuntu 10.10 guest, the network interface is down after the guest is resumed.
  • When you run an Nmap ("Network Mapper") scan from a virtual machine that is configured to use Network Address Translation (NAT) networking to an external Windows machine, the NAT service fails and the virtual machine has problems connecting to the external network.
  • You cannot use Microsoft Office 2010 in a Windows guest to open an attachment in a shared folder. The guest returns an error message that states the file is not located in a shared folder and cannot be opened by the host.
  • A Mac OS X Server 10.6.x virtual machine is unable to access IDE hard disks and CD/DVD drives after the guest is updated to 10.6.5 or newer. If the boot volume is on an IDE hard disk, the guest will fail to boot.
  • After a Windows 7 guest goes into screen saver mode, you cannot wake up the guest when you click inside the virtual machine. This problem occurs only when the following screen saver and power plan settings are selected or enabled:
    • In Screen Saver Settings, a screen saver is enabled, the idle time is set, and "On resume, display logon screen" is selected.
    • In Power Options, the Balanced plan is selected and the "Turn off the display" and "Put the computer to sleep" plan settings are set to the same timeout value as the screen saver idle time.
  • Previously, when you created a Mac OS X virtual machine in Fusion, the virtual machine configuration (.vmx) file contained an absolute path to the virtual machine disk (.vmdk) file. This setting prevented you from copying the virtual machine because the copy pointed to the .vmdk file for the original virtual machine. Now, the .vmx file contains a relative path to the .vmdk file and you can copy Mac OS X virtual machines.
  • When DisplayLink drivers are installed in a Windows 7 virtual machine, the virtual machine crashes when you run it in Fusion.
  • Previously, when a virtual machine was configured to use NAT networking, browser performance was slow the first time you launched Internet Explorer 7 or 8 after starting the virtual machine for the first time and after resuming the virtual machine. Now, browser performance has been improved.

Top of Page

Known Issues with VMware Fusion

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

Virtual Machine Creation Issues

  • If you split a large virtual disk into 2GB files, or if you have too many snapshots, you can exceed the open file limit of the Mac OS and cause the virtual machine to fail, and potentially damage the virtual hard disk.
    If you have a large virtual hard disk, or if you intend to use a lot of snapshots, you should not split a virtual machine's virtual hard disk into 2GB files. For smaller virtual hard disks, you can limit the number of snapshots you take.

    The default limit for open files on the Mac is 256. If you have a large virtual disk split into 2GB files, for instance a 500GB virtual disk split into 250 files, taking a snapshot immediately exceeds the limit because the snapshot attempts to create another 250 files. This can cause the virtual machine to fail when powered on, or fail when taking a snapshot. If you have smaller virtual hard disks, but are taking many manual snapshots and AutoProtect snapshots, the limit can be exceeded as well.

    Workaround: If you have encountered this problem, you can attempt to recover by converting the split files into a monolithic file. Converting to a monolithic virtual hard disk is a two-stage process.

    Delete all snapshots for the virtual machine:
    1. Select Virtual Machine > Snapshots > Snapshots.
    2. (Optional) If Only show my snapshots is selected, deselect it.
    3. Click the snapshot to delete, or shift-click to select multiple snapshots, and select Delete Snapshot.
    4. Click Delete to discard the snapshot and merge its changes into the parent virtual disk.
    Rebuild the virtual hard disk files as a monolithic file:
    1. Power off the virtual machine.
    2. Click the virtual machine thumbnail in the Virtual Machine Library and click Settings.
    3. Under Removable Devices in the Settings window, select Hard Disks.
    4. Deselect Split disk into 2GB files, and click Apply.
    VMware Fusion displays a progress dialog as it rebuilds the virtual disk.
  • 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.
  • 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.
  • A virtual machine powered on from the Boot Camp partition can fail if the Boot Camp partition uses a display connected as a USB device.
    VMware Fusion does not support USB adapters for connecting displays to virtual machines, such as a DisplayLink USB adapter. Windows 7 running natively in a Boot Camp partition can support displays connected as a USB device. If you power on such a partition as a virtual machine, the Windows 7 guest operating system fails because of the USB device present. At this time, the only way to be able to power on the Boot Camp partition as a VMware Fusion virtual machine is to remove the USB display device driver from Boot Camp when you have booted into it natively. After this, you can power on the Boot Camp partition as a virtual machine, but neither the virtual machine nor the native Boot Camp partition will use the USB display.
  • 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.
  • Easy Install of CentOS 4 can require user input at the beginning of the installation.
    When you create a virtual machine using a CentOS 4 DVD or CD image, the New Virtual Machine Assistant might offer to use Easy Install to create the virtual machine. Usually, Easy Install provides an unattended install experience, but in this particular case, the installation process asks a few questions at the very beginning of the install. Answer those and the installation will be unattended from there.
  • You must update VMware Tools manually when you upgrade VMware Fusion from version 2.0.x 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.x 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.
  • 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 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

  • Unity view windows can disappear, then reappear, if a guest application becomes unresponsive for a period of time.
    When a guest application becomes unresponsive for a while (for instance, when Outlook is in the process of sending an email), if that application is open in Unity view, its window can disappear during that period of unresponsiveness.
  • In some instances a Unity view window brought forward does not show contents previously obscured by a Mac application window.
    This can occur with Mac OS X 10.6 running on your Mac.

    Workaround: Move the window to refresh the contents.
  • On MacBooks with the Intel GMA X3100 graphics card, using Exposé in Unity view can cause VMware Fusion to fail if 3D acceleration is turned off.
    In this instance, VMware Fusion can fail with the alert, "A serious error has occurred inside your computer's OpenGL graphics drivers."

    To work around this problem, enable 3D acceleration.
    1. Power off the virtual machine.
    2. Select Virtual Machine > Settings, and click Display.
    3. Select Accelerate 3D Graphics, close the window, and restart the virtual machine.
  • With Ubuntu 10.04, and with Windows XP in certain cases, do not use a keyboard shortcut to minimize all windows when you are using Unity view.
    If you use command+d or control+option+d ("show desktop") to minimize an application window when you are using Unity view, the window can get into a loop of minimizing and restoring. This can occur with Ubuntu 10.04 on a Mac running 10.5.8 and 10.6.3, and with Windows XP on a Mac running 10.5.8 only.

    Workaround: Switch to Single Window view, then return to Unity view. Use command+m to minimize each window separately.
  • Cannot run OpenGL applications using full screen view across multiple displays with a Windows XP virtual machine.
    This problem does not occur with Windows 7 virtual machines.
  • 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.
  • 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.
  • 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.
  • Keyboard input works improperly in one virtual machine if another virtual machine is being suspended at the time of the keyboard input.
    If you suspend a virtual machine, and start some keyboard operation in another open virtual machine before the suspending is complete, the key input acts erratically. This issue disappears when the suspending process completes. Workaround: Wait until a virtual machine is completely suspended before using the keyboard in another open virtual machine.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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

  • Do not use fast user switching with Windows virtual machines.
    Using fast user switching can result in unpredictable behavior in the virtual machine, including problems with the mouse and with CPU usage.
  • The universal Mac OS X Server 10.6.3 (build 10d573) operating system does not work inside a virtual machine on the physical MacBook Pro models with Core i7 processors, released in April 2010.
    These physical machines were released after Mac OS X Server 10.6.3 (build 10d573) was released, and they have a processor that Mac OS X Server 10.6.3 (build 10d573) does not support. See http://support.apple.com/kb/ht1159 and http://discussions.apple.com/thread.jspa?messageID=11430561 for details.

    Workaround: Install Mac OS X Server 10.6 in the virtual machine and use a combo updater to update directly to 10.6.4 or 10.6.5 (the latest version at time of writing).
  • Install GCC in order to install VMware Tools and to share folders in openSUSE 11.3.
    VMware Fusion 3.1 does not include prebuilt kernel modules for openSUSE 11.3. If you want to use openSUSE 11.3, you must install the gcc compiler prior to installation of VMware Tools, so that the kernel modules can be compiled during Tools installation. Without the compiler installed, trying to enable shared folders produces the alert, "Unable to update run-time folder sharing status: Unknown error".
  • On SUSE Linux Enterprise Desktop 11.0 and 11.1 guests with PulseAudio version earlier than 0.9.19, the timer based scheduling with PulseAudio might not work properly with the virtual sound card ENS1371.
    Workaround: Turn off the timer-based scheduling and use the interrupt-based approach.
    1. From the SUSE Linux Enterprise Desktop guest, open the /etc/pulse/default.pa file.
    2. To turn off the timer-based scheduling, change the load-module module-udev-detect code to load-module module-udev-detect tsched=0.
      If you do not find the load-module module-udev-detect code in the file, then change the load-module module-hal-detect code to load-module module-hal-detect tsched=0.
  • If you have been using Ubuntu 10.04 with a VMware Fusion build earlier than this build or the release candidate build, you must delete some existing dockers to get certain dock icons to work in Unity view.
    Some dock icons for applications in your Ubuntu 10.04 virtual machine that you created prior to downloading this build of VMware Fusion will not work after you upgrade. You must delete the existing docker files for those applications after upgrading to VMware Fusion 3.1. After you delete the files, VMware Fusion produces new dockers that work properly.

    To delete old dockers, take the following steps.
    1. Suspend or shut down the virtual machine and quit VMware Fusion.
    2. Navigate to the Mac folder where the Ubuntu virtual machine is located. The default is user/Documents/Virtual Machines.
    3. Right click on the Ubuntu 10.04 virtual machine and select Show Package Contents.
    4. Open the Applications folder in the package, and delete the contents.
    5. Close the package, start VMware Fusion, and resume the virtual machine.
    New dockers are created automatically the first time you run the applications in Unity view.
  • 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.

File and Application Sharing Issues

  • Do not create nested shared folders with Linux virtual machines.
    If you share a folder that is already within a shared folder, the File Browser or the virtual machine can become unresponsive later when you attempt to access the folder.

    Workaround: Reboot the virtual machine and remove sharing from one of the folders.
  • 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 /.
  • 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.
  • Old .host alias for Shared Folders might still appear under My Network Places in Windows after upgrade to a version of VMware Fusion 3.
    With VMware Fusion 3, the UNC name path for Shared Folders was 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 a version of VMware Fusion 3. 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.
  • 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

  • Audio recording is broken in Windows virtual machines with Adobe Audition.
    Playback after recording produces unusable sounds and static. There is no workaround.
  • Some 3D applications in a virtual machine can cause a Mac with Mac OS X 10.5 Leopard to become unresponsive.
    Running certain video games and other 3D applications in VMware Fusion on Macs with Mac OS X 10.5 and the NVIDIA GeForce 9400M and 9600M GT chipsets can cause the Mac to become unresponsive.

    Workaround: Apple has fixed the underlying problem in Mac OS X 10.6 Snow Leopard. If you have a Mac with NVIDIA hardware, upgrade to Snow Leopard to use 3D applications in a virtual machine.
  • 3D in Topo USA 8.0 can cause VMware Fusion to fail with an unrecoverable error message.
    If you encounter problems switching to 3D using Topo USA 8.0 GPS software, disable 3D in the application by using the Start menu from the guest operating system.
    1. Select Start > Programs > DeLorme > Topo USA 8.0 > Tools > Tab Manager.
    2. Deselect 3D.
  • 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.

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

Virtual Machine Import Issues

  • VMware mouse driver not installed after importing a Parallels Desktop 5 virtual machine.
    When you import a third-party virtual machine, VMware Fusion automatically installs VMware Tools as the final step in the importation process. However, with a Parallels Desktop 5 for Mac virtual machine, you might see a dialog informing you that the vmmouse.sys driver could not be installed. If this happens, you can successfully install VMware Tools and the mouse driver manually by selecting Virtual Machine > Install VMware Tools in the VMware Fusion menu bar.
  • 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. In reality, this message is not a result of registry corruption, and no data has been lost. The message can be ignored, and does not occur on subsequent logins.
  • 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 alert, 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 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

  • VMware Fusion does not support using the Migration Assistant on a PC with a recovery partition.
    If you start a migration of a PC with a recovery partition, the migration fails with the error:
    Insufficient space on the source to store VSS snapshots or the source does not have any NTFS volumes. Error code:2147754783(0x8004231F)

    Workaround: If you are attempting to convert a physical machine with Windows XP or Windows Vista with a recovery partition, you can use the vCenter Standalone Converter http://www.vmware.com/download/converter.

    If you are attempting to convert a physical machine with Windows 7 with a recovery partition, there is currently no workaround.
  • If the network link is broken during PC migration, the process does not fail and might not produce an error message.
    Because of a timeout issue, a lost network link might not cause the migration process to fail with an alert. In these instances, the migration process can appear as if it is continuing to do work even though the lack of a network link prevents migration. There is no workaround.
  • Do not install the VMware Fusion Migration Agent on the source physical machine using non-ASCII characters in the path.
    For instance, do not install with a kanji character, or an umlaut, or other non-ASCII character. Doing so results in VMware Fusion not able to reconfigure the new virtual machine after the migration process finishes copying it. VMware Fusion displays the alert, "Unable to reconfigure the target virtual machine."
  • 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.

Device Issues

  • NEW An error occurs when you connect a Globetrotter Connect iCON 225 USB device to the host.
    Workaround: Update the host operating system to Mac OS 10.6.6.
  • If you are running Mac OS X 10.5.8, VMware Fusion does not recognize a virtual smart card.
    Connecting a smart card to a Mac running Mac OS X 10.5.8 does not result in VMware Fusion recognizing it. This issue does not occur on Macs running Mac OS X 10.6.2.
  • On Mac OS X 10.6.2, a smart card might not work in a Windows XP SP2 virtual machine due to a card sharing violation error.
    Upgrading the host to Mac OS X 10.6.3 or later fixes this issue.
  • If you try to add a new virtual hard disk when there is not enough free space on your Mac, you cannot resize that virtual hard disk to a smaller size.
    If you do not have enough free space for a new virtual disk of the size you have set, a message appears when you click Apply in the Hard Disk Settings panel, "The current amount of free space on the hard disk is not enough to create the specified disk file. Please choose a different location or specify a smaller disk size." However, when you try to make the disk smaller you can't, because the scroll box for disk size cannot be moved to the left to indicate a smaller size.

    Workaround: Delete this newly created disk, which is empty. Create a new, smaller disk.
  • If you have iTunes running on your Mac and iTunes running in a virtual machine when you connect an iPad, an iPad restore can fail under certain conditions.
    Having iTunes running on your Mac and in a virtual machine at the same time, you might encounter a problem when you connect an iPad to the virtual machine using the VMware Fusion USB connection dialog, and start a restore. This can produce the alert, "iTunes has detected an iPad in recovery mode. You must restore this iPad before it can be used with iTunes". If you click OK the iPad is recognized by iTunes on the Mac, but iTunes in the virtual machine is waiting for it to reconnect. The iPad doesn't reconnect, however, because it is connected to the host iTunes, and the virtual machine presents an alert: "The iPad "name" could not be restored. An unknown error occurred (1602)."

    If you encounter this issue, you can connect the iPad to the iTunes virtual machine by using the Virtual Machine menu, and carry on the restore. Select Virtual Machine > USB, and select Connect Apple iPad.
  • Attempting to mount a dynamic disk prevents the virtual machine from powering on in a Mac running Mac OS X 10.5.8.
    Mounting a dynamic disk is not supported in VMware Fusion. If you attempt this for a virtual machine on a Mac OS X 10.5.8 host, it locks the .vdmk file and prevents the virtual machine from powering on. This problem does not occur with Mac OS X 10.6.

    Workaround: Reboot your Mac. This unlocks the file.
  • 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.
  • 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.

Miscellaneous Issues

  • OVF Tool 2.0.0 might not open correctly, depending on the path to it.
    If OVF Tool is installed in a directory where the path contains spaces, the tool may not launch correctly in some circumstances. This issue is resolved in OVF Tool 2.0.1, available on the VMware Web site.

    Workaround for OVF Tool 2.0.0: Edit line 23 of the ovftool script to contain the following command: "$OVFTOOL_BIN" "$@"

Top of Page