From: Lilijun <jerry.lilijun@huawei.com>
To: "Dong, Binghua" <binghua.dong@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver
Date: Thu, 23 Oct 2014 13:54:10 +0800 [thread overview]
Message-ID: <54489802.6030706@huawei.com> (raw)
In-Reply-To: <87AA51EDE124984B9C1CABE77679F9B2117CC675@SHSMSX103.ccr.corp.intel.com>
On 2014/10/23 13:37, Dong, Binghua wrote:
> Hi Lilijun,
>
> I think you need unbind the device 02:10.0 from driver ixgbevf first; In Host Linux, you also need ifconfig up the PF eth of this VF;
The script dpdk_nic_bind.py will unbind ixgbevf automatically when doing dpdk_nic_bind.py -b igb_uio 02:10.0.
As you said, the problem is fixed by executing ifconfig up my PF eth.
Thanks very much.
> Please ref my script to unbind a VF device and pass into VM, such as:
> PCI_eth="0000:02:10.0"
> ID_eth="ffff ffff"
> PCIX_eth=" -device pci-assign,host="${PCI_eth}
> echo $ID_eth > /sys/bus/pci/drivers/pci-stub/new_id
> echo ${PCI_eth} > /sys/bus/pci/devices/${PCI_eth}/driver/unbind
> echo ${PCI_eth} > /sys/bus/pci/drivers/pci-stub/bind
> CMD=${CMD}${PCIX_eth}
>
> ==============================================================================================
> #!/bin/bash
> ID="8086 0442"
> PCI="0000:83:01"
> IMG="/root/test_image/sles11sp2.img"
> HOST=" -vnc 172.16.200.166:1 "
> PCIX=" -device pci-assign,host="${PCI}
> CDROM=" -cdrom /root/QAT/driver.iso "
>
>
> CMD="qemu-system-x86_64 -m 2048 -smp 4 -hda "${IMG}${HOST}" -enable-kvm "
> #ADD CCK
> if [ 1 -eq 0 ];then
> echo $ID > /sys/bus/pci/drivers/pci-stub/new_id
> for i in 4 5 6 7
> do
> echo ${PCI}"."$i > /sys/bus/pci/devices/${PCI}"."$i/driver/unbind
> echo ${PCI}"."$i > /sys/bus/pci/drivers/pci-stub/bind
> CMD=${CMD}${PCIX}.$i
> done
> fi
>
> #ADD ETH
> if [ 1 -eq 0 ];then
> PCI_eth="0000:02:00.1"
> ID_eth="8086 1521"
> PCIX_eth=" -device pci-assign,host="${PCI_eth}
> echo $ID_eth > /sys/bus/pci/drivers/pci-stub/new_id
> echo ${PCI_eth} > /sys/bus/pci/devices/${PCI_eth}/driver/unbind
> echo ${PCI_eth} > /sys/bus/pci/drivers/pci-stub/bind
> CMD=${CMD}${PCIX_eth}
> fi
>
> #ADD CDROM
> #CMD=${CMD}${CDROM}
> echo $CMD
>
> #rmmod kvm_intel
> #rmmod kvm
> modprobe kvm
> modprobe kvm_intel
> $CMD
>
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lilijun
> Sent: Thursday, October 23, 2014 11:36 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver
>
> Hi all,
>
> I am testing the example l2fwd of dpdk-1.7.0 using intel 82599 VF NICs.
> But the VF can't be used when doing probe pmd driver with following error:
>
> EAL: PCI device 0000:02:10.0 on NUMA socket -1
> EAL: probe driver: 8086:10ed rte_ixgbevf_pmd
> EAL: PCI memory mapped at 0x7f78b181f000
> EAL: PCI memory mapped at 0x7f78b181b000
> EAL: Error - exiting with code: 1
> Cause: Requested device 0000:02:10.0 cannot be used
>
> Any suggestions?
>
> Thanks,
> Jerry
>
>
> .
>
next prev parent reply other threads:[~2014-10-23 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 3:36 Lilijun
2014-10-23 3:44 ` Zhang, Helin
2014-10-23 4:31 ` Lilijun
2014-10-23 4:56 ` Zhang, Helin
2014-10-23 5:51 ` Lilijun
2014-10-23 5:52 ` Dong, Binghua
2014-10-23 7:02 ` Lilijun
2014-10-23 5:37 ` Dong, Binghua
2014-10-23 5:54 ` Lilijun [this message]
2014-10-23 5:56 ` Zhang, Jerry
2014-10-23 7:03 ` Lilijun
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=54489802.6030706@huawei.com \
--to=jerry.lilijun@huawei.com \
--cc=binghua.dong@intel.com \
--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).