Description of problem: There is a bug in spice: when no color-depth is specified in vv file, after resize of remote-viewer window, color-depth automatically goes to 32 bits (see https://bugzilla.redhat.com/show_bug.cgi?id=1543538). After this behaviour will be changed, there arises a problem: When user unchecks 'Enable Wan Options' dialog in 'RHV Admin Portal'->'Console Options', the color depth will not return to 32 bits. So I propose to always have color-depth parameter in vv file for vms, which are capable to have 16 bit color depth. Version-Release number of selected component (if applicable): rhv4.2.1.6-0.1.el7 RHV-toolsSetup_4.2_2.iso
Why is “wan options” not enough?h
(In reply to Michal Skrivanek from comment #1) > Why is “wan options” not enough?h I do not know what you exactly have on your mind. There is no “wan options” in vv-file. If you check 'Enable WAN Options', then two lines are added to the vv-file: .. color-depth=16 disable-effects= .. and color depth of Win7 guest change to 16 bits. But if you then uncheck "WAN Options" check-box, options listed above are not added to vv file - so color-depth of guest is not enhanced to 32 bits and stays on 16. And this is a problem. Now undone "WAN Options" (i.e. return to 32 bits) is (partly) functional thanks to https://bugzilla.redhat.com/show_bug.cgi?id=1543538 - color depth can be returned to 32 bits by resizing remote-viewer's window (of guest) - this is certainly not a proper behaviour. After https://bugzilla.redhat.com/show_bug.cgi?id=1543538 will be resolved, user cannot return to 32 bits color depth by unchecking 'Enable WAN Options' check-box at all. If you pass no 'color-depth' parameter to remote-viewer, color depth remains intact. From man-pages of remote-viewer: .. "color-depth" (integer) Set the color depth of the guest display (16 or 32). .. So I propose to always have 'color-depth' in vv-file for guest OS which is capable of transition between 16 and 32 color-depth.
This will not make it in a reasonable time. Please re-open if you still feel this should be fixed