[dpdk-dev] Could virtio-net-pmd co-exist with virtio-net.ko?

GongJinrong jinronggong at hotmail.com
Thu Nov 6 10:58:21 CET 2014

Hi, Matthew, Thanks a lot, I will try it.

-----Original Message-----
From: Matthew Hall [mailto:mhall at mhcomputing.net] 
Sent: Thursday, November 06, 2014 4:21 PM
To: GongJinrong
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] Could virtio-net-pmd co-exist with virtio-net.ko?

On Thu, Nov 06, 2014 at 10:24:11AM +0800, GongJinrong wrote:
> Hi, Guys
>      When I run virtio-net-pmd in VM, I got "virtio-net device is 
> already used by another driver" error message, after I removed the 
> virtio-net.ko, it worked, but now I cannot use the virio-net driver 
> for another virtual NIC, this cost that normal network 
> performance(non-DPDK application) drops a lot, could the virtio-net-pmd
co-exist with standard virio-net driver?
> BR
> John Gong

I have no proof it will work perfectly, as I never got to use the virtio
PMDs because neither works in VirtualBox (developer-friendly / desktop

But there is a script included in DPDK, dpdk_nic_bind.py, which should let
you configure this more intelligently on a per-VNIC basis. You could try
something similar to this:

export RTE_SDK="${build_directory}/external/dpdk"
export RTE_TOOLS="${RTE_SDK}/tools"
export RTE_NIC_BIND="${RTE_TOOLS}/dpdk_nic_bind.py"

"${RTE_NIC_BIND}" --status | fgrep "${PCI_ID}"
"${RTE_NIC_BIND}" -b none          "${PCI_ID}"
"${RTE_NIC_BIND}" -b igb_uio       "${PCI_ID}"
"${RTE_NIC_BIND}" --status | fgrep "${PCI_ID}"

Good Luck!

More information about the dev mailing list