Hi,

I'm trying to add the dpdk ports to the ovs bridge, and while doing so, i
see the ovs daemon crashing with the 'operation not permitted' error,
here's my architecture, i am on a debian vm (pseudo host) that has virt-io
devices attached to it, i'm binding these virt-io's to the dpdk (igb_uio)
and trying to add it to the ovs bridge.
dpdk version: 17.11.2
ovs-version: 2.9.0
i did try looking for cores in /var/lib/systemd/coredump, but there are no
cores there, strange.
And i cannot look for cores in the current directory of that process
because it keeps getting killed (as the daemon tries to come up and crashes
and keeps at it forever)

2019-11-14T16:08:54.438Z|05381|bridge|INFO|bridge br0: added interface br0
on port 65534
2019-11-14T16:08:54.443Z|05382|dpif_netdev|INFO|PMD thread on numa_id: 0,
core id:  3 created.
2019-11-14T16:08:54.443Z|05383|dpif_netdev|INFO|There are 1 pmd threads on
numa node 0
2019-11-14T16:08:54.554Z|05384|netdev_dpdk|WARN|Rx checksum offload is not
supported on port 0
2019-11-14T16:08:54.554Z|05385|netdev_dpdk|ERR|Interface p1 MTU (1500)
setup error: Operation not supported
2019-11-14T16:08:54.554Z|05386|netdev_dpdk|ERR|Interface p1(rxq:1 txq:2)
configure error: Operation not supported
2019-11-14T16:08:54.554Z|05387|dpif_netdev|INFO|Core 3 on numa node 0
assigned port 'p1' rx queue 0 (measured processing cycles 0).
2019-11-14T16:08:54.562Z|05340|daemon_unix(monitor)|ERR|fork child died
before signaling startup (killed (Segmentation fault))
2019-11-14T16:08:54.562Z|05341|daemon_unix(monitor)|WARN|1781 crashes: pid
10551 died, killed (Segmentation fault), core dumped, waiting until 10
seconds since last restart


Should i be on the physical host (bare metal) instead a vm? and bind
physical devices to dpdk and then add it to the bridge?

I'm not sure where i'm going wrong.
Any advise is appreciated.
Thanks,
-Deepak Gowda
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to