Release Updates

Known Issues

Title	[Firmware] Shared Virtual Memory (SVM) and Address Translation (AT) disabled
Reference	QAT20-23616
Description	When running QAT workloads with AT enabled under loaded traffic conditions, memory page corruption may occur. Intel is looking at a possible workaround for the problem, and until then the QAT firmware/Driver will not make use of or enable SVM with AT.
Implication	It is not currently possible to run with SVM and AT.
Resolution	Current workaround is disabling SVM and AT.

Title	[MCC] MCC SKUs may consume more power than expected
Reference	QAT20-18924
Description	Due to Power Management changes in MCC platforms one QAT device in every socket is permanently clock gated when not processing requests which leads to inevitable heartbeat failures and device resets. Current FW workaround increases power consumption by keeping QAT in active state. Intel is working on workaround that does not have impact on power consumption.
Implication	Higher power consumption is possible.
Resolution	There is no workaround currently available.

Title	[XCC/MCC] Spurious heartbeat failures may be observed on some SKUs
Reference	QAT20-20272
Description	Time tracking in FW is inaccurate due to power management causing that frequency of HW counter that is used as reference for time measurements appears lower than expected. This may lead to delayed heartbeat and telemetry updates when devices become idle. Intel is working on workaround that removes dependency on the HW counter.
Implication	No functional impact, these messages can be ignored.
Resolution	There is no workaround currently available.

Title	Virtual device power on inside Guest causing VM crash conditions
Reference	VQQ-1907
Description	If user will toggle power for virtual PCI device off and then on inside Guest OS, that will cause VM emergency shutdown due issues in VMware ESXi*.
Implication	User may lose unsaved data inside VM.
Resolution	Avoid toggling power for the virtual PCI device. Use latest version of VMware ESXi where this issue will be resolved.

Title	Driver may accept incorrect service mask configuration and treat it as default configuration.
Reference	VQQ-1618
Description	Service mask parsing may interpret incorrect service mask passed to driver as a valid mask that matches the default configuration and still proceed with driver attachment.
Implication	User will be not notified about incorrect service mask. Also device will fall back to the default configuration.
Resolution	User should configure service masks as described in the driver’s documentation.

Title	Incompatibility between legacy 1.X and 2.0 drivers
Reference	VQQ-1553
Description	1.7 driver (version 1.1.0.7) couldn’t be installed on the same system with 2.0 driver. They are using same namespaces and will conflict, so one of the drivers will fail initialization.
Implication	Only one of the driver could be installed on the system.
Resolution	Use updated 1.X driver, starting from version 1.5.0* it’s fully compatible with driver for QAT 2.0.

Title	VM with enabled vIOMMU may crash with IOMMU fault
Reference	VQQ-1542
Description	QAT usecases that require vIOMMU to be enabled for the guest are currently not supported due issue in VMware ESXi*. Running such workload inside VM may cause it’s to stop responding and reported in VMware ESXi logs as IOMMU pagefault.
Implication	Workloads that require vIOMMU will crash VM.
Resolution	Avoid enabling vIOMMU. Use the latest version of VMware ESXi where this issue resolved, like 8.0 Update 2 or 7.0 Update 3q.

Title	Driver may leak memory if virtual device creation failed under certain conditions
Reference	VQQ-2128
Description	Under certain conditions if driver fails to create virtual device for Enhanced DirectPath I/O it may leak memory.
Implication	It will be impossible to recover HW from fatal error as described in the README file, without restarting system.
Resolution	There is no workaround currently available.