Comment # 5 on bug 1001446 from James Fehlig

Upgrades should be handled by this hunk in the libvirt spec file

# In upgrade scenario we must explicitly enable virtlockd/virtlogd
# sockets, if libvirtd is already enabled and start them if
# libvirtd is running, otherwise you'll get failures to start
# guests
%triggerpostun daemon -- libvirt-daemon < 1.3.0
if [ $1 -ge 1 ] ; then
%if %{with_systemd}
        /usr/bin/systemctl is-enabled libvirtd.service 1>/dev/null 2>&1 &&
            /usr/bin/systemctl enable virtlogd.socket || :
        /usr/bin/systemctl is-active libvirtd.service 1>/dev/null 2>&1 &&
            /usr/bin/systemctl start virtlogd.socket || :
%else
        /sbin/chkconfig libvirtd 1>/dev/null 2>&1 &&
            /sbin/chkconfig virtlogd on || :
        /sbin/service libvirtd status 1>/dev/null 2>&1 &&
            /sbin/service virtlogd start || :
%endif
fi

So I'm not really sure how you got into this state. I thought we had all the
upgrade bugs worked out.