On 19 Apr 2016 18:25, "Patrick O'Callaghan" <firstname.lastname@example.org> wrote:
> On Tue, 2016-04-19 at 17:50 +0200, Tom H wrote:
> > On Tue, Apr 19, 2016 at 5:09 PM, Patrick O'Callaghan
> > <email@example.com> wrote:
> > >
> > > On Tue, 2016-04-19 at 15:49 +0200, Tom H wrote:
> > > >
> > > >
> > > > This thread finally explains why you had a virbr0 a few months
> > > > ago
> > > > that wasn't created by libvirt but was messing up your dnsmasq
> > > > setup!
> > > You have a good memory :-)
> > Sometimes. I can't remember what the resolution was...
> > But I do remember that didn't really make sense and found it
> > frustrating.
> Apparently at the time I changed from NAT to Bridged networking, which
> fixed it (don't ask me why). However removing the redundant file seems
> to be the way to go. It's now back to NAT.
Ah when using bridges IIRC libvirt doesn't manage it as there's no dnsmasq for it to handle... So the expectation (and normal thing on hypervisor servers) is to create and manage the bridge with the NM/network service and then point the guest at that bridge in the configuration through libvirtd.