In a similar case of (auto)start not being ready to run due to needing custom config being required I've seen discussions around "make libvirt depend on X" which often sounds intriguing until you realize it either makes it never start or start really late in the 99.9% of the cases that do not care.
The workaround I see often applied to represent this custom system config case in the general service handling was to add systemd drop in config to make it wait on some condition that matches the needs of your custom config. Applied to your case that would be something that represents your VFs to be really ready, and if libvirt would first time start only after that you should get a smooth startup experience including these networks autostart to work reloably. AFAIR we haven't yet found a case which ended up generally applciable to change the upstream service or the packaging to wait for it - so it stays custom-config for a small portion of sysadmins. Sadly I can't find a reference to that case :-/ But I hope this explanation for a config/workaround makes sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095127 Title: The file in /run/libvirt/network/autostarted isn't removed if autostart fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2095127/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
