On Tue, Apr 19, 2016 at 7:31 PM, James Hogarth <james.hogarth(a)gmail.com> wrote:
On 19 Apr 2016 18:25, "Patrick O'Callaghan"
> 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.
You can set up a bridge with libvirt rather than with ifcfg-* or NM
but still use a bridged network for the VMs. It has the merit of
keeping the VM networking within libvirt's realm, just like for natted
or routed networks.