Description of Release

This document contains information on the accompanying Intel® QuickAssist Technology (Intel® QAT) Hardware Version 2.0 Driver for VMware ESXi*.

This software enables Intel® QuickAssist Technology (Intel® QAT) accelerator on VMware ESXi. Driver enables sharing of a Physical Function (PF) across multiple guest Virtual Machines (VM) using Single Root I/O Virtualization (SR-IOV) technology. This is accomplished by exposing Intel® QAT accelerator as Virtual Devices (VDEVs) to a specific guest VM(s) via Enhanced DirectPath I/O.

For instructions on loading and running the release software, refer to the README.txt file in the corresponding released software package. For instructions on installing the driver in the Guest Operating System (OS), refer to corresponding guest driver’s collaterals listed in the Related Documentation section.

Refer to the Revision History to check the changes in this document.

Note

These release notes may include known issues with third-party or reference platform components that affect the operation of the software.

Features

  • Sym/Asym Crypto

  • TLS1.3 elliptical curves Montgomery encryption (curve 25519 and curve 448)

  • Data Compression with CnV for Deflate and LZ4/LZ4s algorithms and CnVnR for Deflate and LZ4s

  • LZ4 E2E CRC32 with CNV enforcement enabled

  • Chaining support

  • SM3/SM4

  • Asynchronous E2E support for compression

  • Telemetry

  • Power Management

  • Extended RAS (uncorrectable and fatal error support)

  • Ratelimiting

  • Intel® Device Manager for VMware* vCenter Server support

  • Enhanced DirectPath I/O via SR-IOV

  • VMware vSphere* vMotion* support

Limitations

  • Symmetric services are not configured by default. Refer to the Driver configuration - Services section in README.txt for additional information.

  • Stateful decompression is not supported.

  • Intel® Key Protection Technology (KPT) is not currently supported.

  • Auto-select best (ASB) is not supported with rolling XXHash32.

  • Dynamic Power Management (DPM) is not currently supported.

  • Shared Virtual Memory (SVM) and Address Translation (AT) are not currently supported.

  • ESXi limitation: number of PCI passthrough devices per VM is limited. Check “ESXi/ESX Configuration Maximums” KB article for exact limits. ESXi will not allow to power on VM if such limit is exceeded.

  • Non-Enhanced DirectPath I/O driver, also known as DirectPath I/O or just SR-IOV driver is not supported anymore. Switching to this release will require next steps: “XXXX QAT VF” PCI device (with access type DirectPath I/O) should be removed from VM config and replaced by “XXXX QAT VF Device” (with access type Enhanced DirectPath I/O). In configuration options of “XXXX QAT VF Device” appropriate/desired configuration should be selected. No changes inside VM are required.

  • Enhanced DirectPath I/O via Intel® Scalable IOV is not supported anymore. Switching to this release will require next steps: “* vQAT Device” PCI device (with access type Enhanced DirectPath I/O) should be removed from VM config and replaced by “XXXX QAT VF Device” (with access type Enhanced DirectPath I/O). In configuration options of “XXXX QAT VF Device” appropriate/desired configuration should be selected. Inside VM, configuration file for vQAT should be replaced by one for VF. Please refer to Guest driver documentation for general information about device configuration.

Packages Information

Enhanced DirectPath I/O package

Package Name

qat-2.0_ext_rel_bin_2.6.6.170-8.0.3-24022510-dvx.tar.gz

Release Date

04/11/2025

Supported Hardware

  • 4th Generation Intel® Xeon® Scalable Processor (4xxx QAT)

  • 5th Generation Intel® Xeon® Scalable Processor (4xxx QAT)

  • Intel® Xeon® 6 Processor (4xxx QAT)

Supported ESXi Version(s)

  • 8.0 Update 3 and newer

Driver Version

1002.6.6.170

Package Checksum

SHA256: 98107c75eee93f78 655914fc4fa3f108 28ba293e95a6447c f6f6777c7a3d42c2

List of Files in Release

File

Description

qat-2.0_ext_rel_bin_2.6.6.170-8.0.3-24022510-dvx.tar.gz

Enhanced DirectPath I/O driver

Also every package includes LICENSE.txt and README.txt files with licensing and basic driver installation and configuration information correspondingly.

Supported Guest Drivers

The software in this release has been validated against the following guest drivers:

  • Linux*: Intel QAT driver QAT20.L.1.2.30-*

  • Windows*: Intel QAT driver QAT2.0.W.2.5.0-*

The actual list of supported guest OS depends on the guest driver compatibility. Refer to the corresponding documentation for more information.

Technical Support

Intel offers only support for this software at the Application Programming Interface (API) level, defined in the Programmer’s Guide and API reference manuals listed in the Related Documentation section.

For technical support, including answers to questions not addressed in this document, visit the technical support forum, FAQs, and other support information at Intel Support.

VMware forwards all issues they suspect to be related to Intel QAT to Intel to help triage and resolve with the customer directly.

Environmental Assumptions

The following assumptions are made about the deployment environment:

  • The driver object/executable file on the disk should be protected using the normal file protection mechanisms so it is writable by only trusted users, for example, a privileged user or an administrator.

  • The public key firmware image on the disk should be protected using normal file protection mechanisms, so it is writable only by trusted users; for example, a privileged user or an administrator.

  • The Intel QAT device should not be exposed to untrusted users through the user space direct deployment model.

  • The Dynamic Random-Access Memory (DRAM) is considered to be inside the trust boundary. The traditional memory-protection schemes provided by the Intel architecture processor and memory controller, and by the OS, are to prevent unauthorized access to these memory regions.

  • Persistent keys were not considered, but the storage media are also considered inside the cryptographic boundary.

  • The driver-exposed device file should be protected using the normal file protection mechanisms so that only trusted users can open, read or write it.