Bug 787160

Summary: xorg-x11-drv-qxl: support multiple monitors & continuous resolutions
Product: Red Hat Enterprise Linux 6 Reporter: Alon Levy <alevy>
Component: xorg-x11-drv-qxlAssignee: Alon Levy <alevy>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: byount, cfergeau, dblechte, djasa, dyuan, lyarwood, mkrcmari, mzhan, rwu, ydu, zpeng
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: xorg-x11-drv-qxl-0.1.0-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 08:16:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 770842, 842298, 842305, 842310, 842411    
Bug Blocks: 787578, 977213, 978877, 978878, 978879, 978880, 978883, 978884, 978885, 978887, 978888, 978889, 978892, 978893, 978895, 979217, 979218, 979221, 1088390    

Description Alon Levy 2012-02-03 11:16:42 UTC
This bug is for the xf86-video-qxl part of bug 770842. The required changes are to have xf86-video-qxl support a single pci device with multiple monitors as implemented by said bug.

Comment 2 Alon Levy 2012-07-23 13:04:32 UTC
*** Bug 754105 has been marked as a duplicate of this bug. ***

Comment 4 Alon Levy 2012-11-03 20:55:43 UTC
For verification you need:

 spice-vdagent>=0.12.0-2 (actually 0.12.0-1 will work too but a bug is fixed in 0.12.0-2 relating to arbitrary resolution & multiple monitor mode setting code, better check with it.


xorg-x11-drv-qxl: should be fixed in 0.1.0-1 but there were some build changes, I'm not sure the package was built correctly, so I used 0.1.0-2 as the fixed-in package.


Comment 7 Marian Krcmarik 2012-11-04 22:55:05 UTC
*** Bug 677618 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2013-02-21 08:16:19 UTC
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.