|
|
| Line 1: |
Line 1: |
| = SPICE protocol / QXL driver for guests =
| | #REDIRECT Features |
| | |
| Add SPICE graphics protocol for guests
| |
| | |
| == Summary ==
| |
| | |
| == Owner ==
| |
| * Name: [[User:Rjones|Richard Jones]]
| |
| * email: rjones@redhat.com
| |
| | |
| == Current status ==
| |
| * Targeted release: [[Releases/11|Fedora 11]]
| |
| * Last updated: 2009-02-30
| |
| * Percentage of completion: XX%
| |
| | |
| == Detailed Description ==
| |
| Current KVM-based virtual machines use an emulated Cirrus Logic graphics driver. This has numerous problems, the main ones being that it is slow and has a limited resolution. When Red Hat acquired Qumranet, we acquired a closed source protocol called SPICE which removes these limitations, is highly optimized, and supports such features as on-the-fly compression of video streams. The plan is to fully open source this and include all the pieces in QEMU/KVM, libvirt, Xorg, virt-install and virt-manager.
| |
| | |
| == Benefit to Fedora ==
| |
| Fedora will benefit because guests will be able to use a graphics protocol which is much more suitable for virtual machines. They will be able to use higher resolutions and more colors, support 2D acceleration, and be able to display video streams. These are all things which are not possible with the current Cirrus Logic device emulation.
| |
| | |
| == Scope ==
| |
| <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
| |
| | |
| == How To Test ==
| |
| <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
| |
| | |
| Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
| |
| | |
| A good "how to test" should answer these four questions:
| |
| | |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this feature? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the feature is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| | |
| -->
| |
| | |
| == User Experience ==
| |
| Users will notice faster guest consoles. They will be able to select high resolutions and color-depths than currently possible. Features such as video playback inside the guest will be possible.
| |
| | |
| == Dependencies ==
| |
| <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? -->
| |
| | |
| == Contingency Plan ==
| |
| None necessary, we will just continue to use the Cirrus Logic driver.
| |
| | |
| == Documentation ==
| |
| <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
| |
| | |
| | |
| == Release Notes ==
| |
| | |
| <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
| |
| <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
| |
| | |
| == Comments and Discussion ==
| |
| | |
| * See [[Talk:Features/SPICE graphics protocol for guests]]
| |
| | |
| [[Category:Virtualization|SPICE graphics protocol for guests]]
| |
| | |
| [[Category:FeaturePageIncomplete]]
| |
| <!-- When your feature page is completed and ready for review -->
| |
| <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
| |
| <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
| |
| <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
| |
