From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [RFC] net/vdev_netvsc: disable auto-detection by default
Date: Tue, 24 Feb 2026 06:41:10 -0800 [thread overview]
Message-ID: <20260224064110.1d65ef69@phoenix.local> (raw)
In-Reply-To: <CAJFAV8z0oo6zUdfYJDPJe8pJCkpZ4WVyABn0Xq1=EN=s+6givA@mail.gmail.com>
On Tue, 24 Feb 2026 08:58:45 +0100
David Marchand <david.marchand@redhat.com> wrote:
> On Tue, 24 Feb 2026 at 08:41, David Marchand <david.marchand@redhat.com> wrote:
> >
> > On Tue, 24 Feb 2026 at 02:43, Stephen Hemminger
> > <stephen@networkplumber.org> wrote:
> > >
> > > The vdev_netvsc driver auto-injects itself on Hyper-V via an
> > > RTE_INIT constructor. This interferes with tests on github actions
> > > which uses Azure where the driver probes in forked subprocesses
> > > and crashes on uninitialized interrupt instances.
> > >
> > > Guard the auto-detection behind RTE_LIBRTE_VDEV_NETVSC_AUTO
> > > (disabled by default). The driver must now be explicitly
> > > requested with --vdev=net_vdev_netvsc.
> > >
> > > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> >
> > The failure in GHA can be avoided with a simpler:
> > https://patchwork.dpdk.org/project/dpdk/patch/20260223155603.3651641-1-david.marchand@redhat.com/
>
> After rerunning with debug, the vdev netvsc is still probed, but is
> not at fault for the recent failures we saw.
>
> VMBUS_BUS: vmbus_probe_one_driver(): VMBUS device
> 7c1e52d8-3f86-7c1e-52d8-3f867c1e52d8 on NUMA socket -1
> VMBUS_BUS: rte_vmbus_map_device(): Not managed by UIO driver, skipped
> VDEV_BUS: vdev_probe_all_drivers(): Search driver to probe device net_ring0
> VDEV_BUS: vdev_probe_all_drivers(): Search driver to probe device
> net_vdev_netvsc
> DPAA2_BUS: fslmc_vfio_close_group: Get fd by name((null)) failed(-19)
> DPAA2_BUS: Unable to close devices -19
> DPAA_BUS: dpaa_bus_cleanup(): >>
> DPAA_BUS: Portal already cleaned
> DPAA_BUS: dpaa_bus_cleanup(): Bus cleanup done
> Calling recursive action for test_invalid_vdev_flag
> Returned from recursive action for test_invalid_vdev_flag with 0
> Cleaning up /home/runner/work/dpdk/dpdk/build/app/dpdk-test recursive instance
> /home/runner/work/dpdk/dpdk/build/app/dpdk-test recursive instance returning 0
> Test OK
> RTE>>
The DPAA_BUS looks like noise.
And also VMBUS.
Maybe we need a --no-bus flag that shuts off all buses?
next prev parent reply other threads:[~2026-02-24 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:42 [RFC] net/vdev_netvsc: disable auto-detection by default Stephen Hemminger
2026-02-24 7:41 ` David Marchand
2026-02-24 7:58 ` David Marchand
2026-02-24 14:41 ` Stephen Hemminger [this message]
2026-02-24 14:44 ` David Marchand
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=20260224064110.1d65ef69@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=matan@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