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.
Description of problem:
"Graphical console is not yet active for guest" displays and fail to open the guest
Version-Release number of selected component (if applicable):
virt-manager-1.3.2-1.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Prepare a running spice guest with autoport setting to 'no'.
<graphics type='spice' autoport='no' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
</graphics>
2. Double click the guest in virt-manager.
Actual results:
"Graphical console is not yet active for guest" displays for the guest.
Expected results:
The graphical console should be connected correctly.
Additional info:
There is a "--attach" option for virt-viewer to connect to this kind of guest. So i think virt-manager should add some option or support this kind of guest by default.
-a, --attach
Instead of making a direct TCP/UNIX socket connection to the remote display, ask libvirt to provide a pre-connected socket for the display. This avoids the need to authenticate with the remote
display server directly. This option will only work when connecting to a guest that is running on the same host as the virt-viewer program. If attaching to the guest via libvirt fails, virt-
viewer will automatically fallback to trying a regular direct TCP/UNIX socket connection.
I can reproduce this bug with package:
virt-manager-1.3.2-1.el7.noarch
Steps are the same as description above.
Then try to verify with new build:
virt-manager-1.4.0-1.el7.noarch
Steps:
1. Prepare a running spice guest with autoport setting to 'no'.
<graphics type='spice' autoport='no' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
</graphics>
2. Double click the guest in virt-manager.
Results:
The graphical console is connected correctly.
According to the result above in the latest version of virt-manager, move this bug from ON_QA to VERIFIED.
I can reproduce this bug with <listen type='none'/> with package:
virt-manager-1.3.2-1.el7.noarch
Steps:
1. Prepare a running spice guest with <listen type = 'none'>.
<graphics type='spice'>
<listen type='none'/>
</graphics>
2. Double click the guest in virt-manager.
Actual results:
"Graphical console is not yet active for guest" displays for the guest.
Expected results:
The graphical console should be connected correctly.
Then try to verify with new build:
virt-manager-1.4.0-1.el7.noarch
Steps:
1. Prepare a running spice guest with <listen type='none'>.
<graphics type='spice'>
<listen type='none'/>
</graphics>
2. Double click the guest in virt-manager.
Results:
The graphical console is connected correctly.
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-2269.html
Description of problem: "Graphical console is not yet active for guest" displays and fail to open the guest Version-Release number of selected component (if applicable): virt-manager-1.3.2-1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Prepare a running spice guest with autoport setting to 'no'. <graphics type='spice' autoport='no' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> 2. Double click the guest in virt-manager. Actual results: "Graphical console is not yet active for guest" displays for the guest. Expected results: The graphical console should be connected correctly. Additional info: There is a "--attach" option for virt-viewer to connect to this kind of guest. So i think virt-manager should add some option or support this kind of guest by default. -a, --attach Instead of making a direct TCP/UNIX socket connection to the remote display, ask libvirt to provide a pre-connected socket for the display. This avoids the need to authenticate with the remote display server directly. This option will only work when connecting to a guest that is running on the same host as the virt-viewer program. If attaching to the guest via libvirt fails, virt- viewer will automatically fallback to trying a regular direct TCP/UNIX socket connection.