ADQ VF Known Issues
- Core-level reset of an ADQ-configured VF port (rare events usually triggered by other failures in the NIC/iavf driver) results in loss of ADQ configuration. To recover, reapply ADQ configuration to the VF interface.
- iavf driver must use Trusted mode with ADQ: Trusted mode must be enabled for ADQ inside a VF. If TC filters are created on a VF interface with trusted mode off, the filters are added to the software table but are not offloaded to the hardware.
- VF supports Max Transmit Rate only: iavf driver only supports setting maximum transmit rate (max_rate) for Tx traffic. Minimum transmit rate (min_rate) setting is not supported with a VF.
- VF Max Transmit Rate: The tc qdisc add command on a VF interface does not verify that max_rate value(s) for the TCs are specified in increments of 500 Kb/s. TC max_rate is expected to be a multiple of (or equal to) 500 Kb/s.
- VF errors when deleting TCs or unloading iavf driver in a VF: ice and iavf driver error messages might get triggered in a VF when TCs are configured, and TCs are either manually deleted or the iavf driver is unloaded. Reloading the ice driver recovers the driver states.
- VF Max Transmit Rate: When a maximum TX transmit rate is specified in the tc qdisc add command on a VF interface, the max rate does not get applied correctly causing inconsistent TX rate limit for some applications.
- The system reboots/crashes when the number of queues on the VF interface is changed using the ethtool command while traffic is flowing from client to SUT, using ice driver version 1.10.X and iavf version 4.6.X.
Mitigation: After the TCs have been created, add at least 2 seconds of sleep time.