{"id":1651,"date":"2016-01-28T22:38:26","date_gmt":"2016-01-28T22:38:26","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=1651"},"modified":"2016-01-31T08:23:19","modified_gmt":"2016-01-31T08:23:19","slug":"fedora-getting-rid-of-unwanted-virtbr0","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=1651","title":{"rendered":"Fedora – Getting Rid of Unwanted ‘virtbr0’"},"content":{"rendered":"

I did a clean install of Fedora 23<\/strong> on my new ‘built from recycled components<\/em>‘ crash-and-burn test system recently, and all went reasonably well – apart from – apparently – having to re-partition an already-partitioned drive (!)…<\/p>\n

After booting for the first time, I found that a ‘bridged’ network link – virtbr0<\/strong> – was active..\u00a0\u00a0\u00a0 As I did not want\/need this, I tried deactivating\/deleting it, using the usual network commands (ifdown<\/strong>, ifconfig…down<\/strong><\/span>…) only to have it reactivated each time..<\/p>\n

After a bit of research, this is one way to get rid of it..<\/p>\n

Check to see if it is running:<\/p>\n

systemctl status libvirtd.service<\/span><\/strong>\r\n\u25cf libvirtd.service - Virtualization daemon\r\n................etc....<\/span><\/strong><\/pre>\n
Kill it (as root):<\/p>\n
systemctl disable libvirt-guests.service<\/span><\/strong>\r\nsystemctl disable libvirtd.service<\/span><\/strong>\r\nsystemctl stop libvirtd.service<\/span><\/strong><\/pre>\n
Get rid of all the libvirt stuff:<\/p>\n
# rpm -qa |grep libvirt<\/span><\/strong>\r\nlibvirt-daemon-driver-qemu-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-client-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-gobject-0.2.2-1.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-driver-nodedev-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-driver-storage-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-kvm-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-glib-0.2.2-1.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-gconfig-0.2.2-1.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-driver-nwfilter-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-driver-interface-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-driver-secret-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-config-network-1.2.18.2-2.fc23.x86_64<\/span><\/strong>\r\nlibvirt-daemon-driver-network-1.2.18.2-2.fc23.x86_64<\/span><\/strong><\/pre>\n
But – be careful<\/span>..\u00a0\u00a0 I tried this by just using # dnf erase libvirt*<\/span><\/strong> but found that this would have also de-installed other software – including parts of qemu<\/strong> and xen<\/strong> – as well..\u00a0\u00a0 This was unwarranted, as I confirmed by using rpm<\/strong> to de-install all of libvirt, and this command completed successfully, without needing to use the –nodeps<\/span><\/strong> parameter..\u00a0\u00a0\u00a0 The rpm command I used to do this was #\u00a0rpm -e $(rpm -qa |grep libvirt) gnome-boxes $(rpm -qa |grep virt-)<\/span><\/strong>…to get rid of associated utilities as well…<\/p>\n
Then just re-start the network..<\/p>\n
systemctl restart network.service<\/span><\/strong><\/pre>\n
Robert Gadsdon.\u00a0\u00a0 January 28, 2016.
\n(rpm command example updated – Jan 30)<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
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..\u00a0\u00a0\u00a0 As I …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[6,10,1238,11,15,19,20],"tags":[1216,1265,242,1267,1175,1268,1266],"class_list":["post-1651","post","type-post","status-publish","format-standard","hentry","category-crash-and-burn","category-fedora","category-fix","category-hacks","category-linux-2","category-opinion","category-performance-2","tag-fedora-23","tag-libvirt","tag-linux","tag-removal","tag-success","tag-use-rpm","tag-virtbr0"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1651","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1651"}],"version-history":[{"count":3,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1651\/revisions"}],"predecessor-version":[{"id":1655,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1651\/revisions\/1655"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1651"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1651"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1651"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}