AppArmor should not be not causing this connection refused message because skogs said there is nothing in the dmesg indicating a denial. Indeed, skogs removal of 'audit deny /etc/apparmor.d/libvirt/** wxl,' should not have done anything because the libvirtd profile disallows this access regardless (and that rule just makes sure it is logged. What probably happened is the libvirtd restart or system reboot 'cleaned up' libvirt so it would function correctly again.
AppArmor should not be not causing this connection refused message because skogs said there is nothing in the dmesg indicating a denial. Indeed, skogs removal of 'audit deny /etc/apparmor. d/libvirt/ ** wxl,' should not have done anything because the libvirtd profile disallows this access regardless (and that rule just makes sure it is logged. What probably happened is the libvirtd restart or system reboot 'cleaned up' libvirt so it would function correctly again.
Please file a different bug-- this one is fixed.