Home > Blogs > VMware Fusion Blog

Fusion 8.1.1 Available Now with Important Networking fixes!

Hi Everyone,

Over the weekend we rolled out an update to Fusion 8 and Fusion 8 Pro that brings our version to 8.1.1.

The important fix has resolved a NAT port forwarding and DNS lookup issues that some users have been experiencing, particularly those who work with Hashicorp’s Vagrant plugin for VMware.

We’ve also addressed USB issues, Fusion crashes related to graphics, and we’ve plugged up a memory leak.

Get it via auto-update today, or grab the download directly from your MyVMware portal or our trial pages (you can drag the trial right over the copy in your /Applications folder, all your licensing and preference information is saved elsewhere)


Details from the release notes:

The following issues were resolved in this version of VMware Fusion.

  • Resolved: Running graphic software with MSAA enabled causes VMware Fusion to crash
    • In a Windows virtual machine, running graphic software, such as a Realtime Landscape Architect program, or a graphic game, such as Civilization 4, with Multisample anti-aliasing (MSAA) enabled causes VMware Fusion to crash.
  • Resolved: Resizing the window of a running virtual machine causes host-system memory to leak
    • Resizing the window of a running virtual machine by dragging its corner causes the amount of system memory used to increase. You can observe the memory usage by looking at the Memory Used value on the Memory tab of the Activity Monitor.
  • Resolved: Enabling port forwarding breaks NAT
    • Enabling any port forwarding prevents the vmnat supporting application to fail to perform Network Address Translation functions
  • Resolved: Installing an automatic update unexpectedly suspends remote virtual machines
    • In VMware Fusion, after you connect to a remote virtual machine stored on either an ESXi server or a Workstation Server instance, as Fusion updates, the automatic update suspends or shuts down the running remote virtual machine, in addition to the running virtual machines that are stored on the local disk.
  • Resolved: Connecting specific USB devices to a virtual machine through a USB 3.0 controller causes issues
    • In VMware Fusion 8.1, the following situations occur when you connect the specified USB devices to a virtual machine through a USB 3.0 controller:
      • USB 3.0 scanner – this type of device does not function inside a virtual machine.
      • USB 3.0 flash drive – you cannot format this type of device inside a virtual machine.

9 thoughts on “Fusion 8.1.1 Available Now with Important Networking fixes!

  1. Ross

    I have a lot of problems with the mouse on VMWare Fusion Pro. I need to restart the mac because the mouse remain clicked

    1. Moa

      I have lost mouse and keyboard input into my Linux Mint VM while running VMWare Fusion 8.1.1 on a Mac Pro 2013. Will revert to VMWare Fusion 8.1.0, but the poor quality of recent Fusion releases is pretty disappointing.

      It is shame that VMWare decided it doesn’t care much about Workstation/Fusion and got rid of the experienced developers for those products. I feel sympathy for the guys that remain. If this is not resolved I’ll be moving to Parallels. I really liked VMWare, but the desktop products seem to be struggling with reliability ever since VMWare management clearly decided that their workstation products are less important than their server ones. Sad puppies all around.

      1. Moa

        I manage to resolve my issue by using VNC to log in to my virtual machine. The VNC input worked perfectly, so I was able to shut down my VM (not suspend it, which was the only option when the VM didn’t receive input), and then restart the VM. After this I was able to install the Ubuntu package open-vm-tools and things worked smoothly.

        So VMWare Fusion 8.1.1 now works smoothly on the Mac Pro (the trashcan, not the laptop).

        I think my issue may have been VMWare Fusion did the upgrade with a VM running in the background and this borked its input. So it appears I was too harsh about the quality of this VMWare Fusion update, so I’ll apologize to the Fusion team and pat them on the back for the fixes. I’m still backing the workstation/Fusion developers against VMWare management though.

        I hope this helps someone – if you get frozen input into your VM then try VNC (if you’re running a Linux client and VNC is available for access).

  2. Pingback: Meet the team! - VMware Fusion Blog - VMware Blogs

  3. Pingback: Meet the Workstation & Fusion Teams! - VMware Workstation Zealot - VMware Blogs

  4. Pingback: Meet the VMware Workstation & Fusion Team - VMware End-User Computing Blog - VMware Blogs

  5. Prokash Sinha

    Can anyone please help me know why I can not setup a kernel debugging environment on OSX 10.11 VM on a 10.11 osx host. From the same host, I can setup the kernel debugging and it works fine for 10.10, 10.9, 10.8 …

    Note that even if I turned the system protection off after rebooting to System recovery mode.

    Few of us tried independently, but the VMware infrastructure no longer supporting halt on boot (nvram boot-args flags). So it does not stop at boot, therefore we can not connect to the target using kdp-remote…


  6. Jonathan

    Yo, Fusion 8.1.1 does NOT fix the issue with port forwarding over the NAT. See http://blogs.vmware.com/teamfusion/2016/01/workaround-of-nat-port-forwarding-issue-in-fusion-8-1.html You have loads of users complaining that it’s still broken, yet you do nothing about it. This issue alone is stoping several hundred of our employees upgrading to Fusion 8. We can’t access any of our internal networks when VPN’ed into work, which defeats the whole point of using Fusion.
    Looks like we’ll be changing to VirtualBox from now on, unless you pull your finger out VmWare.

Comments are closed.