From: Bruce Richardson <bruce.richardson@intel.com>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Bug 644] [dpdk-19.11.7]usertools/dpdk-devbind.py: bind NIC port to DPDK failed in vm.
Date: Mon, 1 Mar 2021 10:08:16 +0000 [thread overview]
Message-ID: <20210301100816.GB1251@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <bug-644-3@http.bugs.dpdk.org/>
On Mon, Mar 01, 2021 at 01:48:49AM +0000, bugzilla@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=644
>
> Bug ID: 644
> Summary: [dpdk-19.11.7]usertools/dpdk-devbind.py: bind NIC port
> to DPDK failed in vm.
> Product: DPDK
> Version: 19.11
> Hardware: All
> OS: All
> Status: UNCONFIRMED
> Severity: normal
> Priority: Normal
> Component: other
> Assignee: dev@dpdk.org
> Reporter: weix.ling@intel.com
> Target Milestone: ---
>
> DPDK version:
> 19.11.7-rc1(cbcd84e3304f43623efe34236f548a1bdae68ca4)
> Other software versions: qemu-4.2.1
> OS: Ubuntu 20.04.1 LTS/5.10.0-051000-generic
> Compiler: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
> Hardware platform: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
> NIC hardware: fortville_spirit
> NIC firmware: 5.10.0-051000-generic/8.00 0x80008b8a 1.2766.0
> Test Setup
> Steps to reproduce
> List the steps to reproduce the issue.
>
> #1.Bind nic port to vfio-pci on host
>
> usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:af:00.0 0000:af:00.1
>
Unrelated to this bug, don't use "--force" flag with dpdk-devbind unless
the script won't let you unbind a port from the kernel and you are
absolutely sure it is safe to do so. It should never be routinely used.
/Bruce
prev parent reply other threads:[~2021-03-01 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 1:48 bugzilla
2021-03-01 10:08 ` Bruce Richardson [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=20210301100816.GB1251@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=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).