DPDK usage discussions
 help / color / mirror / Atom feed
From: Priyanka <ppnaik@cse.iitb.ac.in>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "users@dpdk.org" <users@dpdk.org>
Cc: mitaliyada@cse.iitb.ac.in
Subject: Re: [dpdk-users] [dpdk-dev] DPDK NIC is unreachable
Date: Thu, 12 Jan 2017 18:09:26 +0530	[thread overview]
Message-ID: <587778FE.8020302@cse.iitb.ac.in> (raw)
In-Reply-To: <d440b8c4-341b-7b2a-44ed-939ed9b42f11@intel.com>

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
>>
>>

      reply	other threads:[~2017-01-12 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-10 16:46 [dpdk-users] " Priyanka
2017-01-12 12:09 ` [dpdk-users] [dpdk-dev] " Ferruh Yigit
2017-01-12 12:39   ` Priyanka [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=587778FE.8020302@cse.iitb.ac.in \
    --to=ppnaik@cse.iitb.ac.in \
    --cc=ferruh.yigit@intel.com \
    --cc=mitaliyada@cse.iitb.ac.in \
    --cc=users@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).