@paelzer, glad to see you reproduce the problem successfully, and simulate by creating nested KVM is better the my test, thanks
here I would like to add more history for this bug report, * it is running under KVM with multiple instance * it is ungracefully shut-down (could be simulated by virsh if test under nested KVM, or kill) * disk for physical host is running under RAID-1 * disk for physical host is formatted with 2-partition, / and /boot * one of the KVM instance running with 2 vHDD, partition: / and /data * * the /data is mounted as data volume for DB (yeah, it is reading/writing all the time) as for the patch in the PPA above, let's focus on libvirt-related section only, I would prefer to keep sleep interval short (1s), see discussion #14 ~ #16 above, consider the following scenario, if under a slow environment, waiting for socket ready required 65s, but due to the loop with incremental condition, it will required 91s, there's 26s wasted (1s + 2s + 4s + 8s + 16s + 30s + 30s = 91s) and the worst case, it will lead to 29s wasted. it is slowing down boot up speed, I think it's not a good user experience, although it is no harm for system. BTW, I saw you marked Xenial/Zesty/Artful as Fixed Released in #26, #27 does it mean test#35 all passed for Xenial/Zesty/Artful? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571209 Title: Sockfile check retries too short for a busy system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1571209/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
