Skip to content

Commit

Permalink
INSTALL.DPDK: Notes on running ovs-vswitchd/dpdk inside a VM
Browse files Browse the repository at this point in the history
Additional configuration is required if you want to run ovs-vswitchd
with DPDK backend inside a QEMU virtual machine. This happens because,
by default, virtio NIC provided to the guest doesn't support multiple
TX queues which are required by ovs-vswitchd/dpdk. This commit updates
INSTALL.DPDK.md to provide guidelines on how to enable support for
multiple TX queues using QEMU command line and Libvirt config file.

Signed-off-by: Oleg Strikov <[email protected]>
Acked-by: Pravin B Shelar <[email protected]>
  • Loading branch information
strikov-canonical authored and Pravin B Shelar committed May 12, 2015
1 parent 95e9881 commit 9899125
Showing 1 changed file with 18 additions and 0 deletions.
18 changes: 18 additions & 0 deletions INSTALL.DPDK.md
Original file line number Diff line number Diff line change
Expand Up @@ -560,6 +560,24 @@ steps in the previous section before proceeding with the following steps:
5. Use virt-manager to launch the VM
Running ovs-vswitchd with DPDK backend inside a VM
--------------------------------------------------
Please note that additional configuration is required if you want to run
ovs-vswitchd with DPDK backend inside a QEMU virtual machine. Ovs-vswitchd
creates separate DPDK TX queues for each CPU core available. This operation
fails inside QEMU virtual machine because, by default, VirtIO NIC provided
to the guest is configured to support only single TX queue and single RX
queue. To change this behavior, you need to turn on 'mq' (multiqueue)
property of all virtio-net-pci devices emulated by QEMU and used by DPDK.
You may do it manually (by changing QEMU command line) or, if you use Libvirt,
by adding the following string:
`<driver name='vhost' queues='N'/>`
to <interface> sections of all network devices used by DPDK. Parameter 'N'
determines how many queues can be used by the guest.
Restrictions:
-------------
Expand Down

0 comments on commit 9899125

Please sign in to comment.