From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015
Date: Fri, 24 Oct 2014 12:10:20 +0200 [thread overview]
Message-ID: <2237912.y2DQ3nfIDF@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C42AEE@IRSMSX102.ger.corp.intel.com>
2014-10-24 08:10, O'driscoll, Tim:
> > From: Matthew Hall [mailto:mhall@mhcomputing.net]
> > Specifically, in the virtio-net case above, I have discovered, and Sergio at Intel
> > just reproduced today, that neither virtio PMD works at all inside of
> > VirtualBox. One can't init, and the other gets into an infinite loop. But yet it's
> > claiming support for VBox on the DPDK Supported NICs page though it
> > doesn't seem it ever could have worked.
>
> At the moment, within Intel we test with KVM, Xen and ESXi. We've never
> tested with VirtualBox. So, maybe this is an error on the Supported NICs
> page, or maybe somebody else is testing that configuration.
I'm the author of this page. I think I've written VirtualBox to show where
virtio is implemented. You interpreted this as "supported environment", so
I'm removing it.
Thanks for testing and reporting.
--
Thomas
next prev parent reply other threads:[~2014-10-24 10:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:48 O'driscoll, Tim
2014-10-22 14:20 ` [dpdk-dev] " Thomas Monjalon
2014-10-22 14:44 ` Zhou, Danny
2014-10-22 15:05 ` Liang, Cunming
2014-10-22 16:10 ` [dpdk-dev] [dpdk-announce] " Luke Gorrie
2014-10-23 12:29 ` O'driscoll, Tim
2014-10-22 19:22 ` Matthew Hall
2014-10-24 8:10 ` O'driscoll, Tim
2014-10-24 10:10 ` Thomas Monjalon [this message]
2014-10-24 19:02 ` Matthew Hall
2014-10-24 19:01 ` Matthew Hall
2014-10-23 3:06 ` Tetsuya Mukawa
2014-10-23 10:04 ` O'driscoll, Tim
2014-10-23 3:17 ` Tetsuya Mukawa
2014-10-23 11:27 ` O'driscoll, Tim
2014-10-31 22:05 ` Xie, Huawei
2014-11-02 12:50 ` Tetsuya Mukawa
2014-10-23 14:18 ` [dpdk-dev] Fwd: " Jay Rolette
2014-10-23 14:52 ` Alex Markuze
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=2237912.y2DQ3nfIDF@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).