Hide Forgot
Description of problem: Run virt-viewer --verbose to display verbose information,it doesn't display verbose information. Version-Release number of selected component (if applicable): virt-viewer-0.2.1-3.el6.x86_64 How reproducible: always Steps to Reproduce: 1.virt-viewer --verbose rhel5 2. 3. Actual results: virt-viewer doesn't display verbose information. Expected results: It should display verbose information. Additional info:
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Verified with the following component: virt-viewer-0.4.1-4.el6.x86_64 Steps: 1. # virt-viewer --verbose fedora Opening connection to libvirt with URI <null> Guest fedora is running, determining display Guest (null) has a spice display Opening direct TCP connection to display at 127.0.0.1:5900 (Guest window pop-up) 2.# virt-viewer --connect qemu+ssh://10.66.3.130/system demo --verbose Opening connection to libvirt with URI qemu+ssh://10.66.3.130/system Guest demo is running, determining display Guest (null) has a spice display Opening indirect TCP connection to display at 0.0.0.0:5900 Setting up SSH tunnel via (null)@10.66.3.130 (Guest window pop-up) So move the status of this bug to verified.
'vnc' graphics is also OK. # virt-viewer -v fedora Opening connection to libvirt with URI <null> Guest fedora is running, determining display Guest (null) has a vnc display Opening direct TCP connection to display at 127.0.0.1:5900 (Guest window pop-up) # virt-viewer --connect qemu+ssh://10.66.3.130/system demo -v Opening connection to libvirt with URI qemu+ssh://10.66.3.130/system Guest demo is running, determining display Guest (null) has a vnc display Opening indirect TCP connection to display at 127.0.0.1:5900 Setting up SSH tunnel via (null)@10.66.3.130 (Guest window pop-up)
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. http://rhn.redhat.com/errata/RHEA-2011-1614.html