I was able to reproduce the bug on Focal, and since we seem to carry the same version on Jammy/Mantic (and likely Noble), it's probable that the bug also happens in those releases.
For future reference:
# apt install -y libvirt-daemon-system bind9 dnsmasq
Reboot, and try bringing up the "default" network on libvirt:
# virsh net-start default error: Failed to start network default error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2: dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use
I was able to reproduce the bug on Focal, and since we seem to carry the same version on Jammy/Mantic (and likely Noble), it's probable that the bug also happens in those releases.
For future reference:
# apt install -y libvirt- daemon- system bind9 dnsmasq
Reboot, and try bringing up the "default" network on libvirt:
# virsh net-start default NAME=virbr0 /usr/sbin/dnsmasq --conf- file=/var/ lib/libvirt/ dnsmasq/ default. conf --leasefile-ro --dhcp- script= /usr/lib/ libvirt/ libvirt_ leaseshelper) unexpected exit status 2:
error: Failed to start network default
error: internal error: Child process (VIR_BRIDGE_
dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use