On 25 April 2018 at 22:00, Ben Pfaff <[email protected]> wrote: > On Fri, Apr 20, 2018 at 04:35:27PM +0200, Riccardo Ravaioli wrote: > > [...] > > ovs-vsctl: Error detected while setting up 'eth9': could not add network > > device eth9 to ofproto (File exists). See ovs-vswitchd log for details. > > [...] > > The interface is up and bound to the correct driver: > > # ip a show dev eth9 > > 206: eth9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master > > ovs-system state UP group default qlen 1000 > > link/ether 00:90:0b:54:88:58 brd ff:ff:ff:ff:ff:ff > > "master ovs-system" means that the interface is already part of a Open > vSwitch bridge. Probably you added it to an Open vSwitch bridge some > funny way? What does "ovs-dpctl show" print? How about "brctl show"? >
Yes, I was testing configurations with the same interface bound to DPDK, then in PCI-pt to a VM, and then added normally to a switch (as above). I'm not sure which exact sequence of configuration changes caused this, though. I'll try to repeat some tests and run the commands you suggested. Thanks! Riccardo
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
