VMware Fusion 12.1.0 | 19 November 2020 | Build 17195230

What's in the Release Notes

The release notes cover the following topics:

About VMware Fusion

VMware Fusion® 12.1.0 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.

  • Software
    macOS 10.15 Catalina and newer versions.

What's New

  • Optimized for macOS 11 Big Sur as host and guest
  • New guest operating system support
    • Windows 10 20H2
    • Ubuntu 20.10
    • RHEL 8.3
    • Fedora 33
  • Fusion health check

​            When VMware Fusion is running on macOS 10.15, the kernel extension issue can be easily fixed by a button click.           

  • Updated vctl kind to support KIND v0.9.0
  • Includes docker-machine-driver-vmware
  • Performance improvements, bug fixes and security updates

Prior Releases

Features and Known Issues from prior releases of VMware Fusion 12 are described in the release notes for each release. To view the release notes for a prior release, click the appropriate link:

Resolved Issues

  • The Exporting Cluster Logs functionality in kind does not work

    The user cannot use kind to export cluster logs for exploring.

    This issue is resolved.

  • The USB Ethernet adapter devices are unable to connect to the guest while using VMware Fusion 12

    The user is unable to pass through the USB Ethernet Adapter devices to the guest while using Fusion 12.

    This issue is resolved.

  • The "Failed to initialize PhoneHome library" error displays

    While trying to run a repair using the vdiskmanager utility in VMware Fusion, the following error displays:

    Failed to initialize PhoneHome library

    This issue is resolved.

  • Nested virtualization is not supported without VMCS shadowing

    Nested virtualization is now supported on the CPU models without the VMCS shadowing feature.

    This issue is resolved.

Known Issues

  • The virtual machine (VM) cannot access the same network as the host while macOS Big Sur host is connected to the virtual private network (VPN)

    If the Big Sur host is connected to VPN, then the VM cannot access the same network as that of the host.

    Workaround: Connect to the VPN in the VM instead of connecting to the VPN on the host.

check-circle-line exclamation-circle-line close-line
Scroll to top icon