Prior to this update, when a SPICE console was launched from the Red Hat Enterprise Virtualization User Portal with the 'Native Client' invocation method and 'Open in Full Screen' selected, the display of the guest virtual machine were not always configured to match the client displays. After this update, the SPICE console will show a full-screen guest display for each client monitor.
Description of problem:
1. From the UserPortal, with the "Full screen" checkbox enabled, a 2nd display did not enable automatically as it should by default. Selecting "2" from the Displays menu on Remote Viewer was required.
2. After manually enabling the 2nd display, that display did not auto-sense the proper screen resolution.
Version-Release number of selected component (if applicable):
RHEL 6.5 guest
How reproducible: 100%
Steps to Reproduce:
1. Log into UserPortal
2. Check the Full Screen checkbox
3. Open a VM
4. The second display does not appear automatically
The second display must be manually enabled and the screen resolution is not as it should be set.
The second display appears in full screen
please reconsider severity/priority...
what is the launch method Browser plugin/Native and what client OS is used?
There were some bugs I can point you to If I know that.
The important thing for RHEL6.5 guest is to have Spice agent/RHEV agent/QXL driver installed and operational on the guest which means that RHEV agent reports to the RHEVM that QXL driver is installed ont the guest and This can be seen in RHEVM webadmind in Aplllication tab of VM details.
per discussion with byount, it sounds like this is launched in native client mode. The vv file format does not currently have a parameter for specifying auto-conf, so it just uses basic fullscreen mode. We'd need to add an auto-conf param to the vv file format, and the user portal would have to include that param in its vv-file.
we will address this issue in rhel 6.6 first( see bz 1083203 ).
moving to 3.5, and propose for 3.4.z. The 3.4.z will be built following the 3.4 release. This was discussed and agreed with Peter Manzella
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.