[ebuild R ] app-emulation/libvirt-0.7.6-r1 USE="caps libvirtd lvm nls numa -avahi -iscsi -lxc -network -nfs -openvz -parted -phyp -policykit -python -qemu -sasl (-selinux) -udev -uml -virtualbox -xen" 0 kB host linux # virsh error: no hypervisor driver available error: failed to connect to the hypervisor pkg_setup should check that one of the hypervisors is selected
Unfortunately people on the Gentoo Dev ML have railed against having a package fail in pkg_setup() and as such this prevention code was removed by Diego.
(In reply to comment #1) > Unfortunately people on the Gentoo Dev ML have railed against having a package > fail in pkg_setup() and as such this prevention code was removed by Diego. > I don't think QA wants ebuilds to be installable so they don't work at runtime. I do know that Diego wants the defaults to work.
Actually the package works just fine. You're default config attempts to connect to qemu:///system, which is a localhost connection. However at work those exact same USE flags render a perfectly working libvirt... Why? Because I don't actually host any virtual machines locally. So my default in the config file has been changed to automatically connect to the main server I use for virtualization. There's a few people in #gentoo-virtualization that actually use the ebuild like this. Please look at the -c | --connect option if you don't want to change your defaults. People actually don't want ebuilds to fail in pkg_setup. There's been a giant stink about this. For anyone that wants to implement this in a "doesn't fail in pkg_setup" case is, if libvirtd is enabled then lxc, qemu, uml, virtualbox, or xen must be enabled.