Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1289971

Summary: virt-viewer cannot reconnect libvirtd connection via ssh after libvirtd restart
Product: Red Hat Enterprise Linux 6 Reporter: Fabiano Fidêncio <fidencio>
Component: virt-viewerAssignee: Virt Viewer Maint <virt-viewer-maint>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.8CC: cfergeau, codong, dblechte, dyuan, fidencio, juzhou, mxie, mzhan, rbalakri, tzheng, virt-bugs, virt-viewer-maint, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-viewer-2.0-8.el6 Doc Type: Bug Fix
Doc Text:
Cause: Notifications about libvirt going away were not received when connecting to a VM hosted in a RHEL-7 (or newer). Consequence: virt-viewer was not able to reconnect to libvirtd after it goes away. Fix: Set keepAlive on the libvirt connection. Result: virt-viewer is able to reconnect to libvirtd after it does away.
 Story Points: ---
Clone Of: 1164052 Environment:
Last Closed: 2016-05-10 21:19:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1164052, 1243228, 1246395    
Bug Blocks:    

Comment 3 mxie@redhat.com 2015-12-17 09:02:17 UTC 
According the comment: one important info that has been missing about how to reproduce this bug is that the remote host *MUST* be a RHEL-7 or newer.Older versions of libvirt (in the remote host) don't present the keepalive problem,

I can reproduce the bug on below build with a RHEL7 remote host
virt-viewer-2.0-7.el6.x86_64

Try to verify this bug with build:
virt-viewer-2.0-8.el6.x86_64


Steps to Reproduce:
1. install a spice guest on a rhel7 remote host and shut it down
2. use virt-viewer to connect the guest on rhel6 host with --wait
#virt-viewer -c qemu+ssh://remote_rhel7_ip/system vm --wait --debug --spice-debug
3. restart libvirtd on rhel7 remote host
# service libvirtd restart


Results now:

Step 3:there is more debug message pop out on after libvirtd restart, 

#virt-viewer -c qemu+ssh://remote_rhel7_ip/system vm --wait --debug --spice-debug
(virt-viewer:23384): virt-viewer-DEBUG: Connect timer fired
(virt-viewer:23384): virt-viewer-DEBUG: initial connect
(virt-viewer:23384): virt-viewer-DEBUG: notebook show status 0x1adf000
(virt-viewer:23384): virt-viewer-DEBUG: Update timeout 0x1b4fe40 10 4000
(virt-viewer:23384): virt-viewer-DEBUG: Update timeout 0x1b4fe40 10 4000
(virt-viewer:23384): virt-viewer-DEBUG: Update timeout 0x1b4fe40 10 5000
(virt-viewer:23384): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 9d86c356-c434-4209-81d2-2f38533a2eb7
(virt-viewer:23384): virt-viewer-DEBUG: No guest-specific fullscreen config, using fallback
(virt-viewer:23384): virt-viewer-DEBUG: notebook show status 0x1adf000
(virt-viewer:23384): virt-viewer-DEBUG: Update timeout 0x1b4fe40 10 5000
(virt-viewer:23384): virt-viewer-DEBUG: Update timeout 0x1b4fe40 10 5000
(virt-viewer:23384): virt-viewer-DEBUG: Update timeout 0x1b4fe40 10 5000
(virt-viewer:23384): virt-viewer-DEBUG: notebook show status 0x1adf000
(virt-viewer:23384): virt-viewer-DEBUG: Guest test has not activated its display yet, waiting for it to start

So move this bug from ON_QA to VERIFIED.
Comment 5 errata-xmlrpc 2016-05-10 21:19:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0832.html