Red Hat Bugzilla – Bug 867546
fresh install of libvirt-daemon-config-network requires libvirtd restart to define+start default network
Last modified: 2016-05-08 20:03:50 EDT
yum install -y virt-manager
This picks up libvirt including libvirt-daemon-config-network-0.10.2-3.fc18.x86_64
run virt-manager and find there is no network available.
virsh net-list --all is blank
systemctl restart libvirtd.service
the default NAT network will be available.
So it seems that the problem is that the libvirt-daemon package is installed and started before the %post script for libvirt-deamon-config-network is run.
Perhaps that script should check for libvirtd already running and, if so, use virsh define instead of directly placing the file in /etc/libvirt?
Still relevant on F20
Patch was proposed on the upstream list:
*** Bug 1224398 has been marked as a duplicate of this bug. ***
Round #2: http://www.redhat.com/archives/libvir-list/2016-April/msg01680.html
libvirt-22.214.171.124-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f5b59b4ca5
libvirt-126.96.36.199-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f5b59b4ca5
libvirt-188.8.131.52-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.