Bug#663931: libvirt-bin: libvirtd make "udevadm settle" respond too slow

[Ernesto Domato]

On Wed, Mar 14, 2012 at 19:19, Marco d'Itri <md at linux.it> wrote:
> reassign 663931 lvm2
> thanks
>
> On Mar 14, Ernesto Domato <edomat at gmail.com> wrote:
>
>> (about 3 minutes). Then I found running libvirtd on debug mode that it calls
>> "udevadm settle" on startup. This command also takes about 3 minutes to respond.
> Why does libvirtd run "udevadm settle", for a start?
>

I don't know about this one but maybe Guido could give some words about this.

>> Not using LVM doesn't generates this problem.
>>
>> So, it seems that when libvirtd is started and there's a pool that use LVM it
>> mess with udev somehow that produce this behavior.
> So this looks like a LVM issue.
> It is not a udev bug unless you can show that it is.
>
> --
> ciao,
> Marco

I'm inclined to believe that maybe is more a race condition between
libvirtd and udev (the libvirt-bin package that contains libvirtd
depends on udev) that involves LVM provoked by libvirtd. This
assumption comes from the fact that udev with LVM works without
problem when libvirtd doesn't get involved.

Let me know what can I do to help debug this issue to find a solution
rather than restart udev :-)

Thanks.
Ernesto