[Bug 850309] Re: libvirt fails to autostart VM attached to a bridged port

[Serge Hallyn]

For natty, the linked ifupdown tree (a compiled package of which is at
http://people.canonical.com/~serge/ifupdown_0.6.10ubuntu4.1_amd64.deb)
works for me.  Installing that, and then changing the 'start on' line in
/etc/init/libvirt-bin.conf to

start on (runlevel [2345] and static-network-up)

makes libvirt wait for all network devices to really be up and have ip
addresses.  As discussed on irc, if dhclient times out, then libvirt
will start anyway, but this is still a big improvement.

I'm assigning this to smoser for a quick sanity check.  smoser, if you
think it better than SpamapS take a look, please assign him, or assign
to me to bounce back to me.

** Changed in: ifupdown (Ubuntu Natty)
     Assignee: (unassigned) => Scott Moser (smoser)

** Changed in: ifupdown (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ifupdown (Ubuntu Natty)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Natty)
   Importance: Undecided => Medium

-- 
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/850309

Title:
  libvirt fails to autostart VM attached to a bridged port

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/850309/+subscriptions