Fusion 12 Vmware

  • VMware Fusion 12 Pro Price: $199.00 Build, Test and Demo your next big thing with VMware Fusion Pro. Designed for power users, developers and IT admins, Fusion Pro is the simply powerful desktop hypervisor for the modern technology professional looking to use local or remote virtual machines, containers or Kubernetes clusters.
  • February 11, 2021 A number of months back, I wrote an article which looked at how we now provide a Kubernetes in Docker (KinD) service in VMware Fusion 12. In a nutshell, this allows us to very quickly stand up a Kubernetes environment using the Nautilus Container Engine with a very lightweight virtual machine (CRX) based on VMware Photon OS.
  • Except one glitch which I think VMWare is aware of: Fusion 12 fails to create the installation medium when you select the macOS Big Sur Installer: I’ve ran into this issue in the past, where are reboot of the host Mac fixed it, but not this time. To work around this I had to create an ISO file from the installer and use that to create the VM.

A number of months back, I wrote an article which looked at how we now provide a Kubernetes in Docker (KinD) service in VMware Fusion 12. In a nutshell, this allows us to very quickly stand up a Kubernetes environment using the Nautilus Container Engine with a very lightweight virtual machine (CRX) based on VMware Photon OS. In this post, I wanted to extend the experience, and demonstrate how we can stand up a simple Nginx deployment. First, we will do a simple deployment. Then we will extend it to use a Load Balancer service (leveraging MetalLB).

TECH SPECS Fusion 12 See VMware Fusion system requirements: Hardware All Macs launched in 2012. or later are supported, as well as: 2010 Mac Pro “Six Core”, “Eight Core” and “Twelve Core”.With exception, the following Macs are not supported: 2012 Mac Pro “Quad Core” using the Intel Xeon W3565 Processor Software Fusion 12.

This post will not cover how to launch the Container Engine or KinD with Fusion, since these are both covered in the previous post. Instead we will focus on deploying an Nginx web server. First, let’s look at a sample deployment and service for the Nginx application. Here is a simple manifest, which describes 2 objects; a deployment with 2 replicas (Pods), and a service. These are linked through the use of spec.selector.matchLabels. There is a single container image which presents its web service via port 80.

Assuming that I have once again used VMware Fusion to launch the Container Engine and KinD, I can apply the above manifest via kubectl create or kubectl apply via my MacOS terminal. Next, I will look at what objects are created. I should see a deployment, two Pods, two endpoints and a service.

As we can see, the deployment and two Pods are up and running. What is interesting to observe is the networking configuration. The idea behind a deployment is that there can be multiple Pods to provide the service, in this case an Nginx web server. If one of the Pods fails, the other Pod continues to provide the functionality.

