Quoting Erno Kuusela (e...@iki.fi): > Public bug reported: > > The virbr0 interface with a rfc1918 address stays around after removing > libvirt-bin. I also tried reinstalling it and "stop libvirt-bin", that > didn't work either. Google found me some virsh incantations and "virsh > net-destroy default" finally did the trick.
Thanks for taking the time to submit this bug. Libvirt can be used to create and start virtual machines using external programs like kvm. You can shut down and even remove libvirt-bin while keeping those VMs running. Since those VMs might be using the virbr0 bridge, the bridge is kept up until the next reboot. Perhaps it would make sense to have libvirt shut down all its VMs when it is removed, however as this would be a change in behavior it should be discussed with the community. I've marked down a note to propose this as a UDS topic. ** Changed in: libvirt (Ubuntu) Importance: Undecided => Wishlist ** Changed in: libvirt (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/868379 Title: nat setup left around after removing/stopping libvirt-bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/868379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs