From: Matthew Hall <mhall@mhcomputing.net>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] virtio UIO / PMD issues in default Ubuntu Cloud Images
Date: Wed, 22 Oct 2014 11:41:41 -0700 [thread overview]
Message-ID: <20141022184140.GA10424@mhcomputing.net> (raw)
In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B0C7FD90@IRSMSX108.ger.corp.intel.com>
On Wed, Oct 22, 2014 at 03:20:40PM +0000, Gonzalez Monroy, Sergio wrote:
> You are not forced to use shared libraries. This module loads successfully
> with an app (testpmd) built against static DPDK libs.
It sounds like it just requires additional options as mentioned later in your
mail. We should document the recommended set of link flags for static and
dynamic link w/ DPDK for apps, as it seems to cause issues for everybody
making non-example DPDK apps. I've seen several threads about it since joining
the mailing list a few months back. Maybe it is documented already but I
didn't see it. I'm willing to write it up but somebody will have to help
verify I got it right.
> I have reproduced this issue in VirtualBox:
>
> - For UIO Virtio PMD, there is an issue with igb_uio module and virtio vbox
> backend device, I fail to bind igb_uio driver to the virtio device.
>
> - For non-UIO Virtio PMD, the module fails to initialize properly as you
> have indicated in your previous post (stuck in a loop).
>
> I get this behavior with testpmd regardless of DPDK being built as static or
> shared.
THANK YOU!!! I am so glad to hear I'm not crazy and it really does not work.
So... back to the Supported NICs page. Right not it claims VirtualBox is
supported but 2 people have seen that it doesn't work at all with either
driver. Is it intended to be supported configuration or not?
If it is intended to be supported can we find someone who can help us fix the
bugs? It's not code I know much about. If it is not intended to work on VBox
can we delete it from the documentation so nobody besides me and you and the
other guy in 2013 waste more time trying to use it if it wasn't supposed to
work in the first place?
> Your undefined symbol error is most likely because the symbol is not in the
> dynamic symbol table of you app. You need to pass -rdynamic to GCC or
> -export-dynamic to LD when building your app.
Good advice. I'll try it and see. Of course it won't fix the infinite loop
though so the driver still won't help much even with the change present.
> Thanks,
> Sergio
Thanks to you for help verifying / reproducing / identifying the issues.
Matthew.
next prev parent reply other threads:[~2014-10-22 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 5:45 Matthew Hall
2014-10-14 6:03 ` Matthew Hall
2014-10-14 6:34 ` Matthew Hall
2014-10-14 8:22 ` Gonzalez Monroy, Sergio
2014-10-14 8:34 ` Matthew Hall
2014-10-14 12:16 ` Gonzalez Monroy, Sergio
2014-10-17 8:56 ` Matthew Hall
2014-10-21 13:22 ` Gonzalez Monroy, Sergio
2014-10-22 7:17 ` Matthew Hall
2014-10-22 15:20 ` Gonzalez Monroy, Sergio
2014-10-22 18:41 ` Matthew Hall [this message]
2014-10-23 16:15 ` Gonzalez Monroy, Sergio
2014-10-14 6:43 ` Matthew Hall
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=20141022184140.GA10424@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@intel.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).