KVM-specific constructs used even when the corresponding control variables in /etc/conf.d/libvirtd are turned off Also, LIBVIRTD_NET_SHUTDOWN should really be called LIBVIRTD_KVM_NET_SHUTDOWN, since it also depends on the use of KVM-specific constructs. Reproducible: Always
Created attachment 290453 [details] Sanitize /etc/{init,conf}.d/libvirtd for non-KVM systems
I've implemented this, slightly differently however with room to grow for supporting other hypervisors. Check out libvirt-0.9.10.