Whenever I restart dnsmasq (including a system restart), I have to start
with a new (empty) DHCP leases file. Your DHCP leases file is specified
in your dnsmasq configuration file (*.conf).
Your config file appears to be /var/lib/libvirt/dnsmasq/default.conf
Your DHCP leases file appears to be /usr/lib/libvirt/libvirt_leaseshelper
Hope that helps,
Ken
On 1/14/25 2:00 PM, Charles Curley wrote:
I have a virtual network controlled with Virtual Machine Manager. I
just gracefully rebooted the host machine. Bringing up the virtual
network produces the following:
Error starting network 'default': 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
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57,
in newfn
ret = fn(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/virt-manager/virtManager/object/network.py", line 69, in
start
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 3547, in create
raise libvirtError('virNetworkCreate() failed')
libvirt.libvirtError: 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
Near as I can tell, that address is not already in use. The host is on
192.168.100.0/24.
root@hawk:~# ifconfig -a
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.6 netmask 255.255.255.0 broadcast 192.168.100.255
ether 30:5a:3a:81:83:79 txqueuelen 1000 (Ethernet)
RX packets 2027 bytes 661510 (646.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2016 bytes 669884 (654.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 1525 bytes 1023413 (999.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1525 bytes 1023413 (999.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@hawk:~#
dnsmasq is not running now.
Might this be related to the upgrade of dnsmasq-base on January 12
(2.89-1, 2.90-4~deb12u1)?
