Ubuntu
libvirt package

libvirt no longer needs to start on stopped networking

Bug #852000 reported by Serge Hallyn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

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.

Serge Hallyn (serge-hallyn)
Changed in libvirt (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
Serge Hallyn (serge-hallyn)
Changed in libvirt (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.