Very interesting, thanks for the report - continuing on the bug with the discussion ...
Note: I'll be very busy this week. It woudl be great if you could you share your crash with the DPDK and OVS-Dev lists (and keep me on CC) to see if this is a known issue? Happened quite a few times in the past when I hunted down bugs and it would help me to help faster once I get to it. Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd On Sun, May 1, 2016 at 6:42 AM, Martinx - ジェームズ <[email protected]> wrote: > Cool! Thank you for taking time to reply for me during your flight... =) > > One more bug report for you! > > https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1577088 > > I am crashing the OVS+DPDK running at the host, from inside of a KVM Guest > running another OVS+DPDK! > > Cheers! > Thiago > > On 30 April 2016 at 18:17, Christian Ehrhardt < > [email protected]> wrote: > >> Hi Thiago, >> Writing on the cellphone at the airport so I hope autocorrect doesn't >> kill me ;-) >> >> 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 - ジェームズ" <[email protected] >> >: >> >>> Never mind, it is working now... Doing more tests... Have a nice weekend! >>> >>> On 29 April 2016 at 21:40, Martinx - ジェームズ <[email protected]> >>> wrote: >>> >>>> 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@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 >>>> unused=uio_pci_generic >>>> 0000:00:04.0 'Virtio network device' if= drv=virtio-pci >>>> unused=uio_pci_generic >>>> --- >>>> >>>> apt install openvswitch-switch-dpdk >>>> >>>> update-alternatives --set ovs-vswitchd >>>> /usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk >>>> >>>> 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? >>>> >>>> Cheers! >>>> Thiago >>>> >>> >>> >
-- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