Each of the Pods gets its own IP addresses (e.g., from the Pod network range. These IP addresses are also assigned to the endpoints, which can be referenced by the service.

Similarly, the idea of creating a Service is to provide a “front-end” or “virtual” IP address from the Service network range to access the deployment (e.g. It gets its own unique IP address so that clients of the web server can avoid using the Pod IP/Endpoints. If clients use the Pod IP addresses, then they would lose connectivity to the application (e.g. Ford 10 speed transmission lawsuit. web server) if that Pod failed. If connectivity is made via the Service, then there is no loss of connectivity if the Pod fails as the Service would redirect the connection to the other Pod IP address/Endpoint.

When a service is created, it typically gets (1) a virtual IP address, (2) a DNS entry and (3) networking rules that ‘proxy’ or redirects the network traffic to the Pod/Endpoint that actually provides the service. When that virtual IP address receives traffic, the traffic is redirected to the correct back-end Pod/Endpoint.

Let’s test the deployment, and see if we can verify that the web service is running. At present, there is no route from my MacOS to either the Pod network ( or the service network ( In order to reach them, I can add a static route to them using the IP address of the KinD node as the gateway. You can get the KinD node IP address by simply running a docker ps as shown below:

Now that the IP address of the KinD node has been identified, we can use it as a gateway when adding routes to the Pod network and the Service network. We can then test that the web server is running by using curl to retrieve the index.html landing page, as follows:

This looks good – we can get the Nginx web server landing page from both Pods. Let’s now check accessibility via the service. First, let’s remove the route to the Pods, and then add the route to the Service.

Excellent, everything appears to be working as expected. However, we would not normally allow external clients to access the ClusterIP directly as shown here. We would typically setup a Load Balancer service, which creates an EXTERNAL-IP. This is presently set to none, as per the service output seen earlier. We will configure the LoadBalancer using MetalLB.There are only a few steps needed. (1) Deploy the MetalLB namespace manifest, (2) deploy the MetalLB objects manifest and (3) create and deploy a ConfigMap with the range of Load Balancer / External IP addresses. Steps 1 and 2 are covered in the MetalLB Installation page. Item 3 is covered in the MetalLB Configuration Page. Below are the steps taken from my KinD setup. Note that the range of Load Balancer IP addresses that I chose are from to as per the ConfigMap.
Now there is only a single change need to my Nginx manifest, and that is to add the spec.type: LoadBalancer to the Service, highlighted in blue below:
Let’s again query the objects that were created from this manifest, and we should see that the Service now has both a ClusterIP and an External-IP populated. It should match the first IP address in the range provided in MetalLB’s ConfigMap, which it does (
This is now the IP address that should be used by external clients to access the web service. However, as before, there is no route from my desktop to this network, so I need to add a static route, once again using the KinD node as the gateway.

Everything is working as expected. Hopefully that has given you a good idea of how you can use KinD in VMware Fusion (and indeed VMware Workstation) to become familiar with Kubernetes.

VMware Fusion 12 14 September 2020 Build 16880131

What's in the Release Notes

The release notes cover the following topics:

Vmware 12 Pro Download Free

About VMware Fusion

VMware Fusion® 12 is the easiest, fastest, and most reliable way to run Windows and other x86 based operating systems on a Mac without rebooting.

For more information, see the broader VMware Fusion documentation.

System Requirements

  • Hardware
    Mac models that support macOS 10.15 Catalina and newer version.

    • Mac models that support macOS 10.15 Catalina - https://support.apple.com/en-us/HT21022.

  • Software
    macOS 10.15 Catalina and newer versions.

What's New

  • Free Product for Personal Non-Commercial Use

    Fusion Player (previously Fusion Standard) is now free for personal non-commercial use.

  • Support macOS 11 Big Sur
    • Run macOS 11 Big Sur as a host operating system.
    • Run macOS 11 Big Sur as a virtual machine.
  • DirectX 11 and OpenGL 4.1 Support
    • Support has been added for DirectX 11 (DX11) and OpenGL 4.1 in the guest operating system.
    • Hardware requirements for DirectX 11 and OpenGL 4.1:
      • MacPro 2013 and later
      • iMac 27-inch 2014 and later
      • MacBook Pro 13-inch 2015 and later
      • MacBook Pro 15-inch 2015 with dual graphics and later
      • MacBook Air 2015 and later
      • MacBook 2015 and later
      • iMac 21-inch 2015 and later
      • iMac Pro 2017 and later
      • MacMini 2018 and later
    • Software requirements for DirectX 11 and OpenGL 4.1:
      • Guest OS: Windows 7 or higher, or Linux with vmwgfx.
  • External GPU support

    Fusion provides support for external GPU when an external GPU is connected to the host. Choose the Prefer External GPU option from the Fusion UI.

  • Sandboxed Graphics

    Virtual machine security is enhanced by removing graphics render from vmx and running it as a separate sandbox process.

  • New Guest Operating Systems Support
    • RHEL 8.2
    • Debian 10.5
    • Fedora 32
    • CentOS 8.2
    • SLE 15 SP2
    • FreeBSD 11.4
    • ESXi 7.0
  • USB 3.1 Controller Support

    The virtual machine's virtual XHCI controller is changed from USB 3.0 to USB 3.1 to support 10 Gbps.

  • Larger Scale VM
    • 32 virtual CPUs
    • 128 GB virtual memory
      Note: Running virtual machines with 32 vCPUs requires that your host and guest operating systems both support 32 logical processors.
    • 8 GB virtual graphics memory
  • Create VM from APFS Recovery Partition (Now limited to macOS 10.15 host)
  • Performance Improvements
    • Improved file transfer speeds (Drag and Drop, Copy and Paste, HGFS)
    • Improved virtual machine shutdown time.
    • Improved container performance.
  • vSphere 7.0 Support

    In Fusion 12 you can perform the following:

    • Connect to vSphere 7.0.
    • Upload a local virtual machine to vSphere 7.0.
    • Download a remote virtual machine running on vSphere 7.0 to the local desktop.
  • Login to Container Image Registry

    Ability to login to a container image registry with the vctl login command has been added.

  • Kubernetes Support

    Fusion 12 now supports KIND kubernetes clusters.

  • Improved Accessibility Support

    Accessibility improvements have been added so Fusion is compliant with WCAG 2.1 criteria.

Product Support Notices

  • Removal of restricted virtual machines
    Restricted virtual machine has reached end of life and been removed from VMware Fusion 12.
  • REST API security hardening
    REST API is now only available on local host.

Important Fixes

This release of VMware Fusion addresses the following issues:

Fusion 12 Vmware

  • Fusion addresses a privilege escalation vulnerability due to the way it allows configuring the system wide path. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the identifier CVE-2020-3980 to this issue. For more information, see VMSA-2020-0020.

Fusion 12 Vmware Download

Resolved Issues

  • USB devices are not recognized after the Mac wakes up from sleep mode

    A USB device connected to guest OS is not recognized after the Mac woken up from sleep mode.

    This issue is now resolved.

  • Unable to use a 2 TB USB drive in the guest OS after upgrading to Fusion 11.5.5

    2 TB USB drives are not recognized in guest OS.

    This issue is now resolved.

  • Unable to use the USB devices in macOS Mojave guest operating systems.

    Unable to connect USB devices to macOS Mojave guest operating systems as they are not recognized.

    This issue is now resolved.

  • User data in an anonymous volume is lost when the container is stopped

    If a host directory is not mounted to an anonymous volume of a container, the user data in the anonymous volume is not persistent after the container is stopped.

    This issue is now resolved.

Known Issues

Vmware Tools Fusion 12

  • Unable to access port forwarding on a NAT virtual machine, if the traffic is routed through the host IP stack on Big Sur hosts

    On Big Sur hosts, if user configures NAT port forwarding in Fusion, the service running in the virtual machine is unavailable on the macOS host using localhost:exposedPort, hostIP:exposedPort, or; Port forwarding is also not accessible inside a NAT virtual machine using hostIP:exposedPort.

    Workaround: Access the NAT port forwarding through another physical machine with Windows or macOS; or
    access the NAT port forwarding from a bridged virtual machine running on the same Mac machine as the NAT virtual machine.

  • Virtual machine's IP address must be changed for NAT port forwarding to work after upgrading Fusion on Big Sur hosts

    If user configures NAT port forwarding on Fusion 11, the port forwarding may be not accessible after upgrading to Fusion 12 on Big Sur because the virtual machine's IP address changes after upgrade.

    Workaround: Change the IP address used for the port forwarding to the current IP address assigned to the virtual machine.

  • Users are unable to capture transfer packets in the same subnet of a virtual network inside a virtual machine.

    Virtual machine's virtual interface doesn't report packet exchanges between other virtual machines in the same subnet on Big Sur hosts.

    Workaround: Use the virtual interface on the host to capture traffic information in the subnet. For example, use the interface bridge100 on macOS host to capture the traffic in the subnet.

  • If you are using multiple displays in Full Screen mode and the external display is unplugged and re-plugged, multiple full screen spaces will be created in the same display

    The guest OS screen can't be refreshed to the expected screen topology and the user is unable to interact with guest OS using keyboard and mouse after unplugging and re-plugging an external monitor.

    Workaround: Go back to Single Window mode, then switch to Full Screen again.

  • Jumbo Frame can't be enabled for NAT and Host-only virtual networks on Big Sur hosts

    MTU configuration option is not available in the Fusion UI on Big Sur hosts.


    1. To enable jumbo frames on macOS host, navigate to System Preferences > Network> Advanced >Hardware > MTU.
    2. Change the virtual machine network to bridged mode to use the jumbo frame feature.
  • Can't boot a macOS Big Sur virtual machine into Recovery mode or install macOS Big Sur from host Recovery

    A virtual machine running macOS Big Sur is stuck in a reboot loop after attempting to boot the guest OS into Recovery by holding the Command+R key during boot. Attempting to create a new Big Sur virtual machine from the host's Recovery partition results in the same failure.

    To restore normal operation of an existing macOS Big Sur virtual machine, clear the virtual machine's nonvolatile RAM (NVRAM) by holding the Command+Option+P+R key combination.

  • After the easy install operation is complete, the VMware Tools is not installed in the guest operating system

    Easy install will not install VMware tools in some guest operating systems including Windows 7, Windows server 2012 R2 and Windows server 2008 R2. This is because some specific Windows update packages need to be installed manually prior to VMware Tools installation.

    Workaround: Perform the following steps after the guest operating system becomes ready:
    For Windows 7 and Windows server 2008 R2 Guest:

    1. Review the information available here: https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus.
    2. Manually get the windows update, then download and install the required Windows updates, available at https://support.microsoft.com/en-us/help/4474419/sha-2-code-signing-support-update and https://support.microsoft.com/en-us/help/4490628/servicing-stack-update-for-windows-7-sp1-and-windows-server-2008-r2.
    3. Manually install VMware Tools in the guest operating system.

    For Windows server 2012 R2 Guest:

    1. Manually get the windows update, then download and install the Update Package (KB2919355) from https://www.microsoft.com/en-ca/download/details.aspx?id=42334.
    2. Install the .NET 3.5 Framework from Add Roles and Features Wizard.
    3. Manually install VMware Tools in the guest operating system.

    To manually install VMware Tools:

    1. Mount the /Applications/VMware Fusion.app/Contents/Library/isoimages/windows.iso to the virtual machine's CD/DVD, then connect to the CD/DVD.
    2. Open the CD/DVD in guest and install the VMware Tools in the guest operating system.