From: Asaf Penso <asafp@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
Julien <julien.marcin.tech@gmail.com>,
Maayan Kashani <mkashani@nvidia.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: RE: [mlx5 driver] Usage of mlx5 with unpriviledged LXC container
Date: Wed, 3 Sep 2025 16:09:32 +0000 [thread overview]
Message-ID: <MN0PR12MB60539360B91D8639FB2985FFCD01A@MN0PR12MB6053.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zE77Rz70pFu2VMdQTEiJ03fs0N173RpO0py1CmXwp+wA@mail.gmail.com>
+ @Maayan Kashani, please help here
Regards,
Asaf Penso
>-----Original Message-----
>From: David Marchand <david.marchand@redhat.com>
>Sent: Wednesday, 3 September 2025 18:07
>To: Julien <julien.marcin.tech@gmail.com>
>Cc: users@dpdk.org; Dariusz Sosnowski <dsosnowski@nvidia.com>; Slava
>Ovsiienko <viacheslavo@nvidia.com>; Bing Zhao <bingz@nvidia.com>; Ori
>Kam <orika@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Matan
>Azrad <matan@nvidia.com>
>Subject: Re: [mlx5 driver] Usage of mlx5 with unpriviledged LXC container
>
>On Wed, 3 Sept 2025 at 16:54, Julien <julien.marcin.tech@gmail.com> wrote:
>>
>> 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"?
>
>Sorry, I can't help about such low level details for the mlx5 driver.
>I copied the DPDK mlx5 maintainers, maybe they can help.
>
>However, I am a bit concerned as you are mixing in some DOCA proprietary
>libraries.
>If you need DOCA, you should probably contact the NVIDIA DOCA support
>team.
>
>
>--
>David Marchand
prev parent reply other threads:[~2025-09-03 16:09 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
2025-09-03 15:07 ` David Marchand
2025-09-03 16:09 ` Asaf Penso [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=MN0PR12MB60539360B91D8639FB2985FFCD01A@MN0PR12MB6053.namprd12.prod.outlook.com \
--to=asafp@nvidia.com \
--cc=bingz@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dsosnowski@nvidia.com \
--cc=julien.marcin.tech@gmail.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=users@dpdk.org \
--cc=viacheslavo@nvidia.com \
/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).