** Description changed: - This bug has already been reported in http://bugs.debian.org/cgi- - bin/bugreport.cgi?bug=663931 but Libvirt 0.9.8 in Ubuntu Precise suffers - from the same problem. + ===================================== + SRU Justification: + 1. Impact: starting libvirtd takes 2 minutes + 2. Development fix: in debian and quantal, this is fixed by explicitly + giving a shorter timeout when calling udevadm settle. + 3. Stable fix: same as development fix + 4. Test case: define an lvm based storage pool, then stop and start libvirt. + 5. Regression potential: we're lowering a timeout, so in theory the timing + of some races could be changed. + ===================================== + This bug has already been reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663931 but Libvirt 0.9.8 in Ubuntu Precise suffers from the same problem. When an LVM-based storage pool is present libvirtd takes around three minutes to start up because a timeout occurs when libvirtd calls "udevadm settle". In the Debian bug report this has been identified as a problem in Libvirt, additional info is found here: http://article.gmane.org/gmane.linux.hotplug.devel/17421 - A local workaround is to issue "service udev restart" before starting + A local workaround is to issue "service udev restart" before starting libvirtd. The bug has been worked around in Debian's Libvirt 0.9.12 by reducing the "udev settle" timeout to ten seconds. Can we expect this workaround to somehow make it into Libvirt 0.9.8 and Ubuntu Precise?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027987 Title: Starting libvirtd takes too long because of "udevadm settle" timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1027987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
