Re: DPDK Netvsc - RNDIS reports VF but device not found, retrying

[Stephen Hemminger <stephen@networkplumber.org>]

On Tue, 23 Jan 2024 14:34:12 +0200
Oleksandr Nahnybida <oleksandrn@interfacemasters.com> wrote:

> Hello,
> 
> I am trying to set up dpdk with netvsc as master pmd on Azure following
> https://learn.microsoft.com/en-us/azure/virtual-network/setup-dpdk?tabs=ubuntu
> and
> https://doc.dpdk.org/guides-22.11/nics/netvsc.html
> 
> but I have the following error messages
> 
> EAL: VFIO support initialized
> EAL: Probe PCI driver: mlx5_pci (15b3:1018) device: 8565:00:02.0 (socket 0)
> mlx5_net: DV flow is not supported.
> mlx5_common: Failed to allocate DevX UAR (BF/NC)
> mlx5_common: Failed to allocate UAR.
> mlx5_net: Failed to prepare Tx DevX UAR.
> mlx5_net: probe of PCI device 8565:00:02.0 aborted after encountering an
> error: Operation not permitted
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device 8565:00:02.0 cannot be used
> EAL: Probe PCI driver: mlx5_pci (15b3:1018) device: d377:00:02.0 (socket 0)
> mlx5_net: DV flow is not supported.
> mlx5_common: Failed to allocate DevX UAR (BF/NC)
> mlx5_common: Failed to allocate UAR.
> mlx5_net: Failed to prepare Tx DevX UAR.
> mlx5_net: probe of PCI device d377:00:02.0 aborted after encountering an
> error: Operation not permitted
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device d377:00:02.0 cannot be used
> EAL: Probe PCI driver: mlx5_pci (15b3:1018) device: f97e:00:02.0 (socket 0)
> mlx5_net: DV flow is not supported.
> mlx5_common: Failed to allocate DevX UAR (BF/NC)
> mlx5_common: Failed to allocate UAR.
> mlx5_net: Failed to prepare Tx DevX UAR.
> mlx5_net: probe of PCI device f97e:00:02.0 aborted after encountering an
> error: Operation not permitted
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device f97e:00:02.0 cannot be used
> EAL: Bus (pci) probe failed.
> hn_vf_attach(): Couldn't find port for VF
> hn_vf_add(): RNDIS reports VF but device not found, retrying
> hn_vf_attach(): Couldn't find port for VF
> hn_vf_add(): RNDIS reports VF but device not found, retrying
> and so on in a loop
> 
> Also, with debug logs I see
> 
> mlx5_common: DevX read access NIC register=0X9055 failed errno=22 status=0
> syndrome=0
> mlx5_common: DevX read access NIC register=0X9055 failed errno=22 status=0
> syndrome=0
> mlx5_common: DevX read access NIC register=0X9055 failed errno=22 status=0
> syndrome=0
> 
> 
> The DPDK version is 22.11, running on
> Linux dpdk0 5.15.0-1053-azure #61~20.04.1-Ubuntu
> VM type D8ls v5, accelerated networking is on for two ports
> 
> driverctl -b vmbus list-devices
> 
> 000d3a1c-e0df-000d-3a1c-e0df000d3a1c hv_netvsc
> 000d3a1e-4573-000d-3a1e-4573000d3a1e uio_hv_generic [*]
> 000d3a1e-47da-000d-3a1e-47da000d3a1e uio_hv_generic [*]
> 
> 
> Any, ideas what I might be doing wrong? I see the same behavior with
> testpmd and my app.

Looks like a mlx5 driver issue, which kernel driver are you using?
The netvsc code sees a VF but can't use it because of the mlx5 errors.