From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com [209.85.216.179]) by dpdk.org (Postfix) with ESMTP id 418AD7D63; Thu, 27 Jul 2017 12:12:11 +0200 (CEST) Received: by mail-qt0-f179.google.com with SMTP id v29so39731218qtv.3; Thu, 27 Jul 2017 03:12:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NWNSvIS3H/eAUwh0pT//CwlDJX46KK9cn7Hhz+Q1P3Y=; b=QHlHrwlS3ilOj/JYI/ovDzrHz9nofC7ykEfn85F1ch9Q/ovzp1/MsQbg2Ew5xiSYqj qbfJY7qCt9m670vOmFW0G6dRFc0ycT0bZNy8XQ3hjDzCRb3kPazidQHhTHDfWkghPH+3 m1ZwGnaAMHYXOe6W0uqMniGYS6G7Cz7QVRGmkzfm1cr7aMR5ST00VUwqJjKEuZaMnR1+ v0ru725Tl69P8RfDutx8hdMki7803/5sBEkkeXvoxHutwj44OyRptnfwLO5MyESAMZge /lRGjziBF/X37IjZLk5U0iA14/gRCvI7Bn6eSSbXH5oJAAampf/54I8702yVaHPJJwlF Mlng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NWNSvIS3H/eAUwh0pT//CwlDJX46KK9cn7Hhz+Q1P3Y=; b=DIMZ5lPQgSb7uXnxNo1nC1tn+pk9lGzl2PPnZiWS33piZjTfId9Mn6OIijy0qqovSE daHYM7FdGVqXo1/ZzmPSocBMP5/A8EkO9h0aOVXrBhoR+kuQxA22Qh0nU5wAnEx1jI6U vWPhjjVZ7mVVo1+1FM1g9tmE7dsnzXPwebIr5lrrpBmqvGU91TULDMdbZd0LHjeJUPUl 6xCKbp4V9QmNa0Dej4njadP/v6lXhhKwkLShfXJ05kaEih+7unR5ZVDocVTpJI8H/ciT EZVlj30U52xUFm3u6213x5zQf4dH5Uv+4WFxJJTryheCQWj87T5upgeBgtGZQNe9UwgX Hczg== X-Gm-Message-State: AIVw111uJTVB3/d6kJTnqNdknmpDGZNwIpjMhJmidz+LkcwsyCQCi1kL Hmh0n1Z0XjFZYRNFiKIgH1WTvbNsPA== X-Received: by 10.200.55.53 with SMTP id o50mr5232195qtb.211.1501150330234; Thu, 27 Jul 2017 03:12:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.3.129 with HTTP; Thu, 27 Jul 2017 03:12:09 -0700 (PDT) In-Reply-To: References: From: SAKTHIVEL ANAND S Date: Thu, 27 Jul 2017 15:42:09 +0530 Message-ID: To: Raju-dev grishma , dev@dpdk.org Cc: Kyle Larose , "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] SR-IOV problem with dpdk drivers X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2017 10:12:11 -0000 +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 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 vmwar= e > hypervisors. > > > > On Wed, Jul 26, 2017 at 6:38 PM, SAKTHIVEL ANAND S > 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 >> 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 >> > wrote: >>> >>>> i just upgraded the Intel NIC firmware and still there is no improveme= nt >>>> 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 >>>> wrote: >>>> >>>> > I=E2=80=99m 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 googl= e >>>> 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 DP= DK >>>> > 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=3D2 --nb-ports=3D2 --total-num-mbufs=3D1024 >>>> > 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 >>>> 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 >> >> > --=20 Thanks Sakthivel S OM