Bug 788686

Summary:	RFE: launch a separate thread for polling each connection
Product:	[Community] Virtualization Tools	Reporter:	Cole Robinson <crobinso>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, crobinso, xen-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-07 16:29:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Cole Robinson 2012-02-08 19:27:24 UTC

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.

Comment 1 Cole Robinson 2013-07-07 16:29:41 UTC

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.