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.
Description of problem:
virt-manager failed to connect to remote guest console for VNC with listen type none
Version-Release number of selected component (if applicable):
virt-manager-1.4.1-2.el7.noarch
libvirt-3.2.0-3.virtcov.el7.x86_64
qemu-kvm-rhev-2.9.0-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
Need 2 hosts: HostA and HostB.
1. Prepare a vnc guest with listen type equals none on HostA.
# virsh dumpxml esx5.5-rhel7.2-x86_64 --security-info
...
<graphics type='vnc' port='-1' autoport='yes'>
<listen type='none'/>
</graphics>
2. Launch virt-manager on HostB, File->Add connection->Hypervisor choosing 'QEMU/KVM'->Tick 'Connect to remote host'->Method 'SSH'->Username: root ->Hostname: $host A ->Connect.
3. Open guest console 'esx5.5-rhel7.2-x86_64' on hostA.
Actual results:
Failed to connect to guest console with error:
Viewer was disconnected.
SSH tunnel error output: nc: invalid option -- '1'
Ncat: Try `--help' or man(1) ncat for more information, usage options and help. QUITTING.
Expected results:
Can connect to guest console successfully.
Additional info:
Expected result isn't that virt-manager is able to connect to guest console successfully, it should print a meaningful error message:
Guest is on a remote host, but is only configured to allow local file descriptor connections.
Pavel sent a libvirt patch that will fix this, but I added a fix to virt-manager too
commit cd0e3a897c2fa0f7efb0149dcbb6848844fb724b
Author: Cole Robinson <crobinso>
Date: Thu Apr 27 15:28:41 2017 -0400
sshtunnels: Detect listen type=none for VNC (bz 1445714)
Try to verify this bug with new package:
virt-manager-1.4.1-3.el7.noarch
libvirt-3.2.0-4.el7.x86_64
qemu-kvm-rhev-2.9.0-2.el7.x86_64
Steps:
Need 2 hosts: HostA and HostB.
1. Prepare a vnc guest with listen type equals none on HostA.
# virsh dumpxml rhel7.3 --security-info
...
<graphics type='vnc' port='-1' autoport='yes'>
<listen type='none'/>
</graphics>
2. Launch virt-manager on HostB, File->Add connection->Hypervisor choosing 'QEMU/KVM'->Tick 'Connect to remote host'->Method 'SSH'->Username: root ->Hostname: $host A ->Connect.
3. Open guest console 'rhel7.3' on hostA.
Result: Failed to connect to guest 'rhel7.3' with clear error.
Error connecting to graphical console:
Guest is on a remote host, but is only configured to allow local file descriptor connections.
So move this bug from ON_QA to VERIFIED.
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://access.redhat.com/errata/RHBA-2017:2072
Description of problem: virt-manager failed to connect to remote guest console for VNC with listen type none Version-Release number of selected component (if applicable): virt-manager-1.4.1-2.el7.noarch libvirt-3.2.0-3.virtcov.el7.x86_64 qemu-kvm-rhev-2.9.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: Need 2 hosts: HostA and HostB. 1. Prepare a vnc guest with listen type equals none on HostA. # virsh dumpxml esx5.5-rhel7.2-x86_64 --security-info ... <graphics type='vnc' port='-1' autoport='yes'> <listen type='none'/> </graphics> 2. Launch virt-manager on HostB, File->Add connection->Hypervisor choosing 'QEMU/KVM'->Tick 'Connect to remote host'->Method 'SSH'->Username: root ->Hostname: $host A ->Connect. 3. Open guest console 'esx5.5-rhel7.2-x86_64' on hostA. Actual results: Failed to connect to guest console with error: Viewer was disconnected. SSH tunnel error output: nc: invalid option -- '1' Ncat: Try `--help' or man(1) ncat for more information, usage options and help. QUITTING. Expected results: Can connect to guest console successfully. Additional info: