Hi Andrei,
thanks for your report!
I can confirm the issue, and it doesn't seem to matter which out of
$ virsh nwfilter-list
you pick.
Your log shows 2 ~5 second timeouts which explains the ~10 seconds we see.
But we likely need to find what the issue is in the background (on the daemon).
Fortunately I was able to further confirm that not all releases are affected:
- Xenial: affected
- Yakkety: affected
- Zesty: affected
- Artful: no affected
So the fix seems to exist in later versions, although it could be something
outside of libvirt/qemu but in those releases.
Anyway as easiest next step I'll have to check if I can create a setup to
bisect this down to a fix, then we can evaluate the backportability.
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727366
Title:
virsh start/destroy is too slow after adding firewall rule
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1727366/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
