On Centos 6.5 both packages cannot be identified. any idea? sudo yum search libivirt-daemon-driver-network libvirt-daemon-config-network [sudo] password for bigfoot: Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: www.mirrorservice.org * extras: centos.openitc.uk * updates: mirror.mhd.uk.as44574.net Warning: No matches found for: libivirt-daemon-driver-network Warning: No matches found for: libvirt-daemon-config-network No Matches found [bigfoot@localhost ~]$ sudo yum whatprovide libivirt-daemon-driver-network libvirt-daemon-config-network Loaded plugins: fastestmirror, refresh-packagekit, security No such command: whatprovide. Please use /usr/bin/yum --help [bigfoot@localhost ~]$ sudo yum whatprovides libivirt-daemon-driver-network libvirt-daemon-config-network Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: www.mirrorservice.org * extras: centos.openitc.uk * updates: mirror.mhd.uk.as44574.net Warning: 3.0.x versions of yum would erroneously match against filenames. You can use "*/libivirt-daemon-driver-network" and/or "*bin/libivirt-daemon-driver-network" to get that behaviour Warning: 3.0.x versions of yum would erroneously match against filenames. You can use "*/libvirt-daemon-config-network" and/or "*bin/libvirt-daemon-config-network" to get that behaviour No Matches found [bigfoot@localhost ~]$ sudo rpm -qa | egrep -i 'libivirt-daemon-driver-network|libvirt-daemon-config-network' [bigfoot@localhost ~]$ [bigfoot@localhost ~]$ yum groupinfo "Virtualization Tools" "Virtualization Platform" Loaded plugins: fastestmirror, refresh-packagekit, security Setting up Group Process Loading mirror speeds from cached hostfile * base: mirror.sov.uk.goscomb.net * extras: centos.serverspace.co.uk * updates: centos.serverspace.co.uk Group: Virtualization Tools Description: Tools for offline virtual image management. Default Packages: libguestfs Optional Packages: libguestfs-bash-completion libguestfs-gfs2 libguestfs-java libguestfs-mount libguestfs-rescue libguestfs-rsync libguestfs-tools libguestfs-xfs virt-v2v Group: Virtualization Platform Description: Provides an interface for accessing and controlling virtualized guests and containers. Mandatory Packages: libvirt libvirt-client virt-who Optional Packages: fence-virtd-libvirt fence-virtd-multicast fence-virtd-serial libvirt-cim libvirt-java libvirt-qmf libvirt-snmp perl-Sys-Virt [bigfoot@localhost ~]$ sudo rpm -qa |grep libvirt* [sudo] password for bigfoot: Sorry, try again. [sudo] password for bigfoot: libvirt-java-javadoc-0.4.9-1.el6.noarch libvirt-lock-sanlock-0.10.2-46.el6_6.3.x86_64 libvirt-java-0.4.9-1.el6.noarch libvirt-snmp-0.0.2-4.el6.x86_64 libvirt-python-0.10.2-46.el6_6.3.x86_64 libvirt-java-devel-0.4.9-1.el6.noarch libvirt-0.10.2-46.el6_6.3.x86_64 libvirt-cim-0.6.1-12.el6.x86_64 libvirt-client-0.10.2-46.el6_6.3.x86_64 libvirt-devel-0.10.2-46.el6_6.3.x86_64 Mimi On 24 April 2015 at 16:08, mimicafe@gmail.com <mimicafe@gmail.com> wrote:
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