From: Julien <julien.marcin.tech@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: users@dpdk.org
Subject: Re: [mlx5 driver] Usage of mlx5 with unpriviledged LXC container
Date: Wed, 3 Sep 2025 16:54:37 +0200 [thread overview]
Message-ID: <CAHD7jhES5pLcWLuA84JbYnva8atXzGAsxcgfkXTYWb7KWVMFNA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yt9F_bSXkWA=j=fN+0Wou2BCeQxWnuOjaymbLYM+6cVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]
Thank you for the response.
Yes, these capabilities are necessary in order to run dpdk-testpmd inside a
container. However, they are not sufficient.
I tried again with a 6.8 kernel and the Nvidia tools/libraries suite:
"doca-host_3.1.0-091000-25.07-ubuntu2404_amd64.deb".
The log is more informative this time: "mlx5_common: DevX create TIS failed
errno=121 status=0x3 syndrome=0x6a6678".
Do you have any idea how to investigate this issue, especially regarding
"status" and "syndrome"?
On Mon, Aug 25, 2025 at 2:24 PM David Marchand <david.marchand@redhat.com>
wrote:
> On Mon, 25 Aug 2025 at 14:09, Julien <julien.marcin.tech@gmail.com> wrote:
> >
> > Hello,
> > I have a question about using the mlx5 driver with LXC.
> > I'm trying to use dpdk-testpmd in an LXC container whose root user isn't
> mapped to the host's root user.
> > Note: The entire physical interface is given to the LXC container, not a
> virtual interface.
> >
> > The following error occured:
> > mlx5_common: DevX create TIS failed errno=22 status=0 syndrome=0
> > mlx5_net: Failed to create TIS 0/0 for [bonding] device mlx5_2.
> > mlx5_net: TIS allocation failure
> > mlx5_net: probe of PCI device 0000:27:00.0 aborted after encountering an
> error: Cannot allocate memory
> > mlx5_common: Failed to load driver mlx5_eth
> > EAL: Requested device 0000:27:00.0 cannot be used
> > EAL: Bus (pci) probe failed.
> >
> > The "transport_domain" is created, and the mlx5_devx_cmd_create_td()
> function runs normally.
> > The call to mlx5dv_devx_obj_create() receives an errno of 22.
> >
> > I don't encounter any problems when the container's root user is mapped
> to the host's root user.
> > Has anyone experienced this before?
> > Is it possible to use the driver in an unprivileged LXC container?
>
> There is probably something missing in terms of capabilities.
> I don't know how LXC behaves in this regard.
>
> I suggest you look at "5.5.1.5. Run as Non-Root" in
> https://doc.dpdk.org/guides/platform/mlx5.html.
>
>
> --
> David Marchand
>
>
[-- Attachment #2: Type: text/html, Size: 2835 bytes --]
next prev parent reply other threads:[~2025-09-04 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 15:38 Julien
2025-08-25 12:24 ` David Marchand
2025-09-03 14:54 ` Julien [this message]
2025-09-03 15:07 ` David Marchand
2025-09-03 16:09 ` Asaf Penso
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=CAHD7jhES5pLcWLuA84JbYnva8atXzGAsxcgfkXTYWb7KWVMFNA@mail.gmail.com \
--to=julien.marcin.tech@gmail.com \
--cc=david.marchand@redhat.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).