OpenvSwitch with DPDK isn't working with VirIO (Proposed Repo enabled)
christian.ehrhardt at canonical.com
Sat Apr 30 21:17:34 UTC 2016
Writing on the cellphone at the airport so I hope autocorrect doesn't kill
Fine that you got it working, but for whoever else that might find the
thread. It was a bug that you could use virtue devices without unassigning
them from the kernel first.
The new conffiles talk about it, also the changelog as well as the updated
server-side - the last one takes a few more days to update externally.
The behaviour in that part now matches DPDK 16.04 which had the fix.
Am 29.04.2016 20:37 schrieb "Martinx - ジェームズ" <thiagocmartinsc at gmail.com>:
> Never mind, it is working now... Doing more tests... Have a nice weekend!
> On 29 April 2016 at 21:40, Martinx - ジェームズ <thiagocmartinsc at gmail.com>
>> Guys, Christian,
>> After upgrading DPDK to "2.2.0-0ubuntu8", OpenvSwitch with DPDK is not
>> starting up anymore within a KVM Guest.
>> Here is what I have in my Xenial KVM Guest:
>> root at template-1:~# dpdk_nic_bind --status
>> Network devices using DPDK-compatible driver
>> 0000:00:05.0 'Virtio network device' drv=uio_pci_generic unused=
>> 0000:00:06.0 'Virtio network device' drv=uio_pci_generic unused=
>> Network devices using kernel driver
>> 0000:00:03.0 'Virtio network device' if= drv=virtio-pci
>> 0000:00:04.0 'Virtio network device' if= drv=virtio-pci
>> apt install openvswitch-switch-dpdk
>> update-alternatives --set ovs-vswitchd
>> file "/etc/default/openvswitch-switch" contains:
>> DPDK_OPTS='--dpdk -c 0x1 -n 4 -m 1024'
>> However, after running:
>> service openvswitch-switch restart
>> There is no "ovs-vswit... --dpdk -c 0x1 -n 4 -m 1024" process!
>> It was behaving differently before... I'll try rebuild it, or try to use
>> l2fwd DPDK App to test this VM...
>> Any clue?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ubuntu-server