Bug 452466 - virtmanager-GUI writes "localhost status:disconnected", but virt machines are running
virtmanager-GUI writes "localhost status:disconnected", but virt machines are...
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Daniel Berrange
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2008-06-23 03:40 EDT by Petr Sklenar
Modified: 2009-12-14 16:16 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-23 16:44:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Petr Sklenar 2008-06-23 03:40:33 EDT
Description of problem:
GUI of virtmanager writes localhost disconnected, but virt machines are running

Version-Release number of selected component (if applicable):

How reproducible:

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 16:44:51 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.