Starting libvirtd takes too long because of "udevadm settle" timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Unassigned | ||
Quantal |
Fix Released
|
Medium
|
Unassigned |
Bug Description
=======
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://
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://
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?
description: | updated |
Thanks for reporting this bug. Marking it confirmed based on separate debian reports.
I see no commits in the libvirt git tree addressing this. Do you know whether it has been discussed on irc (or libvirt mailing list)?