DPDK usage discussions
 help / color / mirror / Atom feed
From: Liwu Liu <liwuliu@fortinet.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] TX fails for Intel 550 and 710 PMD on Hyper-V guests
Date: Wed, 19 Aug 2020 17:42:46 +0000	[thread overview]
Message-ID: <e362fcf68c294f4097d26d2ff6253419@fortinet.com> (raw)

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?

(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,

***  Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. ***

             reply	other threads:[~2020-08-19 17:42 UTC|newest]

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

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=e362fcf68c294f4097d26d2ff6253419@fortinet.com \
    --to=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).