Hide Forgot
Some context: https://bugzilla.redhat.com/show_bug.cgi?id=766796 If a libvirt host goes down or a connection just blocks for some reason, all tick polling for other well behaved connections stalls. We should fire off a thread for each connection. This might also give us an opportunity to see that a connection has stalled and maybe update the UI to that effect, or auto close the connection.
Actually given the issues I pointed out in the other bug, a hung connection can easily hang the whole app if you try to open one of its VMs. Going through the effort of polling in separate threads when that bigger issue is basically intractable isn't really worth the effort.