On Thu, Oct 27, 2016 at 3:45 PM, Daniel P. Berrange <berra...@redhat.com> wrote:
> We can not do any sychronous wait against udev doing work - that will > add an unacceptable delay in the VM startup process - it is already > too long and we don't want to design a system that will make it even > slower. Note that if implemented it would be very targeted wait for one specific event. It *won't* be an equivalent of udevadm settle. In "uncontented" case udev's response should be very quick. Otherwise, something (e.g. lv resize) is still setting up a block device because change events are still being processed for it, and if that is the case, then just spawning qemu and hoping for the best doesn't seem right to me (disregarding SELinux and permission issues). Is libvirt really not waiting for udev at all? Michal -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
