> -----Original Message----- > From: Joe Stringer [mailto:j...@ovn.org] > Sent: Friday, April 28, 2017 12:35 AM > To: fukaige > Cc: ovs-discuss@openvswitch.org > Subject: Re: [ovs-discuss] Create ovs br0 failed using command "ovs-vsctl > add-br br0" > > On 26 April 2017 at 23:51, fukaige <fuka...@huawei.com> wrote: > > Hi all, > > > > I use command "ovs-vsctl add-br br0" to create a bridge, but got below log: > > > > ovs-vsctl: Error detected while setting up 'br0'. See ovs-vswitchd log for > details. > > > > Then, I check the ovs-vswitched log for details: > > > > 2017-03-30T01:23:49.324Z|00056|ofproto_dpif|INFO|system@ovs-system: > > Datapath supports recirculation > > 2017-03-30T01:23:49.324Z|00057|ofproto_dpif|INFO|system@ovs-system: > > MPLS label stack length probed as 1 > > 2017-03-30T01:23:49.324Z|00058|ofproto_dpif|INFO|system@ovs-system: > > Datapath supports unique flow ids > > 2017-03-30T01:23:49.324Z|00059|ofproto_dpif|INFO|system@ovs-system: > > Datapath supports ct_state > > 2017-03-30T01:23:49.324Z|00060|ofproto_dpif|INFO|system@ovs-system: > > Datapath supports ct_zone > > 2017-03-30T01:23:49.325Z|00061|ofproto_dpif|INFO|system@ovs-system: > > Datapath supports ct_mark > > 2017-03-30T01:23:49.325Z|00062|ofproto_dpif|INFO|system@ovs-system: > > Datapath supports ct_label > > 2017-03-30T01:23:49.400Z|00001|ofproto_dpif_upcall(handler386)|INFO|re > > ceived packet on unassociated datapath port 0 > > 2017-03-30T01:23:49.404Z|00063|netdev_linux|WARN|ethtool command > > ETHTOOL_GFLAGS on network device br0 failed: No such device > > 2017-03-30T01:23:49.404Z|00064|dpif|WARN|system@ovs-system: failed > to > > add br0 as port: No such device > > 2017-03-30T01:23:49.404Z|00065|bridge|INFO|bridge br0: using datapath > > ID 000036dab10ee643 > > 2017-03-30T01:23:49.404Z|00066|connmgr|INFO|br0: added service > controller "punix:/var/run/openvswitch/br0.mgmt" > > > > I delete the br0, then try to add it. But, got same error as above. > > > > Finally, I restart the thread ovs-vswitchd and ovsdb-server. Then, the error > disappear and ovs-vsctl add-br br0 work well. > > > > My question: > > 1. Is any one meet with the same error? > > 2. Is any one can offer some suggestions to reproduce the error? > > Are you able to reliably reproduce this with upstream OVS? Can you provide a > list of commands that always hits this?
I am trying to reproduce it with ovs-2.5.1 & kernel 4.1 on ARM64. Any suggestions? _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
