Bug 813267 - cann't show vnc server status in monitor via "info vnc" when connect to a listening vnc with "reverse"
Summary: cann't show vnc server status in monitor via "info vnc" when connect to a lis...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Luiz Capitulino
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1461682
TreeView+ depends on / blocked
 
Reported: 2012-04-17 11:16 UTC by Sibiao Luo
Modified: 2017-06-15 07:36 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1461682 (view as bug list)
Environment:
Last Closed: 2012-04-27 00:18:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sibiao Luo 2012-04-17 11:16:02 UTC 
Description of problem:
connect to a listening VNC client via a "reverse" connection, the client is specified by the display, but "info vnc" cann't get the vnc server status in the monitor.

Version-Release number of selected component (if applicable):
# uname -r && rpm -q qemu-kvm
2.6.32-262.el6.x86_64
qemu-kvm-0.12.1.2-2.275.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.launch a listening vnc on host A by:
# vncviewer -listen 7000
2.launch qemu-kvm process and try to connect to the listening vnc on host B by:
...-vnc ${ip_of_host_A's}:7000,"reverse"
3.run "info vnc" in the monitor.
(qemu) info vnc

Actual results:
after the step 3, "info vnc" cann't get the vnc server status.

Expected results:
"info vnc" can get the vnc server status in the monitor.

Additional info:
Comment 2 Ademar Reis 2012-04-17 19:34:34 UTC 
corner case, not critical, deferring to rhel6.4
Comment 3 Luiz Capitulino 2012-04-26 18:10:19 UTC 
This is more like a missing feature than a bug. Also, HMP is not supported in RHEL, so the only reason to implement this as a RHEL feature would be a real need from one of our stack's components (vs. "this is nice to the end user").

I'd close this as WONTFIX, but I'll let Ademar decide.

PS: You're welcome to report this upstream.
Comment 4 Ademar Reis 2012-04-27 00:18:48 UTC 
Closing as wontfix. It will get to RHEL7 automatically if fixed upstream on time, but we won't focus on it for now.
Note You need to log in before you can comment on or make changes to this bug.