Comment 2 for bug 1722702
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: bind port regression | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hi,
I have seen this issue once but never found a root cause when trying to reproduce. I ended up with one system showing the behavior you mentioned and others not without seeing the difference why.
I thank you a lot to throw in the info that in your case it is the changing kernel version that breaks this - I didn't try to compare those when I looked at it.
In my cases I had the issue on multiple versions of libvirt, but it weould be really great if you would have a chance to test newer libvirt stacks e.g. from [1] - that way you can stick to your 16.04.3 set up and switching to your kernels as you had before but bump ther qemu/libvirt versions?
I want to avoid starting to work on it - to again end up unreproducible and this cross check would help a lot to start at the right setup.
Setting confirmed as I have seen it in the past hoping that this bug and the further tests will help to identify and eventually fix the issues root cause.
Since kernel version seems to matter adding a kernel task in case we end up with known issues or a fix there instead of in libvirt.
[1]: https:/