|Thursday Sep 17, 2009||All day||#fedora-test-day (webchat)|
What to test?
Today's installment of Fedora Test Day will focus on Virtualization improvements in Fedora 12, such as:
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your graphics card and provide feedback.
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - Mark McLoughlin
- Quality Assurance -
What's needed to test
- A fully updated Fedora 12 Rawhide machine. See instructions below
- Hardware virtualization support (e.g. Intel VT or AMD-V). If unavailable, you can still help with testing QEMU support.
- At least one guest image installed before the test day.
- Up to 10-20Gb free disk space. Guest images take up a lot of space.
- See test areas below for area specific requirements
How to test?
Update your system to the latest rawhide using one of the following techniques.
Prepare your system
- Install from a nearby rawhide mirror
- Download and install Test Day Live Image
- Download and install Fedora 12 Alpha
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Things to test, roughly in dependency order:
Perform each of the following test cases that you are able to with the resources available to you. Some of the tests depend on the others, so obviously if X fails to run with kernel mode setting for you, you will not be able meaningfully to test video playback or 3D application on top of KMS, for instance.
Report your results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component xorg-x11-drv-intel. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Follow the instructions on this page to ensure you include sufficient information in the report. Once you have completed the tests, add your results to the Results table below, following the example results as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the comments column (as in the example line). If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the multihead test as you have only one display), enter the word N/A. In the comments column, you can enter the model name and PCI device ID (vendor ID is usually 8086) of your card, if you know it - you can usually find this information in the output of the command lspci -nn.