HI Michal

Thank you for explaining. I have this situation in a number of production servers where we would always use static IPs for the host and VMs. In such case we have no requirement for NATed network in the future. And we we ever do, we can rely on a DHCP server within the LAN to provide IPs to the VMs.

I'll look to remove both libivirt-daemon-driver-network, libvirt-daemon-driver-network and dnsmasq.

Any further thought from your side?

On 24 April 2015 at 13:12, Michal Privoznik <mprivozn@redhat.com> wrote:

On 24.04.2015 12:45, mimicafe@gmail.com wrote:
> I am running KVM virtualization with libvirtd (libvirt) 0.10.2 in bridged
> network mode, however I still have the default virtual network
> bridge/interfaces and dnsmasq on the host. What I am trying to understand
> is whether or not dnsmasq and the virtual network (*virbr0, Vnet0 and Vnet1*)
> still play any role. If not, can I remove them?

Yes, you can safely remove libvirt-daemon-config-network package. It
should disable the default network. However, dropping dnsmasq is a bit
harder, since libivirt-daemon-driver-network depends on it. We can't
know whether you will not someday like a NATed network with a DHCP
server, even though now you don't. However,
libvirt-daemon-driver-network takes care about all the network types
known to libvirt, so you can't really drop it (unless forcibly removing
the package and let the libvirt just deal with it, which I'd discourage
you from doing anyway).

Michal