Re: [dpdk-dev] [dpdk-users] SR-IOV problem with dpdk drivers

Re: [dpdk-dev] [dpdk-users] SR-IOV problem with dpdk drivers

[SAKTHIVEL ANAND S]

+dev-dpdk can help here..

I have removed SR-IOV and made those interfaces as PIC-passthrough and that
is working without any issues.
So, Yes! this could be problem with virtual function driver(i40evf).

Thanks


On Thu, Jul 27, 2017 at 8:30 AM, Raju-dev grishma <rajugrishma@gmail.com>
wrote:

> Linux driver works, DPDK older version works but not dpdk 17.05.
> Then it seems the dpdk driver of 17.05 has some issues to work with vmware
> hypervisors.
>
>
>
> On Wed, Jul 26, 2017 at 6:38 PM, SAKTHIVEL ANAND S <anand.sa88@gmail.com>
> wrote:
>
>> Thanks Raju..
>>
>> These SR-IOV interfaces are reachable with linux drivers and also i have
>> verified with dpdk 2.2.0, which is running without any issues.
>> But when i bring in dpdk17.05, it failed to come up with above mentioned
>> error messages.
>>
>> please help me if, is it known issue with new SR-IOV drivers? or did i
>> miss something?
>>
>> -Sakthivel S
>>
>> On Wed, Jul 26, 2017 at 6:02 PM, Raju-dev grishma <rajugrishma@gmail.com>
>> wrote:
>>
>>> hello Sakthivel,
>>> Can you try if on this VM, the kernel can see the interfaces and ping
>>> works with those interfaces?
>>> Secondly did you try with older version of DPDK ?
>>>
>>> Tx
>>>
>>>
>>> On Wed, Jul 26, 2017 at 5:05 PM, SAKTHIVEL ANAND S <anand.sa88@gmail.com
>>> > wrote:
>>>
>>>> i just upgraded the Intel NIC firmware and still there is no improvement
>>>> for this.. It is falling under same issue. Following are NIC firmware
>>>> details.
>>>>
>>>> ethtool -i vmnic4
>>>>
>>>> driver: i40e
>>>>
>>>> version: 1.3.45
>>>>
>>>> firmware-version: 5.60 0x80002dab 1.1618.0
>>>>
>>>> bus-info: 0000:05:00.0
>>>>
>>>> Can someone pls help me to fix this. is this known issue, or did i
>>>> missed
>>>> something?
>>>>
>>>> Thanks in Advance
>>>>
>>>> Sakthivel S OM
>>>>
>>>> On Thu, Jul 20, 2017 at 7:06 PM, Kyle Larose <klarose@sandvine.com>
>>>> wrote:
>>>>
>>>> > I’m not an expert, but my guess is that your PF is running a very
>>>> > different version of the i40e driver, and because of this the two
>>>> cannot
>>>> > communicate. I personally have never seen this before. Perhaps google
>>>> has?
>>>> >
>>>> >
>>>> >
>>>> > *From:* SAKTHIVEL ANAND S [mailto:anand.sa88@gmail.com]
>>>> > *Sent:* Thursday, July 20, 2017 6:57 PM
>>>> > *To:* Kyle Larose
>>>> > *Cc:* users@dpdk.org
>>>> > *Subject:* Re: [dpdk-users] SR-IOV problem with dpdk drivers
>>>> >
>>>> >
>>>> >
>>>> > Thanks Kyle , yes i loaded the .ko files and i am able to bind to DPDK
>>>> > driver now. But when i am running testpmd, it shows the below error
>>>> message.
>>>> >
>>>> > root@ubuntu:~/dpdk-stable-17.05.1/bin# ./testpmd -c7 -n1 -- -i
>>>> > --nb-cores=2 --nb-ports=2 --total-num-mbufs=1024
>>>> > EAL: Detected 8 lcore(s)
>>>> > EAL: No free hugepages reported in hugepages-1048576kB
>>>> > EAL: Probing VFIO support...
>>>> >
>>>> >
>>>> >
>>>> > *EAL: PCI device 0000:03:00.0 on NUMA socket -1 EAL:   probe driver:
>>>> > 8086:154c net_i40e_vf i40evf_init_vf(): init_adminq failed
>>>> > i40evf_dev_init(): Init vf failed*
>>>> > EAL: Requested device 0000:03:00.0 cannot be used
>>>> > EAL: PCI device 0000:04:00.0 on NUMA socket -1
>>>> > EAL:   probe driver: 15ad:7b0 net_vmxnet3
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > *EAL: PCI device 0000:0b:00.0 on NUMA socket -1 EAL:   probe driver:
>>>> > 8086:154c net_i40e_vf i40evf_check_api_version(): PF/VF API version
>>>> > mismatch:(0.0)-(1.1) i40evf_init_vf(): check_api version failed
>>>> > i40evf_dev_init(): Init vf failed*
>>>>
>>>> > EAL: Requested device 0000:0b:00.0 cannot be used
>>>> > EAL: PCI device 0000:13:00.0 on NUMA socket -1
>>>> > EAL:   probe driver: 15ad:7b0 net_vmxnet3
>>>> > EAL: PCI device 0000:1b:00.0 on NUMA socket -1
>>>> > EAL:   probe driver: 15ad:7b0 net_vmxnet3
>>>> > EAL: No probed ethernet devices
>>>> > Interactive-mode selected
>>>> > EAL: Error - exiting with code: 1
>>>> >   Cause: Invalid port 2
>>>> >
>>>> > pls help me ti resolve this.
>>>> >
>>>> > Thanks
>>>> >
>>>> > Sakthivel S OM
>>>> >
>>>> >
>>>> >
>>>> > On Thu, Jul 20, 2017 at 4:01 PM, Kyle Larose <klarose@sandvine.com>
>>>> wrote:
>>>> >
>>>> > Hi
>>>> >
>>>> > > -----Original Message-----
>>>> > > From: users [mailto:users-bounces@dpdk.org] On Behalf Of SAKTHIVEL
>>>> > > ANAND S
>>>> > > Sent: Thursday, July 20, 2017 3:05 PM
>>>> > > To: users@dpdk.org
>>>> > > Subject: [dpdk-users] SR-IOV problem with dpdk drivers
>>>> > >
>>>> > > Hi
>>>> > >
>>>> > > I am facing problem when i tried to bring up my SR-IOV interfaces
>>>> in to
>>>> > dpdk
>>>> > > compatible driver..
>>>> > > could someone pls help where i have missed?
>>>> > >
>>>> > > ERROR:
>>>> > >
>>>> > > root@ubuntu:~# ./dpdk-devbind.py -b igb_uio 0b:00.0
>>>> > > Error: bind failed for 0000:0b:00.0 - Cannot open
>>>> > > /sys/bus/pci/drivers/igb_uio/bind
>>>> > >
>>>> >
>>>> >
>>>> > Is the igb_uio kernel module loaded? lsmod should say. If not, run
>>>> > 'modprobe igb_uio', then try again.
>>>> >
>>>> >
>>>> > > DPDK: 17.05.1
>>>> > > ubuntu:16.04.2
>>>> > > Nic: Intel XL710/X710
>>>> > > --
>>>> > > Thanks
>>>> > > Sakthivel S OM
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> > Thanks
>>>> > Sakthivel S OM
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Thanks
>>>> Sakthivel S OM
>>>>
>>>
>>>
>>
>>
>> --
>> Thanks
>> Sakthivel S OM
>>
>>
>


-- 
Thanks
Sakthivel S OM