On Jul 2, 2011, at 2:24 PM, Piotr Kandziora wrote: > This situation happens usually after I restart my testing server. What is > reason of this? How can I fix it? Maybe this is connected to brcompatd mode. > If it were possible to use OVS with LibVirt (maybe am I wrong here that this > is not possible?) I would not use this mode.
My guess is that when you reboot, a new interface record is getting created but nothing is cleaning up the old records. I doubt the old record is being referenced, which is why nothing complained about the duplicate name and ovs-vswitchd did not fille the record with useful information (e.g., ofport, statistics, and status). This isn't really a problem other than filling your database with discarded records. We generally recommend people avoid brcompatd whenever possible. Others on this list can answer better than I (please jump in!), but I believe you can configure libvirt to use an Ethernet device model. You then write ifup/ifdown scripts that make the appropriate ovs-vsctl calls. --Justin _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
