On Thu, Oct 08, 2026 at 11:15:16AM +0200, Peter Krempa via Users wrote:
On Thu, Oct 08, 2026 at 06:59:42 +0200, lejeczek via Users wrote:
Hi guys.
Under what circumstances libvrirt would start _dnsmasq_ on it's own?
Libvirt starts a dnsmasq instance when you have a libvirt-managed network which is configured to provide addresses via DHCP or DNS forwarding.
I certainly did not plan for libvirt to manage dhcp but sometimes I find:
-> $ netstat -utapn | grep \:67 udp 0 0 0.0.0.0:67 0.0.0.0:* 19678/dnsmasq
-> $ ps -Fp 19678 UID PID PPID C SZ RSS PSR STIME TTY TIME CMD dnsmasq 19678 1 0 2258 1824 8 Oct07 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
which... does fcuk up my main (should be the only) DHCP server. Is it possible to tell libvirt not to do that no matter the circumstances? (or it's not libvirt?)
You need to disable 'DNS' and 'DHCP' addressing for all networks you have defined in libvirt or disable them (disable autostart).
Or configure your own dnsmasq to only operate on certain interfaces. Libvirt's dnsmasq are all configured to explicitly only touch the network interface (bridge) that libvirt created, so it can co-exist with other dnsmasqs that are servicing other interfaces https://wiki.libvirt.org/Libvirtd_and_dnsmasq.html 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 :|