After quite some analysis and debugging I could identify an issue regarding
double configuring the device.
Daniele replied to the mailing list request I had and suggested backporting an
virtio fix that came after 2.2.
That worked well, with backporting these I can get it to work now.
Thanks
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openvswitch-dpdk (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
Info on progress.
No feedback from communities so far.
After various other DPDK fixes took 3/4 of my day I set up a more thorough
debugging environment derived from my testing env, but the real debugging
itself has to start tomorrow morning.
--
You received this bug notification because you
** Also affects: openvswitch-dpdk (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1559912
Title:
Openvswitch 2.5 + dpdk 2.2 totally
systemd[1]: Starting Open vSwitch Internal Unit...
ovs-ctl[13868]: * Starting ovsdb-server
ovs-vsctl[13893]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait --
init -- set Open_vSwitch . db-version=7.12.1
ovs-vsctl[13898]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait set
Open_vSwitch .
It was also reported in 1559408 that this also affects BNX2X_PMD
** Description changed:
*as a start same text as my reach for the involved project mailing
lists*
I was trying to replicate a setup that I have working on physical devices
(ixgbe) under kvm since there is a virtio pmd
