[Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

Marking this bug as Fix Released - newer versions of OVS don't slurp all capable devices by default any longer. ** Changed in: openvswitch (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

Setting to Triaged but only low as it is documented, just not in that conf file. ** Changed in: openvswitch (Ubuntu) Status: New => Triaged ** Changed in: openvswitch (Ubuntu) Status: Triaged => Invalid ** Changed in: openvswitch (Ubuntu) Importance: Undecided => Low **

[Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

Hi Thiago, as James said this is a known dpdk behaviour - not special to OpenVswitch. Any other DPDK tool like l2fwd or such would have killed you just the same. We documented it in the serverguide. No release for 16.04 yet but you can take a look at

Re: [Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

Awesome! I'm gonna try it... Thanks James! :-D On 11 April 2016 at 04:34, James Page wrote: > Hi Thiago > > DPDK can use the virtio-pci devices directly without them being bound to > the userspace driver - as a result, the default configuration will try > to consume all

[Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

Hi Thiago DPDK can use the virtio-pci devices directly without them being bound to the userspace driver - as a result, the default configuration will try to consume all virtio-pci devices configured on the system; make sure the blacklist the primary network adapter so that DPDK does not try to

[Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

Hi Thiago DPDK can use the virtio-pci devices directly without them being bound to the userspace driver - as a result, the default configuration will try to consume all virtio-pci devices configured on the system; make sure the blacklist the primary network adapter so that DPDK does not try to

[Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

WAIT! I was too fast on reply about Trusty... On Trusty with Cloud Archive Liberty enabled, and even after this: update-alternatives --set ovs-vswitchd /usr/lib/openvswitch-switch-dpdk /ovs-vswitchd-dpdk And this: # grep DPDK_OPTS /etc/default/openvswitch-switch DPDK_OPTS='--dpdk -c 0x1 -n 4'

[Bug 1568627] Re: OpenvSwitch with DPDK brings all VirtIO NICs down, software reboot also doesn't work.

Guys, I can confirm that this problem does exists on top of Trusty KVM Guest with Linux 4.4 (same Xenial kernel), but with DPDK 2.0 and OpenvSwitch 2.4 from Liberty Cloud Archive, it works!! At least, the Trusty guest doesn't lose connectivity and soft reboot works too! Precisely where Xenial