Description of problem:
I just got a libvirt update, and when I rebooted my system I found the
virbr0 interface had been created and dnsmasq running.
Long ago I removed the default network definition via:
virsh net-destroy default
virsh net-undefine default
Yet now, a libvirt update has apparently brought it back.
Seems like a bug to me that a sysadmin's libvirt configuration
would be changed by an update.
Version-Release number of selected component (if applicable):
libvirt-0.9.6-4.fc16.x86_64
How reproducible:
Just did the update, but I suspect it would happen again.
Steps to Reproduce:
1.see above
2.
3.
Actual results:
Default network has apparently returned.
Expected results:
Leave my configuration alone.
Additional info:
This question really needs to be discussed upstream, but I'm starting to think that Fedora should ship a libvirt-config RPM that contains things like the default network so people can avoid having the default network configured if they don't want it.
We ended up doing that in F17 at least. Maybe worth doing for F16.
Tom, you can actually make it stop by just doing
virsh net-destroy default
virsh net-autostart --disable default
Skipping the undefine step should prevent libvirt from enabling the network.