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.
Descriptionmxie@redhat.com
2016-09-19 11:30:01 UTC
Created attachment 1202452[details]
virt-viewer.log
Description of problem:
[RFE]Should add ssh-agent info for virt-viewer -c connecting in manual page
Version-Release number of selected component (if applicable):
virt-viewer-2.0-12.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Prepare a linux guest with spice+qxl mode and there is service spice-vdagentd running in guest on hostA
# virsh dumpxml rhel6.7withcdrom
<channel type='spicevmc'>
<target type='virtio' name='com.redhat.spice.0' state='connected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<graphics type='spice' port='5902' autoport='yes' listen='127.0.0.1'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<video>
<model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
2.Don't configure ssh-agent for hostA on hostB and connect the guest of hostA at hostB
# virt-viewer -c qemu+ssh://10.66.4.242/system rhel6.7withcdrom
** (virt-viewer:24537): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-LlBTlBBNvS: Connection refused
root.4.242's password:
root.4.242's password:
root.4.242's password:
root.4.242's password: root.4.242's password:
(virt-viewer:24537): GSpice-WARNING **: Warning no automount-inhibiting implementation available
3.There are many problems using step3 to open guest console without configure ssh-agent on hostB , such as:the mouse and keyboard can't be used in guest ,the guest console has no graphic after connecting sometimes and the terminal couldn't be used after closing virt-viewer as below(can't input any word)
# virt-viewer -c qemu+ssh://10.66.4.242/system rhel6.7withcdrom
** (virt-viewer:24537): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-LlBTlBBNvS: Connection refused
root.4.242's password:
root.4.242's password:
root.4.242's password:
root.4.242's password: root.4.242's password:
(virt-viewer:24537): GSpice-WARNING **: Warning no automount-inhibiting implementation available
(virt-viewer:24537): GSpice-WARNING **: incomplete link header (0/16)
(virt-viewer:24537): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
(virt-viewer:24537): GSpice-WARNING **: channel_connect: channel setup incomplete
(virt-viewer:24537): GSpice-WARNING **: incomplete link header (0/16)
(virt-viewer:24537): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
(virt-viewer:24537): GSpice-WARNING **: channel_connect: channel setup incomplete
[root@localhost Desktop(keystone_admin)]#
Connection closed by 10.66.4.242
Connection closed by 10.66.4.242
bash: A: command not found...
[root@localhost Desktop(keystone_admin)]# bash: A: command not found...
[root@localhost Desktop(keystone_admin)]#
** (virt-viewer:24646): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-LlBTlBBNvS: Connection refused
(virt-viewer:24646): virt-viewer-DEBUG: connecting ...
(virt-viewer:24646): virt-viewer-DEBUG: Opening connection to libvirt with URI qemu+ssh://10.66.4.242/system
(virt-viewer:24646): virt-viewer-DEBUG: Add handle 6 1 0x1b34e00
root.4.242's password:
root.4.242's password:
4.Could solve all problems of step3 if setting ssh-agent on hostB and then do step2 again, but there is no info about how to configure ssh-agent before doing virt-viewer -c qemu+ssh in virt-viewer manual page
# man virt-viewer |grep -i ssh-agent
#
Actual results:
As above description
Expected results:
Should add ssh-agent info for virt-viewer -c connecting in manual page ,then customer will know how to solve the problem which maybe met in step3
Additional info:
Comment 2Christophe Fergeau
2016-12-06 13:17:38 UTC
I verified it with virt-viewer-5.0-2.el7.x86_64 and below examples are added in manual page.
To connect to a remote host using SSH, lookup the guest config and then make a tunnelled connection of the console
virt-viewer --connect qemu+ssh://root/system demo
When using a SSH tunnel to connect to a SPICE console, it's recommended to have ssh-agent running to avoid getting multiple authentication prompts.
So move the 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:1849
Created attachment 1202452 [details] virt-viewer.log Description of problem: [RFE]Should add ssh-agent info for virt-viewer -c connecting in manual page Version-Release number of selected component (if applicable): virt-viewer-2.0-12.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Prepare a linux guest with spice+qxl mode and there is service spice-vdagentd running in guest on hostA # virsh dumpxml rhel6.7withcdrom <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <graphics type='spice' port='5902' autoport='yes' listen='127.0.0.1'> <listen type='address' address='127.0.0.1'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> 2.Don't configure ssh-agent for hostA on hostB and connect the guest of hostA at hostB # virt-viewer -c qemu+ssh://10.66.4.242/system rhel6.7withcdrom ** (virt-viewer:24537): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-LlBTlBBNvS: Connection refused root.4.242's password: root.4.242's password: root.4.242's password: root.4.242's password: root.4.242's password: (virt-viewer:24537): GSpice-WARNING **: Warning no automount-inhibiting implementation available 3.There are many problems using step3 to open guest console without configure ssh-agent on hostB , such as:the mouse and keyboard can't be used in guest ,the guest console has no graphic after connecting sometimes and the terminal couldn't be used after closing virt-viewer as below(can't input any word) # virt-viewer -c qemu+ssh://10.66.4.242/system rhel6.7withcdrom ** (virt-viewer:24537): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-LlBTlBBNvS: Connection refused root.4.242's password: root.4.242's password: root.4.242's password: root.4.242's password: root.4.242's password: (virt-viewer:24537): GSpice-WARNING **: Warning no automount-inhibiting implementation available (virt-viewer:24537): GSpice-WARNING **: incomplete link header (0/16) (virt-viewer:24537): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed (virt-viewer:24537): GSpice-WARNING **: channel_connect: channel setup incomplete (virt-viewer:24537): GSpice-WARNING **: incomplete link header (0/16) (virt-viewer:24537): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed (virt-viewer:24537): GSpice-WARNING **: channel_connect: channel setup incomplete [root@localhost Desktop(keystone_admin)]# Connection closed by 10.66.4.242 Connection closed by 10.66.4.242 bash: A: command not found... [root@localhost Desktop(keystone_admin)]# bash: A: command not found... [root@localhost Desktop(keystone_admin)]# ** (virt-viewer:24646): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-LlBTlBBNvS: Connection refused (virt-viewer:24646): virt-viewer-DEBUG: connecting ... (virt-viewer:24646): virt-viewer-DEBUG: Opening connection to libvirt with URI qemu+ssh://10.66.4.242/system (virt-viewer:24646): virt-viewer-DEBUG: Add handle 6 1 0x1b34e00 root.4.242's password: root.4.242's password: 4.Could solve all problems of step3 if setting ssh-agent on hostB and then do step2 again, but there is no info about how to configure ssh-agent before doing virt-viewer -c qemu+ssh in virt-viewer manual page # man virt-viewer |grep -i ssh-agent # Actual results: As above description Expected results: Should add ssh-agent info for virt-viewer -c connecting in manual page ,then customer will know how to solve the problem which maybe met in step3 Additional info: