Bug 1000598

Summary:	Multi-monitor Spice limitations for RHEL guests in RHEV 3.2 need to be documented
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Bryan Yount <byount>
Component:	Documentation	Assignee:	Andrew Dahms <adahms>
Status:	CLOSED DUPLICATE	QA Contact:	ecs-bugs
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	acathrow, gklein, rmcswain, yeylon, zdover
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Instance Name: Not Defined Build: CSProcessor Builder Version 1.8 Build Name: 9026, Technical Reference Guide-3.2-null Build Date: 13-05-2013 13:48:47
Last Closed:	2013-12-23 00:29:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bryan Yount 2013-08-23 19:34:01 UTC

Describe the issue:
The documentation does not list the current limitations of RHEL guests running in RHEV 3.2 when >1 monitor is enabled.


Suggestions for improvement:
Unsure. Maybe we should add a note to the Installation Guide (1.6. Supported Virtual Machine Operating Systems) that indicates RHEL 6 guests are currently limited to a maximum display resolution until RHEV 3.3 is released.


Additional information:
The Technical Reference Guide (10.8. SPICE limitations), should also list the limitation once we find out from engineering. I sent an email to spice-list with the title "Maximum resolution for RHEL guests in RHEV 3.2 with 2+ displays"

Comment 1 Tim Hildred 2013-10-28 00:05:21 UTC

Reassigning to Jodi Biddle (jbiddle) as I am no longer working on Red Hat Enterprise Virtualization documentation.

Comment 2 Andrew Dahms 2013-12-23 00:29:12 UTC

Information on enabling and using multiple monitors in RHEV 3.3 has been added to the User Portal Guide and Power User Portal Guide, including limitations in screen resolution and use of the displays option.

*** This bug has been marked as a duplicate of bug 974652 ***