DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Liwu Liu <liwuliu@fortinet.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] TX fails for Intel 550 and 710 PMD on Hyper-V guests
Date: Wed, 19 Aug 2020 11:11:35 -0700	[thread overview]
Message-ID: <20200819111135.2428eaaa@hermes.lan> (raw)
In-Reply-To: <e362fcf68c294f4097d26d2ff6253419@fortinet.com>

On Wed, 19 Aug 2020 17:42:46 +0000
Liwu Liu <liwuliu@fortinet.com> wrote:

> Hi Team,
>    My DPDK project uses Intel 550 and 710 virtual functions PMD under Windows Hyper-V environment.
>    Somehow I found out that the VM guest has TX side failing to send out any frame-I guess Windows host side turns on
> Malicious Device Detection feature, for which DPDK PMD's refuse to work with. Though Intel 520 PMD works well.. My questions:
> (1)    Has anyone succeeded to drive Intel 550/710 PMD under Hyper-V environment?

Have not tried those NIC's. Have tried other Intel NIC.
You should check that reported PCI id values match those in DPDK table.
For other Intel cards, the VF in Hyper-V has different than VF in other systems.

> (2)    Do we have any way to turn of MDD on Windows host side, or any other walk-around solution?
> Many thanks and best regards,
> Liwu

      reply	other threads:[~2020-08-19 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 17:42 Liwu Liu
2020-08-19 18:11 ` Stephen Hemminger [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200819111135.2428eaaa@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=liwuliu@fortinet.com \
    --cc=users@dpdk.org \


* 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).