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 1105530 - Blocking UI
Summary: Blocking UI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1138190
TreeView+ depends on / blocked
 
Reported: 2014-06-06 10:48 UTC by Jiri Prajzner
Modified: 2014-12-15 14:15 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1138190 (view as bug list)
Environment:
Last Closed: 2014-12-15 14:15:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jiri Prajzner 2014-06-06 10:48:18 UTC 
Description of problem:
Upon losing a connection to VM(s), the virt. mgr. UI freezes and it's necessary to force quit the vrt. mgr. UI

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

How reproducible:
Every time

Steps to Reproduce:
1. Open virt. mgr. UI
2. Open a connection to VM(s)
3. Drop the connection on VM(s) side

Actual results:
The virt. mgr. UI freezes and the user has to force quit it

Expected results:
The virt. mgr. UI doesn't freeze and notifies about the dropped / lost connection and tries to reconnect (it probably tries to reconnect in the background, but this is not visible to the user)

Additional info:
Comment 1 Jiri Prajzner 2014-06-06 11:01:46 UTC 
virt. mgr. version:
virt-manager-0.9.0-19.el6.x86_64
Comment 2 Giuseppe Scrivano 2014-06-30 14:06:41 UTC 
the upstream version is affected by the same issue.  The solution seems to be in the usage of the virConnectSetKeepAlive API so the libvirt client (virt-manager in this case) keeps regularly pinging the server and be able to detect a dropped connection.
Comment 3 Giuseppe Scrivano 2014-07-02 13:30:43 UTC 
fixed upstream with these patches:

commit 0c95a5e725256f552774db05cc2fa3bee3b1a25e
Author: Giuseppe Scrivano <gscrivan>
Date:   Tue Jul 1 15:01:58 2014 +0200

    console: prevent access to deleted objects
    
    last commits revealed that some objects can still be accessed by
    registered callbacks after the console is closed.  Unregister these
    callbacks.
    
    Signed-off-by: Giuseppe Scrivano <gscrivan>

commit dc1c22bd97aa9104a5299408934036530406f9ca
Author: Giuseppe Scrivano <gscrivan>
Date:   Tue Jul 1 13:06:05 2014 +0200

    virt-manager: check if still connected every 20 seconds
    
    Signed-off-by: Giuseppe Scrivano <gscrivan>

commit 8b94cfa073b517eb65ccf180004c76929c9ebf1a
Author: Giuseppe Scrivano <gscrivan>
Date:   Tue Jul 1 12:54:38 2014 +0200

    virtinst: add method to set connection keep-alive
    
    Signed-off-by: Giuseppe Scrivano <gscrivan>



This is going to be considered for 6.7, hopefully the change won't be too intrusive to be included.
Comment 4 tingting zheng 2014-07-28 09:34:46 UTC 
Hi,Jiri Prajzner
   I am confused by the steps in description,what do you mean in step 3:Drop the connection on VM(s) side.
   I only can reproduce the bug by adding a remote connection,open a guest console,then destroy the network in remote host,then virt-manager freeze.
Comment 5 Jiri Prajzner 2014-09-04 08:03:54 UTC 
(In reply to tingting zheng from comment #4)
> Hi,Jiri Prajzner
>    I am confused by the steps in description,what do you mean in step 3:Drop
> the connection on VM(s) side.
>    I only can reproduce the bug by adding a remote connection,open a guest
> console,then destroy the network in remote host,then virt-manager freeze.

hi,

the way you reprduced it is exactly what i meant.
apologies for vague description and late reply.
Comment 6 Giuseppe Scrivano 2014-12-15 14:15:32 UTC 
I have evaluated the backport and unfortunately it doesn't apply cleanly in the virt-manager version we ship in RHEL-6.  I would prefer to not introduce new changes that are not already tested to address a non-serious issue like this one at a so late stage in the RHEL-6 development.  Please re-open if you disagree with this decision.
Note You need to log in before you can comment on or make changes to this bug.