Red Hat Bugzilla – Bug 1016606
Virtualization comps group should contain libvirt-daemon-config-network
Last modified: 2016-07-19 06:27:54 EDT
Description of problem:
I was following the F20 Virtualization Test Day instructions and installed F20 Beta TC2, followed by 'yum groupinstall virtualization'.
No default NAT network was configured, as confirmed by command 'sudo virsh net-list --all', due to missing libvirt-daemon-config-network.
After installing libvirt-daemon-config-network and manually restarting libvirtd, the default NAT network was set up.
? This is a requirement of libvirt.
I've added libvirt directly to comps, but it's worth figuring out how libvirt itself fell out of the dependency chain.
Sorry, I was going to fix this up earlier but something distracted me.
libvirt is actually a metapackage nowadays that just exists for 'yum install libvirt' back compat. It pulls in libvirt\* which is overkill for most people.
The virtualization group is just targeting kvm management with libvirt, so it only requires libvirt-daemon-kvm which pulls in the minimal bits necessary, and explicitly _not_ things like all every qemu emulator, libvirt virtualbox driver, etc.
libvirt-daemon-config-network was split out from libvirt-daemon-kvm because gnome-boxes doesn't need it, but for virt-manager usage it's expected to be there. So I think just adding libvirt-daemon-config-network to 'virtualization' is the ideal fix. I'll make that change, but revert it if I'm wrong :)
Yeah, go ahead and do a s/libvirt/libvirt-daemon-config-network/, then.
"yum install virt-manager" does not include libvirt-daemon-config-network. Starting virt-manager displays a notice that three packages are not installed with an offer to install them. Acceptance of the offer displays a message that they have already been installed, but libvirt-daemon-config-network is still missing.
FYI see 1081762. Gnome Boxes 3.12 now requires libvirt-daemon-config-network.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.