From: Stephen Hemminger <stephen@networkplumber.org>
To: Nick Allen <nick@nickallen.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Unable to Bind Device in VirtualBox VM
Date: Wed, 10 Feb 2016 09:17:43 -0800 [thread overview]
Message-ID: <CAOaVG15fAErUzW9=syVGgkw3aKQV8oEoo2QV3n0BrbKRAJOrqA@mail.gmail.com> (raw)
In-Reply-To: <CAHSJ8NwiLrg3ZW=R=xhu6CWfgSYHjM4J7xVa+R5EqDM+OaFM+Q@mail.gmail.com>
KVM/QEMU
On Wed, Feb 10, 2016 at 9:15 AM, Nick Allen <nick@nickallen.org> wrote:
> What is typically used instead of VirtualBox? I'd be happy to try an
> alternative. Ideally, it would be something that could run across
> different host operating systems; including OS X and Linux.
>
> Thanks for your thoughts.
>
> On Wed, Feb 10, 2016 at 12:12 PM, Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> > On Wed, 10 Feb 2016 08:45:20 -0500
> > Nick Allen <nick@nickallen.org> wrote:
> >
> >> Problem: I am unable to bind a virtual NIC using DPDK 2.2.0 that I
> >> created inside of a Ubuntu 14.04 guest running in VirtualBox 5.0.14 on
> >> OS X 10.11.3 on a 2015 Macbook Pro. Here is the error that I am
> >> seeing.
> >>
> >
> > Do you mean the virtio NIC?
> > VirtualBox has a non-standard implementation of virtio and I suspect
> > the feature negotiation isn't working. Could be a virtualbox bug.
> >
> > Since virtualbox is not open source, I don't use or test it.
>
>
>
> --
> Nick Allen <nick@nickallen.org>
>
prev parent reply other threads:[~2016-02-10 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 13:45 Nick Allen
2016-02-10 17:12 ` Stephen Hemminger
2016-02-10 17:15 ` Nick Allen
2016-02-10 17:17 ` Stephen Hemminger [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='CAOaVG15fAErUzW9=syVGgkw3aKQV8oEoo2QV3n0BrbKRAJOrqA@mail.gmail.com' \
--to=stephen@networkplumber.org \
--cc=nick@nickallen.org \
--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).