Debian User Forums

I will try to get feedback from the maintainers.
Very good. Please post updates. It is only a work around and not solved. Let's hope the next update works.

I'll be paying attention, but as stated I don't expect to see the issue with my config.


Hi,

So I contacted the libvirt and dnsmasq-base developers and got useful answers from Sven Geuer (dnsmasq maintainer) and Lee Garrett (Debian developer).

First, the explanation:
The conflict between bind9 and dnsmasq-base for the use of the ...

@gooksin
I don't have any guess at the moment, but it does look like it is a generic network error underneath libvirt -which can be specific to method. I use all hardware networking so never have a ‘default’ network active, no bind9, no ‘br0’, etc.

You could look at the status with 'virsh net-list'.

As I remember, that should list states and modes of all libvirt managed networking, mine is empty since all is hardware managed. Maybe simplify, disassemble, reassemble, in order to find the ...

Hello,

Aki : Yes, bind9 is needed to serve local zones.

I can confirm now that rebooting has no effect.

Also, using these commands:


Hello there,

Searching around, in other forums, with those two commands below, i was able to start QEMU/KVM network:

sudo systemctl stop dnsmasq
sudo systemctl disable dnsmasq

[...]

Fontenele


doesn't work in my case. Indeed, the dnsmasq service is neither started (since there is a failure at boot) nor enabled:

(A)> sudo systemctl stop dnsmasq ...

Hi,
Same issue here after yesterday's upgrade.
This is the output from journalctl -b 0 -g 192.168 --no-pager :

de gen. 12 09:45:44 XXX systemd-networkd[512]: wlp3s0: DHCPv4 address 192.168.1.67/24, gateway 192.168.1.1 acquired from 192.168.1.1
de gen. 12 09:45:46 XXX named[1011]: listening on IPv4 interface wlp3s0, 192.168.1.67#53
de gen. 12 09:45:52 XXX named[1011]: listening on IPv4 interface virbr0, 192.168.122.1#53
de gen. 12 09:45:53 XXX dnsmasq[1243]: failed to create listening socket ...