Segmentation Fault when DPDK enabled with OVS

Bug #1682085 reported by Arslan Qadeer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DPDK
New
Undecided
Unassigned

Bug Description

2017-04-12T09:12:23.501Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovs-vswitchd.log
2017-04-12T09:12:23.503Z|00002|ovs_numa|INFO|Discovered 8 CPU cores on NUMA node 0
2017-04-12T09:12:23.503Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 8 CPU cores
2017-04-12T09:12:23.503Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2017-04-12T09:12:23.503Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
2017-04-12T09:12:23.504Z|00006|dpdk|INFO|DPDK Enabled, initializing
2017-04-12T09:12:23.504Z|00007|dpdk|INFO|No vhost-sock-dir provided - defaulting to /var/run/openvswitch
2017-04-12T09:12:23.504Z|00008|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem 1024,0 -c 0x00000001
2017-04-12T09:12:23.567Z|00002|daemon_unix|ERR|fork child died before signaling startup (killed (Aborted), core dumped)
2017-04-12T09:12:23.567Z|00003|daemon_unix|EMER|could not detach from foreground session

Steps to reproduce:

Install Following Packages on CentOS 7 Physical Machine:
1) http://cbs.centos.org/kojifiles/packages/dpdk/16.11/5.el7/x86_64/dpdk-16.11-5.el7.x86_64.rpm
2)http://cbs.centos.org/kojifiles/packages/openvswitch/2.6.1/4.1.git20161206.el7.1/x86_64/openvswitch-2.6.1-4.1.git20161206.el7.1.x86_64.rpm

Without DPDK openvswitch starts perfect but when we enable DPDK as follows:

ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true

openvswitch service fails to start and above error shown in "ovs-vswitchd.log"

Is there anything that i am missing or this is a bug?

Revision history for this message
Adolfo Duarte (adolfo-duarte) wrote :

I know this is old, but just in case someone comes looking for an answer.
I ran into this problem because my hugepages were setup wrong:
if you follow this instructions you can get more info.
in my case my pages were setup wrong because the page setup talks bout bytes. i.e. 2048=2M and the pages are expresed in M, once I made those two match i.e. 2pages = 2048*2 Bytes or 2MB then it worked.
hope it helps someone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.