RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 884739 - graceful automatic handling of connection to unix socket-based connections
Summary: graceful automatic handling of connection to unix socket-based connections
Keywords:
Status: CLOSED DUPLICATE of bug 810576
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: virt-mgr-maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-06 16:18 UTC by David Jaša
Modified: 2013-04-09 02:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-09 02:22:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Jaša 2012-12-06 16:18:53 UTC 
Description of problem:
Currently, virt-manager:
  * doesn't connect automatically if libvirtd service comes up
  * throws exceptions when the service is stopped/restarted
these two make user experience way worse than necessary for no real reason.

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-15.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. configure libvirtd so that it doesn't require password to access qemu:///system
2. connect with virt-manager to qemu:///system session
3. stop libvirtd service
4. start libvirtd service
  
Actual results:
exception is thrown, virt-manager stays disconnected after the service comes up again

Expected results:
3. nothing happens on clean libvirtd exit, virt-manager just gracefully disconnects. Notification may be popped up if libvirt crashes (but that's not necessary)
4. libvirt watches for libvird socket, when it appears (or libvirt starts listening on it again), virt-manager automatically reconnects

Additional info:
Comment 1 Geyang Kong 2012-12-28 09:29:27 UTC 
Looks we've already got bug 810576 for this issue.
Comment 2 Dave Allan 2013-04-09 02:22:35 UTC 

*** This bug has been marked as a duplicate of bug 810576 ***
Note You need to log in before you can comment on or make changes to this bug.