DPDK usage discussions
 help / color / mirror / Atom feed
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:12:15 -0800	[thread overview]
Message-ID: <20160210091215.2f0e7081@xeon-e3> (raw)
In-Reply-To: <CAHSJ8Nysnza1h9cBp77C8v71TUJM_NSWYc3bFAnvFSMa8DtiWw@mail.gmail.com>

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.

  reply	other threads:[~2016-02-10 17:12 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 [this message]
2016-02-10 17:15   ` Nick Allen
2016-02-10 17:17     ` Stephen Hemminger

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=20160210091215.2f0e7081@xeon-e3 \
    --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).