The workaround you found essentially means it is not libvirt, because
that is just stopping and starting a new process to handle those. I'm
happy you found this workaround for you and for others finding this -
but obviously we'd prefer that to just not happen :-/
And indeed that might suffer by suspend/resume and might be related to
the bug you found or any other. At an abstract level this is very much
server-host software that was likely never expecting to be in a
suspend/resume scenario :-/ This means nothing except that many will be
hesitant to go all too deep in it.
As a minimum let me re-map this to dnsmasq, but the problem now becomes
could we somehow reproduce this with libvirt out of the mix (helps
debugging and fixing this eventually anyway).
To get from the transient created
/usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
--leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
To something that can be modified and instructed to take logs and be debugged.
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111765
Title:
DHCP doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2111765/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
