DPDK usage discussions
 help / color / mirror / Atom feed
From: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
To: stephen@networkplumber.org
Cc: users@dpdk.org
Subject: Re: DPDK Netvsc - RNDIS reports VF but device not found, retrying
Date: Tue, 23 Jan 2024 19:51:33 +0200	[thread overview]
Message-ID: <CAAFk=6CCCCN=rBANxCSG348orn78b=RjC-DDcDf7gUApdWkTKA@mail.gmail.com> (raw)
In-Reply-To: <20240123083208.32900f39@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 3720 bytes --]

azureuser@dpdk0:~$ ethtool -i enP47056s2
driver: mlx5_core
version: 5.15.0-1053-azure
firmware-version: 16.30.1284 (MSF0000000012)
expansion-rom-version:
bus-info: b7d0:00:02.0

I also installed rdma-core/libibverbs1 (dpdk was compiled
with  ibverbs_link=shared)

azureuser@dpdk0:~$ apt-cache policy rdma-core
rdma-core:
  Installed: 28.0-1ubuntu1
azureuser@dpdk0:~$ apt-cache policy libibverbs1
libibverbs1:
  Installed: 28.0-1ubuntu1

On Tue, Jan 23, 2024 at 6:32 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> 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.
>

[-- Attachment #2: Type: text/html, Size: 4682 bytes --]

  reply	other threads:[~2024-01-23 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 12:34 Oleksandr Nahnybida
2024-01-23 16:32 ` Stephen Hemminger
2024-01-23 17:51   ` Oleksandr Nahnybida [this message]
2024-01-23 18:13     ` Stephen Hemminger
2024-01-23 19:06       ` Oleksandr Nahnybida
2024-01-24  1:33         ` Stephen Hemminger
2024-01-25 11:36           ` Oleksandr Nahnybida

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAFk=6CCCCN=rBANxCSG348orn78b=RjC-DDcDf7gUApdWkTKA@mail.gmail.com' \
    --to=oleksandrn@interfacemasters.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).