From: Thomas Monjalon <thomas@monjalon.net>
To: bb <becauseof86@163.com>
Cc: users@dpdk.org, dev@dpdk.org, dmitry.kozliuk@gmail.com,
ming3.li@intel.com, pallavi.kadam@intel.com,
Gena Tertychnyi <genter@microsoft.com>,
Andre Muezerie <andremue@linux.microsoft.com>,
greg.cusanza@microsoft.com,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Itai Sharoni <isharoni@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: Windows 10/11 x64 signed NetUIO and virt2phys packages
Date: Thu, 20 Aug 2026 12:49:48 +0200 [thread overview]
Message-ID: <cGq2-0faQ9iJv0T0f8ECAA@monjalon.net> (raw)
In-Reply-To: <1edaac48.4371.1a01dcd3974.Coremail.becauseof86@163.com>
Hello,
Thank you for the catch and the good questions.
We need answers from Microsoft, Intel and NVIDIA.
Please see below
20/08/2026 08:13, bb:
> Dear DPDK Windows maintainers and users,
>
> We are evaluating DPDK for production deployment on Windows 10 x64 and Windows 11 x64.
>
> Our hardware includes Intel XL710 adapters, NVIDIA/Mellanox ConnectX adapters using the mlx5 PMD, and other PCIe network adapters.
>
> We need precompiled, production-ready, Microsoft-signed or WHQL-certified x64 installation packages for:
>
> 1. NetUIO
> 2. virt2phys
>
> The NetUIO README currently states that a WHQL-signed NetUIO driver can be requested from dpdkwin@microsoft.com:
>
> https://git.dpdk.org/dpdk-kmods/tree/windows/netuio/README.rst
>
> However, that address is no longer valid. Microsoft rejected the message with:
>
> 550 5.4.1 Recipient address rejected: Access denied
I think there is a signing procedure here:
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/whql-release-signature
Unfortunately, after 7 years since first introduction of Windows support,
the roadmap still mentions "inbox kernel-mode driver" in "Future (unscheduled)".
> Could you please confirm:
>
> 1. Whether signed NetUIO and virt2phys packages currently exist for Windows 10/11 x64.
Anyone from Microsoft can answer please?
> 2. Whether they are publicly downloadable or available through a vendor or commercial support channel.
Anyone from Microsoft can answer please?
> 3. The current contact responsible for obtaining these packages.
We really need to state who is responsible in Microsoft.
> 4. Whether NetUIO supports Intel XL710/E810 and other PCI device IDs in a signed package.
The question refers to i40e and ice drivers support on Windows.
Someone from Intel to answer please?
> 5. Whether virt2phys is still required for mlx5 with WinOF-2,
It is said "required by hardware PMDs" but I am not sure it is true with IOVA-as-VA.
We should explain this clearly in
https://doc.dpdk.org/guides/windows_gsg/run_apps.html#install-drivers
> or whether IOVA-as-VA is officially supported in production.
It is not said it is officially supported, but I suppose it should work.
Someone from NVIDIA to confirm please?
> 6. Whether the packages support Secure Boot and HVCI / Windows Memory Integrity.
> 7. Whether redistribution with a commercial application is permitted.
> 8. Whether the obsolete dpdkwin@microsoft.com address can be removed or replaced in the dpdk-kmods documentation.
We need Microsoft support for these questions.
> Relevant source and documentation:
>
> NetUIO:
> https://git.dpdk.org/dpdk-kmods/tree/windows/netuio
>
> virt2phys:
> https://git.dpdk.org/dpdk-kmods/tree/windows/virt2phys
>
> Windows driver documentation:
> https://git.dpdk.org/dpdk-kmods/tree/windows/README.rst
>
> DPDK Windows requirements:
> https://doc.dpdk.org/guides/windows_gsg/run_apps.html
>
> DPDK mlx5 documentation:
> https://doc.dpdk.org/guides/nics/mlx5.html
>
> Thank you for any current information or contact details you can provide.
>
> Best regards,
prev parent reply other threads:[~2026-08-20 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 6:13 Windows 10/11 x64 signed NetUIO and virt2phys packages - listed Microsoft contact is no longer valid bb
2026-08-20 10:49 ` Thomas Monjalon [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=cGq2-0faQ9iJv0T0f8ECAA@monjalon.net \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=andremue@linux.microsoft.com \
--cc=becauseof86@163.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dsosnowski@nvidia.com \
--cc=genter@microsoft.com \
--cc=greg.cusanza@microsoft.com \
--cc=isharoni@nvidia.com \
--cc=ming3.li@intel.com \
--cc=pallavi.kadam@intel.com \
--cc=talshn@nvidia.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