[Bug 495394] Re: autostart almost always fails on boot time host

[Mika Båtsman]

Part of this problem is that there are 2 competing mechanisms for
bringing the bridges up:

1) bridge-network-interface.conf from bridge-utils
2) network-interface.conf from ifupdown

These two seem to be racing which one gets to handle the interface. It
seems that most of the time network-interface.conf is faster and emits
net-device-up. bridged-network.conf (from the patch) relies on net-
device-up events. Because of the bridge-network-interface.conf the
bridged-network.conf didn't seem to get all the net-device-up events
which caused occasional failures. At least for me that happened very
seldom and that made the problem more difficult to solve.

I've disabled bridged-network-interface.conf and haven't had any
problems with networking and libvirt for a few months now.

The attachment has my current solution for 10.04. I haven't tested it
with 10.10 or 11.04. It now checks status for status network-interface
instead of bridge-network-interface so it's a bit more generic and could
help with wider range of network configurations, not just with bridges.
I have also rename bridged-network.conf to network-up.conf. If you have
tested the previous patch and are going to test this one make sure you
don't have both bridged-network.conf and network-up.conf.

I don't have any setups using alias interfaces so I don't know if this
helps with with those but at least it's not that bridge specific any
more.

** Patch added: "Patch V3"
   https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/495394/+attachment/2125882/+files/network-up.conf.patch

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/495394

Title:
  autostart almost always fails on boot time host