From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1569] dpdk-devbind not recognizing Hyper-V synthetic network adapters
Date: Mon, 21 Oct 2024 08:39:42 +0000 [thread overview]
Message-ID: <bug-1569-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1569
Bug ID: 1569
Summary: dpdk-devbind not recognizing Hyper-V synthetic network
adapters
Product: DPDK
Version: 24.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: ofer.d@claroty.com
Target Milestone: ---
Hello,
A client of our installed on a Hyper-V Ubuntu VM a synthetic network adapter.
It looks really strange. For example, in `lspci` we don't see any network
adapters, but in `lshw -class network` we do see them.
I see that dpdk-devbind is iterating on the PCIs, I assume that similarly to
lspci, so it doesn't find them either.
Is there a way to solve it in dpdk, or is it simply not supported? Would
changing it to emulated network adapter should work?
Thanks ahead
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2932 bytes --]
next reply other threads:[~2024-10-21 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 8:39 bugzilla [this message]
2024-10-21 15:46 ` bugzilla
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-1569-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).