DPDK usage discussions
 help / color / mirror / Atom feed
From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: "users@dpdk.org" <users@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Cc: "Marjanovic, Nemanja" <nemanja.marjanovic@intel.com>
Subject: mlx5_common: failed to load mlx5_eth driver issue
Date: Tue, 28 Jan 2025 11:15:04 +0000	[thread overview]
Message-ID: <IA1PR11MB629047DBE148DF98ACFBE45DE0EF2@IA1PR11MB6290.namprd11.prod.outlook.com> (raw)

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

Hi Folks,

I am trying to run dpdk-testpmd in a container with NVIDIA ConnectX-7 NIC card on the system and facing issue described below. Details on the system setup are as follow-

Host Configuration for OFED and CX7:
Nvidia CX7 is configured to use Ethernet as opposed to InfiniBand with the following steps:

OFED driver installation:
./mlnxofedinstall --without-dkms --add-kernel-support --kernel 6.8.0-51-generic --without-fw-update --force

Configuration:

mlxconfig -d /dev/mst/mt4129_pciconf0  set LINK_TYPE_P1=2
mlxconfig -d /dev/mst/mt4129_pciconf1  set LINK_TYPE_P1=2

SRIOV has been also enabled on the NIC.

The above configuration resulted in successfully deploying dpdk-testpmd on virtual functions on the host.

Container Configuration for OFED:
Ubuntu 22.04 used within container.

# Install mlnx OFED Drivers
RUN wget https://www.mellanox.com/downloads/ofed/MLNX_OFED-24.07-0.6.1.0/MLNX_OFED_LINUX-24.07-0.6.1.0-ubuntu24.04-x86_64.tgz \
       && tar -xvf MLNX_OFED_LINUX-24.07-0.6.1.0-ubuntu24.04-x86_64.tgz \
       && cd MLNX_OFED_LINUX-24.07-0.6.1.0-ubuntu24.04-x86_64 \
       && ./mlnxofedinstall --force --without-fw-update --dpdk --upstream-libs

Dpdk-testpmd error log:

root@tpmd-0:/tmp/dpdk-build/app# ./dpdk-testpmd -n 4 -a 60:00.1 -a 60:00.2  -- -i
EAL: Detected CPU lcores: 128
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probe PCI driver: mlx5_pci (15b3:101e) device: 0000:60:00.1 (socket 0)
mlx5_net: Unable to recognize master/representors on the multiple IB devices.
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:60:00.1 cannot be used
EAL: Probe PCI driver: mlx5_pci (15b3:101e) device: 0000:60:00.2 (socket 0)
mlx5_net: Unable to recognize master/representors on the multiple IB devices.
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:60:00.2 cannot be used
EAL: Bus (pci) probe failed.
TELEMETRY: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=1163456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done
testpmd> quit


Please provide help to resolve above.


Thanks,
Jasvinder




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

             reply	other threads:[~2025-01-28 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 11:15 Singh, Jasvinder [this message]
2025-01-29  6:33 ` Khadem Ullah
2025-02-24 19:25 ` Tummala, Sivaprasad
2025-02-25  9:34   ` Singh, Jasvinder

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=IA1PR11MB629047DBE148DF98ACFBE45DE0EF2@IA1PR11MB6290.namprd11.prod.outlook.com \
    --to=jasvinder.singh@intel.com \
    --cc=nemanja.marjanovic@intel.com \
    --cc=rasland@nvidia.com \
    --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).