Description of problem: starting from fedora 24, I don't see virbr0 interface anymore. the standard behavior with the previous releases of fedora was to have virbr0 pre configred and ready to be used. Is this a new feature (ie: the way libvirt and kvm manage the network when using ///system has changed? Version-Release number of selected component (if applicable): 24 How reproducible: install f24 Steps to Reproduce: 1. just install it, it's the standard behavior now 2. 3. Actual results: no virbr0 interface is pre configured Expected results: a running virbr0 out of the box??? Additional info:
1) Please check that the package libvirt-daemon-config-network was installed - that is the package that adds the config for libvirt's default network (which is what's creating the bridge named virbr0) 2) If that package is installed, check the output of "sudo virsh net-list --all" to see if the default network has autostart enabled. If not, run "sudo virsh net-autostart default" 3) Try manually starting the default network with "virsh net-start default" and report any error that is generated. 4) if (3) successfully starts the network, reboot the host and see if it is successfully autostarted. If not, check the logs to see any errors generated by libvirtd, and report that here along with the output of "netstat -nr".
hello Laine, installing libvirt-daemon-config-network solved the issue. I was able to add the libvirt interface by myself but I wanted to notify what I thought was a bug. I have to add that I never had to install libvirt-daemon-config-network in the past, so I didn't know it existed. I feel that it should be installed as default, being gnome-boxes installed as default too. thanks
I think think whether or not Fedora installs libvirt-daemon-config-network depends on which type of install you're doing. And if you're doing the install from a live-image, then it's even more convoluted because of the potential for conflicts between the network address used by libvirt's default network and the network that is connected to the host's own ethernet - since an "installation" from a live image is done by simply copying the already-installed system over to the target disk (instead of installing the packages from rpm), there is no chance to execute libvirt code that attempts to avoid this conflict at install time. If this sounds confused, that's because it is :-) For the entire lurid history of that, see Bug 1146232. Can you explain how you installed your system, so that we can know what should have been installed and decide where to place this bug? (It either needs to be moved to a different component and/or be marked as a duplicate of some other Bug, but I don't keep close enough track to know which.
well, starting from fedora 22 I have been installing using the live iso (smaller and it is the default method now). If you install f23 (or f22) you will find a virbr0 interface after the setup, out of the box. The same does not apply to fedora 24. I was pointing this out because in the default installation you get the "ugly" gnome-boxes, which is a pita and runs a qemu:///session. As you know, the best option for this kind of setup network-wise is to have a network interface (virbr0). so it makes no sense to me that you install gnome boxes as default and not the virbr0 adapter.
Okay, I see how this all fits now. Bug 1164492 was filed to have gnome-boxes temporarily drop the dependency on libvirt-daemon-config-network for the F24 release, due to the conflicts as described in Bug 1146232. So what you've seen is definitely just a side effect of the workaround for Bug 1146232. For post-F24 there is a different workaround (which will probably be annoying in some different way :-P), and we can hopefully come up with a permanent solution "some day". I'm going to mark this as a duplicate of 1146232. Cole - feel free to change that if you think it should instead be applied to something else. *** This bug has been marked as a duplicate of bug 1146232 ***