*** Bug 978892 has been marked as a duplicate of this bug. ***
*** Bug 978888 has been marked as a duplicate of this bug. ***
*** Bug 978887 has been marked as a duplicate of this bug. ***
*** Bug 978883 has been marked as a duplicate of this bug. ***
*** Bug 978880 has been marked as a duplicate of this bug. ***
*** Bug 978877 has been marked as a duplicate of this bug. ***
The only part of the Tech Ref that currently mentions QXL drivers is 9.4, "System Devices", which is included below in full:
9.4. System Devices
System devices are critical for the guest to run and cannot be removed. Each system device attached to a guest also takes up an available PCI slot. The default system devices are:
the host bridge,
the ISA bridge and USB bridge (The USB and ISA bridges are the same device),
the graphics card (using either the Cirrus or qxl driver), and
the memory balloon device.
1. Are QXL devices anything more than "virtual monitors"?
2. Does this bug need to go into technical detail about how the QXL device or
QXL driver works? If so, whom can I ask for information about the technical
3. (This is sort of a restatement of 2) Will it suffice to mention in the
documentation that RHEV supports QXL and QXL now supports multiple monitor
Thanks in advance.
This changes the way "multiple Monitors" is implemented, for previous releases each monitor configured had a "virtual PCI video card", with this release a qxl device can have multiple virtual monitors attached.
There are number of k.bases on how to configure monitors with RHEL guest, this changes the implementation so maybe it's worth having this documented.
Shachar, this doesn't change the flow in RHEV, right ?
*** This bug has been marked as a duplicate of bug 977213 ***