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
2015-12-23 10:49:44 UTC
The bug also be reproduced on rhel7, so clone to rhel7
Version-Release number of selected component (if applicable):
virt-viewer-2.0-6.el7.x86_64
+++ This bug was initially created as a clone of Bug #1293878 +++
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
--- Additional comment from mxie on 2015-12-23 05:46 EST ---
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)
I can reproduce it with virt-viewer-2.0-6.el7.x86_64.
Then updated virt-viewer to latest virt-viewer-2.0-7.el7.x86_64. The title displays correctly.
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://rhn.redhat.com/errata/RHBA-2016-2229.html