From: David Marchand <david.marchand@redhat.com>
To: Julien <julien.marcin.tech@gmail.com>
Cc: users@dpdk.org
Subject: Re: [mlx5 driver] Usage of mlx5 with unpriviledged LXC container
Date: Mon, 25 Aug 2025 14:24:11 +0200 [thread overview]
Message-ID: <CAJFAV8yt9F_bSXkWA=j=fN+0Wou2BCeQxWnuOjaymbLYM+6cVQ@mail.gmail.com> (raw)
In-Reply-To: <CAHD7jhEnj9e7tkjJTjSFWoi373A4jem0S3H9Pn0aguq5UxhrMQ@mail.gmail.com>
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
prev parent reply other threads:[~2025-08-25 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 15:38 Julien
2025-08-25 12:24 ` David Marchand [this message]
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='CAJFAV8yt9F_bSXkWA=j=fN+0Wou2BCeQxWnuOjaymbLYM+6cVQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=julien.marcin.tech@gmail.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).