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 1293878 - The vnc guest name shows incorrect when connected by remote-viewer a connection file
Summary: The vnc guest name shows incorrect when connected by remote-viewer a connecti...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-viewer
Version: 6.8
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virt Viewer Maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1293879
TreeView+ depends on / blocked
 
Reported: 2015-12-23 10:45 UTC by mxie@redhat.com
Modified: 2016-05-10 21:20 UTC (History)
8 users (show)

Fixed In Version: virt-viewer-2.0-10.el6
Doc Type: Bug Fix
Doc Text:
Cause: virt-viewer didn't try to set the display name when connecting to VNC guest. Consequence: The name of the VNC guest was not set. Fix: Set the guest name when connecting to a VNC guest. Result: Guest name is showed properly.
Clone Of:
: 1293879 (view as bug list)
Environment:
Last Closed: 2016-05-10 21:20:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot1 (499.10 KB, image/png)
2015-12-23 10:45 UTC, mxie@redhat.com 		no flags Details
screenshot2 (1.25 MB, image/png)
2015-12-23 10:46 UTC, mxie@redhat.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0832 0 normal SHIPPED_LIVE libgovirt, spice-gtk, usbredir, and virt-viewer bug fix update 2016-05-10 22:41:23 UTC

Description mxie@redhat.com 2015-12-23 10:45:03 UTC 
Created attachment 1108933 [details]
screenshot1

Description of problem:
The vnc guest name shows incorrect when connected by remote-viewer a connection file

Version-Release number of selected component (if applicable):
virt-viewer-2.0-9.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a vnc guest name "rhel6.7" and edit xml as below
 <graphics type='vnc' port='5901' autoport='no' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
 </graphics>

2.Start the vnc guest
#virsh start rhel6.7

3.Create an ini file,name "test.ini", format like following:
[virt-viewer]
type=vnc
host=localhost
port=5901

4.remote-viewer the connection file "test.ini" to connect the vnc guest 
#remote viewer test.ini

Actual results:
The vnc guest could be connected but guest's name shows the connection file's name, pls refer to screenshot1

Expected results:
The vnc guest could be connected and guest's name shows correct 

Addtional info:
The spice guest could show name correctly when connected by remote-viewer an connection file

Steps as below:
1.Prepare a spice guest name "2OS" and edit xml as below
 <graphics type='spice' port='5900' autoport='no' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
 </graphics>

2.Start the spice guest
#virsh start 2OS

3.Create an ini file,name "test.ini", format like following:
[virt-viewer]
type=spice
host=localhost
port=5900

4.remote-viewer the connection file "test.ini" to connect the spice guest and the spice guest shows name correctly, pls refer to screenshot2
#remote viewer test.ini
Comment 1 mxie@redhat.com 2015-12-23 10:46:17 UTC 
Created attachment 1108934 [details]
screenshot2
Comment 3 Fabiano Fidêncio 2015-12-23 11:00:01 UTC 
Okay. It's already fixed upstream by this commit: 772698a8a6e34c0b5051a3519f9284313426c1ca (Set guest name when using VNC)
Also, for completeness, we most likely would like to have this commit as well: fc2add5827c359ced244c4e0a9cb36d24c24ee83 (Set uuid when using VNC)
Comment 5 mxie@redhat.com 2016-01-04 05:56:57 UTC 
I can reproduce the bug with build:
virt-viewer-2.0-9.el6.x86_64

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

Steps to Reproduce:
1.Prepare a vnc guest name "rhel6.7" and edit xml as below
 <graphics type='vnc' port='5901' autoport='no' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
 </graphics>

2.Start the vnc guest
#virsh start rhel6.7

3.Create an ini file,name "test.ini", format like following:
[virt-viewer]
type=vnc
host=localhost
port=5901

4.remote-viewer the connection file "test.ini" to connect the vnc guest 
#remote viewer test.ini

Result now:
The vnc guest could be connected and guest's name shows QEMU(rhel6.7)

Hi Fidencio,

Whether the guest's name shows QEMU(rhel6.7) instead of "rhel6.7" could be accepted?
Comment 6 Fabiano Fidêncio 2016-01-04 08:12:12 UTC 
(In reply to mxie from comment #5)
> I can reproduce the bug with build:
> virt-viewer-2.0-9.el6.x86_64
> 
> Try to verify this bug with build:
> virt-viewer-2.0-10.el6.x86_64
> 
> Steps to Reproduce:
> 1.Prepare a vnc guest name "rhel6.7" and edit xml as below
>  <graphics type='vnc' port='5901' autoport='no' listen='127.0.0.1'>
>       <listen type='address' address='127.0.0.1'/>
>  </graphics>
> 
> 2.Start the vnc guest
> #virsh start rhel6.7
> 
> 3.Create an ini file,name "test.ini", format like following:
> [virt-viewer]
> type=vnc
> host=localhost
> port=5901
> 
> 4.remote-viewer the connection file "test.ini" to connect the vnc guest 
> #remote viewer test.ini
> 
> Result now:
> The vnc guest could be connected and guest's name shows QEMU(rhel6.7)
> 
> Hi Fidencio,
> 
> Whether the guest's name shows QEMU(rhel6.7) instead of "rhel6.7" could be
> accepted?

This is what's provided by gtk-vnc widget. If, for some reason, you believe that having "rhel6.7" instead of "QEMU(rhel6.7)" for vnc would be better, please, open a bug on gtk-vnc and set as dependency of this one. (TBH, I don't think we would have the bug approved for 6 cycle, maybe for the 7 one it's okay ...)
Comment 7 mxie@redhat.com 2016-01-04 09:13:04 UTC 
Thanks for Fidencio's quick reply 

According to commnet6 and Fidencio's reply, although the guest's name shows QEMU(rhel6.7) instead of "rhel6.7" is not very perfect, we all could understand the meaning of guest's name which means qemu start the guest "rhel6.7", so move the bug from ON_QA to VERIFIED.
Comment 9 errata-xmlrpc 2016-05-10 21:20:51 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
Note You need to log in before you can comment on or make changes to this bug.