DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sambath Kumar Balasubramanian <sambath.balasubramanian@gmail.com>
To: Selvaganapathy Chidambaram <selvaganapathyc@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Issue in virtio pmd available in dpdk 1.5 - virtqueue does not exist
Date: Fri, 17 Jan 2014 22:49:24 -0800	[thread overview]
Message-ID: <CAPrcauMF6uMbDVuOd7fPY65pXHnPojM1SdqBxMHnSfSRuFO5gw@mail.gmail.com> (raw)
In-Reply-To: <CAB3M1-F6wpP2FNnfpaKvTpSbKh_Z2xocvxOgDw3zAbjF_mGW-w@mail.gmail.com>

Hi All,

  I have the same issue. Is there a known solution for this?

Regards,
Sambath


On Fri, Jan 10, 2014 at 3:47 PM, Selvaganapathy Chidambaram <
selvaganapathyc@gmail.com> wrote:

> Hi,
>
> I am using dpdk 1.5 where virtio pmd is available
> in dpdk-1.5.1r2/lib/librte_pmd_virtio/.
>
> When I run l2fwd reference application, I am getting the following error:
>
> EAL: PCI device 0000:00:08.0 on NUMA socket -1
> EAL:   probe driver: 1af4:1000 rte_virtio_pmd
> EAL: PCI device 0000:00:09.0 on NUMA socket -1
> EAL:   probe driver: 1af4:1000 rte_virtio_pmd
> Lcore 0: RX port 0
> Lcore 1: RX port 1
> Initializing port 0...
> EAL: Error - exiting with code: 1
>   Cause: rte_eth_rx_queue_setup:err=-22, port=0
>
> On debugging further, I see that in function virtio_dev_queue_setup,
> vq_size
> is zero and hence returns error.
>
> I was able to run e1000 pmd and virtio pmd *extension* successfully. Please
> let me know if I need to set anything specifically to make virtio pmd to
> work.
>
> Thanks,
> Selvaganapathy.C.
>

      reply	other threads:[~2014-01-18  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 23:47 Selvaganapathy Chidambaram
2014-01-18  6:49 ` Sambath Kumar Balasubramanian [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=CAPrcauMF6uMbDVuOd7fPY65pXHnPojM1SdqBxMHnSfSRuFO5gw@mail.gmail.com \
    --to=sambath.balasubramanian@gmail.com \
    --cc=dev@dpdk.org \
    --cc=selvaganapathyc@gmail.com \
    /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).