15

Whenever I start my laptop(HP) , 'Network Connections' shows it being connected (though it is actually not) . When I go to 'edit connections' option , it shows virbr0 . I have to delete it every time . How to get rid of this ? Is it a hardware problem ?

Rangerix
  • 471
  • 2
  • 6
  • 11

2 Answers2

15

On my machine virbr0 interface was created after installation of libvirt-bin package which is dependency of virt-manager.

Solution 1 (straight-forward):

It seems you can remove it from startup by removing corresponding file with

sudo rm /etc/libvirt/qemu/networks/autostart/default.xml

You can bring it back with

sudo ln -s /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/autostart/default.xml

Solution 2 (with virsh)

  • disable: sudo virsh net-autostart --disable default
  • enable: sudo virsh net-autostart default

But this has side-effect. If you want to use bridged network in virt-manager you should start bridge before launching VM with sudo virsh net-start default.

Solution 3 (set virbr0 unmanaged in NetworkManager)

The following lines should be added to the end of /etc/NetworkManager/NetworkManager.conf:

[keyfile]
unmanaged-devices=interface-name:virbr0

The result: NetworkManager "does not know" about virbr0, but VMs can access bridged networking.

d a i s y
  • 5,561
N0rbert
  • 103,523
  • I added the same lines as the third solution to /etc/NetworkManager/NetworkManager.conf but it's still there. Will that take effect after restarting the system? – aderchox Aug 30 '20 at 15:29
2

Give this a try this is mostly for Centos

sudo su -
virsh net-destroy default
virsh net-undefine default
systemctl stop libvirtd.service
systemctl disable libvirtd.service
apt remove qemu-kvm qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils
Pablo Bianchi
  • 17,552
IT repo
  • 21
  • 1