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.

Created attachment 433817 [details]
blocking virt manager ui

Description of problem:

- i have a remote hypervisor i'm trying to connect to
- it's a qemu/kvm hypervisor, i pick the ssh tunnel for connection, in the hostname field i put "root@thehostname"
- I hit connect
- over 60 seconds pass by my laptop's clock. The UI gets blocked up and virt-manager looks like it's crashed.
- it eventually comes back and connects to the remote hypervisor.

(see screenshot)

Version-Release number of selected component (if applicable):
virt-manager-0.8.4-7.el6.noarch

How reproducible:
very

Steps to Reproduce:
see steps above

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Hmm, was the remote machine over a VPN connection or some other slow link? Not seeing that kind of delay with a close proximity remote host.

Do you have a lot of VMs on the remote host? Does the app lock at all after connecting?

Hi Cole, I am in the Westford office as is the remote machine - it's in the lab here in the building. No VPN connection.

There are 4 or 5 VMs on the host, but 1 is shut-off. If the app doesn't completely lock up, it works fine after connecting. 

The UI really shouldn't block, right?.... some kind of progress indicator would be good just so it's clear the app hasn't died.

Oh actually I might have lied. I may have been on the wireless VPN in the office.

*** This bug has been marked as a duplicate of bug 607735 ***