[Bug 852000] [NEW] libvirt no longer needs to start on stopped networking

[Serge Hallyn]

Public bug reported:

Recently the 'static-device-up' event was introduced, which fires when
all auto interfaces are up.  /etc/init/rc-sysinit.conf now waits on that
new event.  libvirt starts on runlevel [2345], so it won't start until
all auto interfaces are up.  Looking through upstart --verbose info
confirms this.

So we should be able to have libvirt-bin.conf just be 'start on runlevel
[2345]' again.

** Affects: libvirt (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  libvirt no longer needs to start on stopped networking

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