Hi Ben, I reproduce this crash, there is not gdb backtrace.
After i create bridge like this: [root@juno ~]# ovs-vsctl show ffe31aed-853b-4a88-8036-bbda08d5303a Bridge br-int fail_mode: secure Port br-int Interface br-int type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Bridge br-tun fail_mode: secure Port "vxlan-0a3557f2" Interface "vxlan-0a3557f2" type: vxlan options: {df_default="true", in_key=flow, local_ip="10.53.87.254", out_key=flow, remote_ip="10.53.87.242"} Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port br-tun Interface br-tun type: internal [root@juno ~]# I want to check the ovs route, so i issue command "ovs-appctl ovs/route/show", the ovs-vswitchd stop running. The log is: [root@juno ~]# ovs-appctl ovs/route/show 2015-09-19T14:00:27Z|00001|jsonrpc|WARN|unix:/root/ovs-build/var/run/openvswitch/ovs-vswitchd.15668.ctl: receive error: Connection reset by peer 2015-09-19T14:00:27Z|00002|unixctl|WARN|error communicating with unix:/root/ovs-build/var/run/openvswitch/ovs-vswitchd.15668.ctl: Connection reset by peer ovs-appctl: ovs-vswitchd: transaction error (Connection reset by peer) 2015-09-14 22:49 GMT+08:00 Ben Pfaff <b...@nicira.com>: > On Mon, Sep 14, 2015 at 09:30:08PM +0800, Na Zhu wrote: > > Openstack neutron ovs agent calls ovs-vsctl to create bridge and ports, > > after i upgrade to ovs 2.4 with dpdk, some ovs-vsctl commands can not > run. > > > > For example: > > neutron ovs agent uses the command "ovs-vsctl --timeout=10 --oneline > > --format=json -- --may-exist add-br br-int" to create bridge br-int. > > I want to create a bridge in ovs dpdk, so i use this command "ovs-vsctl > > --timeout=10 --oneline --format=json -- --may-exist add-br br-int -- set > > bridge br-int datapath_type=netdev", the ovs-vswitchd crash. > > Obviously, it's a bug. Can you pass along a backtrace from GDB? > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev