On Thu, Oct 08, 2026 at 03:12:44PM +0200, lejeczek via Users wrote:
I've completely forgotten about 'default' network which I've never used.
But what is pretty confusing to me are the circumstances under which "it" happens, namely... There are no guests using 'default' network - there is DHCP server on "physical" network (same host as libvirt)
If its config is installed, the default network is set to autostart when virtnetworkd or libvirtd is started. Ideally modern deployments use modular daemons instead of libvirtd, such that virnetworkd is only launched when a guest actually wants to use a virtual network.
I can confirm dnsmasq is not started, is not running, not on boot nor later, then... "main" DHCP server goes down for whatever reason and... this happens, libvirt/dnsmasq slaps itself onto main/all network & actual DHCP is unable to come back - for obvious reason - when it does.
Libvirt does not do that. Any dnsmasq libvirt launches is configured to *only* operate on the specific bridge device libvirt creates. It leaves all other NICs alone for the user to configure their own DHCP/DNS service against. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|