From: Santosh Shukla <sshukla@mvista.com>
To: "Mauricio Vásquez" <mauricio.vasquezbernal@studenti.polito.it>
Cc: dpdk <dev@dpdk.org>
Subject: Re: [dpdk-dev] virtio PMD is not working with master version
Date: Thu, 25 Feb 2016 18:38:48 +0530 [thread overview]
Message-ID: <CAAyOgsYfGzwuTr7YHnhDA7nG7_BM75_-9hv4jsgUmnudBk83WA@mail.gmail.com> (raw)
In-Reply-To: <CAPwdgqgVgZaRPUB+VrbExy9JTzjzKWjn2K2j=a3OS1YrkO1OvA@mail.gmail.com>
On Thu, Feb 25, 2016 at 5:00 PM, Mauricio Vásquez
<mauricio.vasquezbernal@studenti.polito.it> wrote:
> Hello,
>
> I am trying to connect two virtual machines through Open vSwitch using
> vhost-user ports, on the host side everything looks fine.
> When using the standard virtio drivers both virtual machines are able to
> exchange traffic, but when I load the virtio PMD and run a DPDK application
> it shows the following error message:
>
> ...
> EAL: PCI device 0000:00:04.0 on NUMA socket -1
> EAL: probe driver: 1af4:1000 rte_virtio_pmd
> EAL: PCI memory mapped at 0x7f892dc00000
> PMD: virtio_read_caps(): [40] skipping non VNDR cap id: 11
> PMD: virtio_read_caps(): no modern virtio pci device found.
> PMD: vtpci_init(): trying with legacy virtio pci.
> EAL: eal_parse_sysfs_value(): cannot open sysfs value
> /sys/bus/pci/devices/0000:00:04.0/uio/uio0/portio/port0/start
> EAL: pci_uio_ioport_map(): cannot parse portio start
> EAL: Error - exiting with code: 1
> Cause: Requested device 0000:00:04.0 cannot be used
> ...
>
hmmm, Resource error log has nothing to do with ovs, I tested
tip-of-tree for testpmd for ioport mode, no interface attached.
Couldn't see those error.
next prev parent reply other threads:[~2016-02-25 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 11:30 Mauricio Vásquez
2016-02-25 13:08 ` Santosh Shukla [this message]
2016-02-25 13:30 ` David Marchand
2016-02-26 2:23 ` Yuanhan Liu
2016-02-26 8:28 ` David Marchand
2016-02-26 8:44 ` Xie, Huawei
2016-02-26 9:04 ` Santosh Shukla
2016-03-16 20:27 ` Thomas Monjalon
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=CAAyOgsYfGzwuTr7YHnhDA7nG7_BM75_-9hv4jsgUmnudBk83WA@mail.gmail.com \
--to=sshukla@mvista.com \
--cc=dev@dpdk.org \
--cc=mauricio.vasquezbernal@studenti.polito.it \
/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).