I did a clean install of Fedora 23 on my new ‘built from recycled components‘ crash-and-burn test system recently, and all went reasonably well – apart from – apparently – having to re-partition an already-partitioned drive (!)…
After booting for the first time, I found that a ‘bridged’ network link – virtbr0 – was active.. As I did not want/need this, I tried deactivating/deleting it, using the usual network commands (ifdown, ifconfig…down…) only to have it reactivated each time..
After a bit of research, this is one way to get rid of it..
Check to see if it is running:
systemctl status libvirtd.service ● libvirtd.service - Virtualization daemon ................etc....
Kill it (as root):
systemctl disable libvirt-guests.service systemctl disable libvirtd.service systemctl stop libvirtd.service
Get rid of all the libvirt stuff:
# rpm -qa |grep libvirt libvirt-daemon-driver-qemu-22.214.171.124-2.fc23.x86_64 libvirt-client-126.96.36.199-2.fc23.x86_64 libvirt-gobject-0.2.2-1.fc23.x86_64 libvirt-daemon-driver-nodedev-188.8.131.52-2.fc23.x86_64 libvirt-daemon-driver-storage-184.108.40.206-2.fc23.x86_64 libvirt-daemon-kvm-220.127.116.11-2.fc23.x86_64 libvirt-glib-0.2.2-1.fc23.x86_64 libvirt-daemon-18.104.22.168-2.fc23.x86_64 libvirt-gconfig-0.2.2-1.fc23.x86_64 libvirt-daemon-driver-nwfilter-22.214.171.124-2.fc23.x86_64 libvirt-daemon-driver-interface-126.96.36.199-2.fc23.x86_64 libvirt-daemon-driver-secret-188.8.131.52-2.fc23.x86_64 libvirt-daemon-config-network-184.108.40.206-2.fc23.x86_64 libvirt-daemon-driver-network-220.127.116.11-2.fc23.x86_64
But – be careful.. I tried this by just using # dnf erase libvirt* but found that this would have also de-installed other software – including parts of qemu and xen – as well.. This was unwarranted, as I confirmed by using rpm to de-install all of libvirt, and this command completed successfully, without needing to use the –nodeps parameter.. The rpm command I used to do this was # rpm -e $(rpm -qa |grep libvirt) gnome-boxes $(rpm -qa |grep virt-)…to get rid of associated utilities as well…
Then just re-start the network..
systemctl restart network.service
Robert Gadsdon. January 28, 2016.
(rpm command example updated – Jan 30)