Your reply solves all my problems, thanks very much Brad! I didn't know I need to add ifup into a startup script and openvswitch-switch.README.Debian does not mention it. After I added ifup, then /etc/network/interfaces seemed ready for ovs. And then I configured br0 and virbr0 (in my case).
-- Best regards, Can Zhang On 2012年11月28日Wednesday at 上午7:51, Brad Hedlund wrote: > Greetings, > The long start-up delay is not related to DHCP -- according to my testing. > I believe it has something to do with openvswitch not normally loading until > after the /etc/network/interfaces file has been processed. > As a result the system hangs waiting for br0 to be available -- at least > thats my best guess. > I came to the conclusion because after adding this configuration to the top > of the /etc/network/interfaces file the boot up time is normal again: > > auto lo > iface lo inet loopback > up service openvswitch-switch start > > This seems to load the openvswitch earlier and in a timley enough manner to > quickly process the configuration of the interfaces file you have. > > I also tried the methods described in openvswitch-switch.README.Debian. That > worked for me too. > > Make sure you're not forgetting the ifup --allow=ovs br0 command. > You'll need to manually type that in at the console or put it in a startup > script -- as it appears the supplied openvswitch scripts do not start that > automatically on boot up. I put that command in the > /etc/network/if-up.d/upstart script and that seems to work. > > Cheers, > Brad > > > On Thu, Nov 22, 2012 at 10:41 PM, can. <[email protected] (mailto:[email protected])> > wrote: > > Hello, > > > > Yesterday I encountered "bridge module is loaded, not loading brcompat" > > error (http://openvswitch.org/pipermail/discuss/2012-November/008446.html), > > and I solved it by not setting a "bridge_port eth0" in > > /etc/network/interfaces. Here's the file now: > > > > ---- > > auto eth0 > > iface eth0 inet static > > address 0.0.0.0 > > > > > > auto br0 > > iface br0 inet dhcp > > > > > > ## bridge_port eth0 ## removed this > > > > > > > > auto virbr0 > > iface virbr0 inet dhcp > > > > > > ---- > > > > and this is `ovs-vsctl show`: > > ---- > > Bridge "virbr0" > > Port "virbr0" > > Interface "virbr0" > > type: internal > > Port vethfFrrKy > > Interface vethfFrrKy > > > > > > > > > > Bridge "br0" > > Port "eth0" > > Interface "eth0" > > Port "br0" > > Interface "br0" > > type: internal > > ovs_version: "1.7.1" > > > > > > ---- > > It seems working well, only that the "network device configuration" time at > > startup is very long. I guess this is related to virbr0, the default > > libvirt virtual bridge, which doesn't get the configuration. > > > > > > > > Also you might notice that eth0 is connected to br0, and these two > > configurations as shown are not conform.(So first question, is there a > > cleaner way to configure ovs? I tried the instructions in > > openvswitch-switch.README.Debian, but didn't work. btw I'm using ubuntu > > 12.04) > > > > And since virbr0 doesn't get enough configuration, it's isolated from the > > Internet. So how to make both br0 and virbr0 connect to the Internet? I > > think I can connect virbr0 to br0 but don't know how. And to be more > > generally, can I create arbitrary topologies inside ubuntu using ovs? > > > > -- > > Best regards, > > Can Zhang > > > > > > > > > > _______________________________________________ > > discuss mailing list > > [email protected] (mailto:[email protected]) > > http://openvswitch.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
