We disabled virtlogd introduced in libvirt 1.3 because it broke our convoluted/sophisticated logging setup resulting in libvirt not starting up. We should review and re-enable it to take benefit of it(rationale: https://www.redhat.com/archives/libvir-list/2015-November/msg00412.html), once we have a bit more time to do that properly (and once the new daemon gets some mileage), so targeting to 4.1
I forgot we already have one *** This bug has been marked as a duplicate of bug 1321010 ***