|Name:||VMware Fusion 8.5.1-4543325|
|Files||VMware Fusion 8.5.1/VMWare Fusion 8 [KG].dmg (929.4 kB)
VMware Fusion 8.5.1/VMware-Fusion-8.5.1-4543325.dmg (385.8 MB)
Name: VMware Fusion for Mac
Release Date: 28 Oct 2016
Mac Platform: Intel
OS version:OS X 10.9 or later (OS X 10.11 recommended)
RAM: 2 GB RAM (4 GB or more recommended)
Processor type(s) & speed: 64-bit
Other Requirement: A copy of Windows (if you’ll be installing Windows)
Activation: Use the included KG (Courtesy of EMBRACE)
Can be installed over a previous version
Web Site: http://www.vmware.com/products/fusion.html
VMware Fusion 8 and Fusion 8 Pro–the latest versions of its virtualization software for running Windows on a Mac without rebooting–include full support for Windows 10, OS X El Capitan, and the latest Retina Macs, in addition to always-on access to Microsoft Cortana. They support DirectX 10 and OpenGL 3.3 for up to 65% faster graphics, alongside compatibility with USB 3.0 and multiple monitors with different DPIs. The virtual machine platform also delivers full 64-bit support with up to 16 vCPUs, 64GB RAM, and an 8TB hard drive for a single virtual machine.
Fusion 8 and Fusion 8 Pro are optimized for the latest Macs, including the iMac with Retina 5K Display and 12-inch MacBook. DirectX 10 support enables Mac users to run Windows virtual machines with native resolution on a 5K display, with USB-C support and Force Touch pass-through also in tow for the latest MacBooks. Fusion 8 Pro has additional advanced features and improvements, including the ability to connect to VMware vCloud Air, IPv6 support for both bridged networks and IPv6-to-IPv4 Network Address Translation (NAT), improved integration with VMware vSphere and support for several new Linux distributions and other operating systems.
What’s New in Version 8.5.1:
・Virtual machines running Linux kernel version 4.7 or above may crash or hang on hosts with Intel CPUs Virtual Machines running Linux kernel version 4.7 or above may crash during installation or during power-on with a crash in the intel_powerclamp driver. This issue has been reported with Ubuntu 16.10, but it is a generic Linux kernel issue.
Workaround:VMware is working with the OS vendors to have them fix their respective kernels. Until a fix is available, you can blacklist the intel_powerclamp driver so that the buggy code doesn’t get loaded.
To blacklist the driver:Add the kernel command-line option modprobe.blacklist=intel_powerclamp to the guest OS’s default grub configuration or add it directly at the grub menu during boot.
・If more than one monitor is used in Full Screen mode on macOS 10.12 host operating system, the virtual displays are merged into one space in different tabs, instead of creating Full Screen space on each monitor – On macOS 10.12 host operating system, if there is external monitor connected to the Mac machine, when you switch a virtual machine to Full Screen with “Use All Displays in Full Screen” option selected, the virtual machine shows in Full Screen only on one monitor and merges all virtual displays to it as tabs, instead of using separated spaces on all monitors. After changing the view mode back to Single Window, a redundant black space remains, and the Fusion menu bar is hidden automatically.
・A virtual machine using EFI firmware sometimes crashes when it is powering on – When powering on a virtual machine that uses EFI firmware instead of BIOS, the virtual machine sometimes crashes.
・Fusion can quit unexpectedly when running a Windows 10 virtual machine in Unity mode – Windows 10 virtual machines running in Unity mode may unexpectedly quit when you are working with certain applications.
・On macOS 10.12 host operating systems, the tab bar on the virtual machine window becomes blank when moving the mouse pointer into the virtual machine – On macOS 10.12 host operating systems, if you move the mouse pointer into a running virtual machine when there is no tools service running inside the guest OS, the tab bar shown on the virtual machine window becomes blank, and the Fusion menu Window > Merge All Windows is disabled for the virtual machine. This problem occurs if the virtual machine does not have VMware Tools installed or it has VMware Tools installed but the Tools services are not launched yet.
Full Release Notes: http://pubs.vmware.com/Release_Notes/en/fusion/8/fusion-851-release-notes.html