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 888594 - Add a more descriptive example in man page of remote-viewer
Summary: Add a more descriptive example in man page of remote-viewer
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-viewer
Version: 6.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Berrangé
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 960054
TreeView+ depends on / blocked
 
Reported: 2012-12-18 23:27 UTC by Nandini Chandra
Modified: 2018-12-01 18:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-08 15:35:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nandini Chandra 2012-12-18 23:27:53 UTC
Description of problem:
A more detailed example needs to be added to the man page of remote-viewer.

Version-Release number of selected component (if applicable):
RHEL 6.3


How reproducible:
NA

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Here's the current example stated in the man page of remote-viewer.
EXAMPLES
       To connect to SPICE server on host "makai" with port 5900

          remote-viewer spice://makai:5900



Expected results:
The SPICE server is enabled in the qemu-kvm process and the SPICE server listens on the KVM host that the guest is running on.

So,in order to connect to the guest 'guest1' running on host 'testvirt',run this command on a SPICE client(assuming that the SPICE server is listening on port 5900).

          remote-viewer spice://<KVM Hostname or IP add>:5900



Additional info:

Comment 2 Peter Schiffer 2012-12-19 12:24:28 UTC
remote-viewer(1) man page is part of the virt-viewer package

Comment 3 RHEL Program Management 2012-12-24 06:49:21 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 Marc-Andre Lureau 2013-05-08 15:35:27 UTC
Your proposed changes are misleading.

remote-viewer is not directly related to KVM, it can connect to any VNC server or any Spice server such as XSpice or Weston with Spice backend. 

There is no relation to mention to qemu-kvm o libvirt, this is what distinguishes from virt-viewer.


Note You need to log in before you can comment on or make changes to this bug.