From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: [PATCH v2 00/24] Single virtio implementation Date: Tue, 27 Jan 2015 01:41:13 -0800 Message-ID: <20150127094113.GB19687@mhcomputing.net> References: <1421298930-15210-1-git-send-email-changchun.ouyang@intel.com> <1422326164-13697-1-git-send-email-changchun.ouyang@intel.com> <20150127030612.GA13138@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Wiles, Keith" Return-path: Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Tue, Jan 27, 2015 at 03:42:00AM +0000, Wiles, Keith wrote: > There is an app note on how to get DPDK working in VirtualBox, it is a bit > bumpy on getting it work. > Here is the link: > http://plvision.eu/blog/deploying-intel-dpdk-in-oracle-virtualbox/ > > I have not tried it, but it was suggested to me it should work. It will be > nice if the new driver works better :-) I already used a derivative of these directions... "cheated" and used the igb driver like they did. Unlike them I automated the entire process, including updating the base OS to latest kernel and recompiling against it, as well as auto-enabling the NICs, the SSE instruction sets, etc. etc. However their directions use an IGB NIC not a virtio-net NIC which would be much better for performance and resource consumption. So I really would be very very happy if we had a virtio-net which worked properly with both qemu and VirtualBox. Matthew.