Can not set inner/outer tpid for qinq filtering on VF (-95 error).

Can not set inner/outer tpid for qinq filtering on VF (-95 error).

[James B]

Hello,

I would like to set up a vf with qinq filtering. My setup is this: I
have an E810 NIC (which uses the ice driver), which I create a child
VF for. The VF is bound to the vfio-pci driver.
I am using testpmd to test/evaluate my setup. Here are the steps I'm
following for setup:
https://edc.intel.com/content/www/us/en/design/products/ethernet/config-guide-e810-dpdk/q-in-q-support

The issue is, once I get to the step where you set the tpid, it fails:

testpmd> vlan set filter on 0
testpmd> vlan set extend on 0
testpmd> vlan set inner tpid 0x8100 0
tx_vlan_tpid_set(port_pi=0, vlan_type=1, tpid=33024) failed diag=-95
testpmd> vlan set outer tpid 0x8100 0
tx_vlan_tpid_set(port_pi=0, vlan_type=2, tpid=33024) failed diag=-95
testpmd>

Here is some additional information about my setup:

Network card:
    Intel E832-L

Linux kernel:
   5.15

Ice driver version:
    Tried 1.11.14, 1.11.17, and 1.12.7

DPDK version:
   Tried both 23.03 and 22.11

Ethtool settings:
    ethtool -k eno1
Features for eno1:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: on
        tx-checksum-ip-generic: off [fixed]
        tx-checksum-ipv6: on
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: on
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
        tx-tcp-segmentation: on
        tx-tcp-ecn-segmentation: on
        tx-tcp-mangleid-segmentation: off
        tx-tcp6-segmentation: on
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: on
receive-hashing: on
highdma: on
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: on
tx-gre-csum-segmentation: on
tx-ipxip4-segmentation: on
tx-ipxip6-segmentation: on
tx-udp_tnl-segmentation: on
tx-udp_tnl-csum-segmentation: on
tx-gso-partial: on
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: on
tx-gso-list: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off
rx-vlan-stag-hw-parse: off
rx-vlan-stag-filter: on
l2-fwd-offload: off
hw-tc-offload: off
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: on
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]

Ethtool private flags:
    ethtool --show-priv-flags eno1
Private flags for eno1:
link-down-on-close           : off
fw-lldp-agent                : off
channel-inline-fd-mark       : off
channel-pkt-inspect-optimize : on
channel-pkt-clean-bp-stop    : off
channel-pkt-clean-bp-stop-cfg: off
vf-true-promisc-support      : on
mdd-auto-reset-vf            : off
vf-vlan-pruning              : off
legacy-rx                    : off
cgu_fast_lock                : off
dpll_monitor                 : off
extts_filter                 : off
itu_g8262_filter_used        : off
allow-no-fec-modules-in-auto : off

link information:
ip link show eno1
6: eno1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq
state UP mode DEFAULT group default qlen 1000
    link/ether 00:e0:4b:78:65:24 brd ff:ff:ff:ff:ff:ff
    vf 0     link/ether 00:11:22:33:44:11 brd ff:ff:ff:ff:ff:ff, spoof
checking off, link-state auto, trust on
    altname enp244s0f0

Has anyone encountered this error before? I'm hoping that I'm just
missing some configuration setting. Given that I've tried multiple ice
drivers and multiple dpdk versions, I'm starting to fear this is a
hardware limitation, despite this not being mentioned in the intel
guide.

Thank you for your help,
James