From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.iitb.ac.in (smtp1.iitb.ac.in [103.21.127.13]) by dpdk.org (Postfix) with ESMTP id 82AFB5588 for ; Thu, 12 Jan 2017 13:39:30 +0100 (CET) Received: from ldns2.iitb.ac.in (ldns2.iitb.ac.in [10.200.12.2]) by smtp1.iitb.ac.in (Postfix) with SMTP id CA83DC5 for ; Thu, 12 Jan 2017 18:09:29 +0530 (IST) Received: (qmail 6391 invoked by uid 510); 12 Jan 2017 18:09:29 +0530 X-Qmail-Scanner-Diagnostics: from 10.200.1.25 by ldns2 (envelope-from , uid 501) with qmail-scanner-2.11 spamassassin: 3.4.1. mhr: 1.0. {clamdscan: 0.99.2/22878} Clear:RC:1(10.200.1.25):SA:0(0.0/5.6):. Processed in 2.781757 secs; 12 Jan 2017 18:09:29 +0530 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ldns2.iitb.ac.in X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.6 tests=IITB_ORIG,PROPER_IITB_MSGID autolearn=disabled version=3.4.1 X-Spam-Pyzor: Reported 0 times. X-Envelope-From: ppnaik@cse.iitb.ac.in X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received: from unknown (HELO ldns2.iitb.ac.in) (10.200.1.25) by ldns2.iitb.ac.in with SMTP; 12 Jan 2017 18:09:26 +0530 Received: from jeeves.cse.iitb.ac.in (miller.cse.iitb.ac.in [10.129.3.1]) by ldns2.iitb.ac.in (Postfix) with ESMTP id B66D334195F for ; Thu, 12 Jan 2017 18:09:26 +0530 (IST) Received: by jeeves.cse.iitb.ac.in (Postfix, from userid 51934) id A7EE98C2342; Thu, 12 Jan 2017 18:09:26 +0530 (IST) Received: from [10.129.41.21] (unknown [10.129.41.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by jeeves.cse.iitb.ac.in (Postfix) with ESMTPSA id 175A48C2325; Thu, 12 Jan 2017 18:09:26 +0530 (IST) Message-ID: <587778FE.8020302@cse.iitb.ac.in> Date: Thu, 12 Jan 2017 18:09:26 +0530 From: Priyanka User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Ferruh Yigit , "users@dpdk.org" CC: mitaliyada@cse.iitb.ac.in References: <584C3183.9020706@cse.iitb.ac.in> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] [dpdk-dev] DPDK NIC is unreachable 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, 12 Jan 2017 12:39:30 -0000 Hi Ferruh, Thanks for the reply. We could resolve this issue. The problem was that the kni command we were using was incorrect. Thanks, Priyanka On Thursday 12 January 2017 05:39 PM, Ferruh Yigit wrote: > Hi Priyanka, > > On 12/10/2016 4:46 PM, Priyanka wrote: >> Hi, >> >> We have a SRIOV+ DPDK 16.04 setup for a VM using KVM-qemu hypervisor. We >> are unable to ping the VM. We are assigning the VM to a SRIOV vf and for >> the DPDK enabled NIC on the VM to detect this VF, we are using KNI. >> >> We used the KNI app available in the examples folder. Although the non >> DPDK NIC is reachable in the VM but once we assign an IP using KNI to >> the DPDK NIC of the VM, it is unreachable. > Removing dev mail list. > > Can you please give some information related setup, is following correct: > > Host: Interface controlled by Linux (H1) > VM: There are two VF's, one controlled by DPDK (G1), other by Linux (G2) > NIC: ? > > KNI sample application ruun on VM. > > You can ping from H1 to G2, but not H1 to G1? > >> Please help us solve this issue. >> >> Thanks, >> >> Priyanka >> >>