From: bugzilla-daemon@kernel.org
To: linux-rdma@vger.kernel.org
Subject: [Bug 220280] New: mlx5 VF node_guid stays 0 in host
Date: Fri, 27 Jun 2025 09:58:11 +0000 [thread overview]
Message-ID: <bug-220280-11804@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220280
Bug ID: 220280
Summary: mlx5 VF node_guid stays 0 in host
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Infiniband/RDMA
Assignee: drivers_infiniband-rdma@kernel-bugs.osdl.org
Reporter: axel@gembe.net
Regression: No
I have a mlx5 setup with switchdev and SR-IOV and I want to make RDMA work
using a VF in the host. VFs attached to a VM work fine, but using the same VF
in the host works for networking but not for RDMA. It seems that this does not
work because the node GUID as shown in `ibv_devices` stays zero. I found a
workaround for this using the following:
> devlink port # find your VF in the list here and copy the id
> devlink port function set pci/0000:10:00.1/65537 hw_addr 72:e4:64:e0:87:a0
> rmmod mlx5_ib
> modprobe mlx5_ib
> ibv_devices # should show a non-zero node_guid for the VF now
https://forums.developer.nvidia.com/t/how-to-use-vf-on-host/277750/4?u=derago
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2025-06-27 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-220280-11804@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-rdma@vger.kernel.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