Vmware Fusion Opengl


VMware Workstation running on Linux or Windows and VMware Fusion running on MacOS are all supported. With the August 2015 Workstation 12 / Fusion 8 releases, OpenGL 3.3 is supported in the guest.

This page describes how to build, install and use theVMware guest GL driver (aka the SVGA orSVGA3D driver) for Linux using the latest source code. This driver givesa Linux virtual machine access to the host’s GPU forhardware-accelerated 3D. VMware Workstation running on Linux or Windowsand VMware Fusion running on MacOS are all supported.

With the August 2015 Workstation 12 / Fusion 8 releases, OpenGL 3.3 issupported in the guest. This requires:

  • The VM is configured for virtual hardware version 12.

  • The host OS, GPU and graphics driver supports DX11 (Windows) orOpenGL 4.0 (Linux, Mac)

  • On Linux, the vmwgfx kernel module must be version 2.9.0 or later.

  • A recent version of Mesa with the updated svga Gallium driver.

Otherwise, OpenGL 2.1 is supported.

With the Fall 2018 Workstation 15 / Fusion 11 releases, additionalfeatures are supported in the driver:

For Pete's sake, they've had almost a full year and still there's no experimental support for OpenGL. This DirectX crap is really just for game support for all intents and purposes. Having used both Fusion and Parallels, VMware is wasting it's time trying to compete with Parallels on the game compatibility. VMware Workstation 16 and Fusion 12 have been announced this week. Both products offer new features and capabilities for IT Admins, Developers, and everyone else. The key focus of these two releases is containers support, vSphere 7 Compatibility, DirectX 11 and OpenGL 4.1, USB 3.1 Support, and more!

  • Multisample antialiasing (2x, 4x)

  • GL_ARB/AMD_draw_buffers_blend

  • GL_ARB_sample_shading

  • GL_ARB_texture_cube_map_array

  • GL_ARB_texture_gather

  • GL_ARB_texture_query_lod

  • GL_EXT/OES_draw_buffers_indexed

This requires version 2.15.0 or later of the vmwgfx kernel module andthe VM must be configured for hardware version 16 or later.

Vmware fusion free trial

OpenGL 3.3 support can be disabled by setting the environment variableSVGA_VGPU10=0. You will then have OpenGL 2.1 support. This may be usefulto work around application bugs (such as incorrect use of the OpenGL 3.xcore profile).

Most modern Linux distros include the SVGA3D driver so end usersshouldn’t be concerned with this information. But if your distro lacksthe driver or you want to update to the latest code these instructionsexplain what to do.

For more information about the X components see these wiki pages atx.org:


The components involved in this include:

  • Linux kernel module: vmwgfx

  • X server 2D driver: xf86-video-vmware

  • User-space libdrm library

  • Mesa/Gallium OpenGL driver: “svga”

All of these components reside in the guest Linux virtual machine. Onthe host, all you’re doing is running VMwareWorkstation orFusion.


  • Kernel version at least 2.6.25

  • Xserver version at least 1.7

  • Ubuntu: For Ubuntu you need to install a number of builddependencies.

  • Fedora: For Fedora you also need to install a number of builddependencies.

Depending on your Linux distro, other packages may be needed. Mesonshould tell you what’s missing.

Getting the Latest Source Code¶

Begin by saving your current directory location:

  • Mesa/Gallium main branch. This code is used to build libGL, and thedirect rendering svga driver for libGL, vmwgfx_dri.so, and the Xacceleration library libxatracker.so.x.x.x.

  • VMware Linux guest kernel module. Note that this repo contains thecomplete DRM and TTM code. The vmware-specific driver is really onlythe files prefixed with vmwgfx.

  • libdrm, a user-space library that interfaces with DRM. Most distrosship with this but it’s safest to install a newer version. To get thelatest code from Git:

  • xf86-video-vmware. The chainloading driver, vmware_drv.so, the legacydriver vmwlegacy_drv.so, and the vmwgfx driver vmwgfx_drv.so.

Vmware Opengl Support


Building the Code¶

  • Determine where the GL-related libraries reside on your system andset the LIBDIR environment variable accordingly.

    For 32-bit Ubuntu systems:

    For 64-bit Ubuntu systems:

    For 32-bit Fedora systems:

    For 64-bit Fedora systems:

  • Build libdrm:

  • Build Mesa and the vmwgfx_dri.so driver, the vmwgfx_drv.so xorgdriver, the X acceleration library libxatracker. The vmwgfx_dri.so isused by the OpenGL libraries during direct rendering, and by the Xorgserver during accelerated indirect GL rendering. The libxatrackerlibrary is used exclusively by the X server to do render, copy andvideo acceleration:

    The following configure options doesn’t build the EGL system.

    Note that you may have to install other packages that Mesa dependsupon if they’re not installed in your system. You should be toldwhat’s missing.

  • xf86-video-vmware: Now, once libxatracker is installed, we proceedwith building and replacing the current Xorg driver. First check ifyour system is 32- or 64-bit.

  • vmwgfx kernel module. First make sure that any old version of thiskernel module is removed from the system by issuing

    Build and install:

    If you’re using a Ubuntu OS:

    If you’re using a Fedora OS:

    Add ‘vmwgfx’ to the /etc/modules file:


    some distros put DRM kernel drivers in different directories.For example, sometimes vmwgfx.ko might be found in/lib/modules/{version}/extra/vmwgfx.ko or in/lib/modules/{version}/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko.

    After installing vmwgfx.ko you might want to run the followingcommand to check that the new kernel module is in the expected place:

    If you see the kernel module listed in more than one place, you mayneed to move things around.

    Finally, if you update your kernel you’ll probably have to rebuildand reinstall the vmwgfx.ko module again.

Now try to load the kernel module by issuing

Then type

to watch the debug output. It should contain a number of lines prefixedwith “[vmwgfx]”.

Then restart the Xserver (or reboot). The lines starting with“vmwlegacy” or “VMWARE” in the file /var/log/Xorg.0.log should now havebeen replaced with lines starting with “vmwgfx”, indicating that the newXorg driver is in use.

Running OpenGL Programs¶


In a shell, run ‘glxinfo’ and look for the following to verify that thedriver is working:

If you don’t see this, try setting this environment variable:

then rerun glxinfo and examine the output for error messages.

If OpenGL 3.3 is not working (you only get OpenGL 2.1):

  • Make sure the VM uses hardware version 12.

  • Make sure the vmwgfx kernel module is version 2.9.0 or later.

  • Check the vmware.log file for errors.

  • Run ‘dmesg grep vmwgfx’ and look for “DX: yes”.

VMware Fusion 12 14 September 2020 Build 16880131

What's in the Release Notes

The release notes cover the following topics:

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

Vmware Fusion Free Trial

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

Vmware Fusion Opengl 4.3

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

Resolved Issues

Vmware Fusion Opengl

  • 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 Fusion Opengl Support

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