Bug 452466

Summary:	virtmanager-GUI writes "localhost status:disconnected", but virt machines are running
Product:	Red Hat Enterprise Linux 5	Reporter:	Petr Sklenar <psklenar>
Component:	virt-manager	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED NOTABUG	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.2	CC:	crobinso
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-06-23 20:44:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Sklenar 2008-06-23 07:40:33 UTC

Description of problem:
GUI of virtmanager writes localhost disconnected, but virt machines are running

Version-Release number of selected component (if applicable):
virt-manager-0.5.3-8.el5

How reproducible:
always

Steps to Reproduce:
1.open virt-manager
2.create or start some virt-machines
3.close virt-manager
4.open virt-manager  

Actual results:
Localhost status is written disconnected, but all virtmachines are running

Expected results:
There should be written localhost connected, because all virt-machines are
running in background.

Additional info:

Comment 1 Cole Robinson 2008-06-23 20:44:51 UTC

This is not a bug, the terminology here is just a bit misleading. Virt manager
can connect to multiple hypervisors at the same time, with each hypervisor
listed as a tree entry and its VMs as the entries children. Since you may not
want an active connection to each hypervisor, polling for resources/taking up
bandwidth, you can connect or disconnect from each hypervisor indivdually. On
start up all connections are disconnected, which is what you are seeing. Double
click the connection and it will connect, listing your VMs.

Closing as NOTABUG.