m (Corrected wiki syntax) |
m (adjusted wording) |
||
Line 46: | Line 46: | ||
Testing requires the latest virtualization software included in Fedora Rawhide. Update your system to the latest rawhide using one of the following techniques. | Testing requires the latest virtualization software included in Fedora Rawhide. Update your system to the latest rawhide using one of the following techniques. | ||
* '''[http://alt.fedoraproject.org/pub/alt/stage/15-Beta. | * '''[http://alt.fedoraproject.org/pub/alt/stage/15-Beta.RC2/ Download and install the beta candidate image]''' | ||
* [[Releases/Branched|Install from a nearby Fedora 15 mirror]] | * [[Releases/Branched|Install from a nearby Fedora 15 mirror]] | ||
Revision as of 15:57, 13 April 2011
DATE | TIME | WHERE |
Thursday April 14, 2011 | From 12:00 to 21:00 UTC (8am -> 5pm EDT) | #fedora-test-day (webirc) |
What to test?
Today's installment of Fedora Test Day will focus on Virtualization improvements in Fedora 15. There is a large list of virtualization improvements coming in Fedora. To simplify things, testing will be divided up into a number of sections.
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 and provide feedback.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Justin Forbes
- Development / general help - Richard W.M. Jones (rwmjones on FreeNode)
What's needed to test
- A fully updated Fedora 15 Alpha machine. See instructions below.
- Hardware virtualization support (e.g. Intel VT or AMD-V) (see How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F Is My Guest Using KVM?). If unavailable, you can still help with testing QEMU support.
- At least one guest image installed before the test day (suggested reading - Virtualization_Quick_Start)
- Up to 10-20Gb free disk space. Guest images take up a lot of space.
- See the individual test area pages for specific requirements.
How to test?
Update your machine
See the instructions on the Branched page on the various ways in which you can install or update to the Branched release. You should have at least the following packages installed.
kernel-devel-2.6.38.2-9.fc15
libvirt-0.8.8-3.fc15
python-virtinst-0.500.6-1.fc15
qemu-0.14.0-7.fc15
seabios-0.6.0-1.fc15
virt-manager-0.8.7-2.fc15
libguestfs-1.9.14-1.fc15
}}
Install Fedora 15
Testing requires the latest virtualization software included in Fedora Rawhide. Update your system to the latest rawhide using one of the following techniques.
Note: if you are using the Live CD image, you will need to mount storage for guests either from the local disk or from NFS. If the latter, you will need to run setsebool virt_use_nfs=on
in order for it to work with SELinux.
Test Cases
When ready, select a category below and follow the instructions provided in each of the test cases:
General Virt
Spice
libvirt
None sumbitted
libguestfs, guestfish
Read more about this here: Features/libguestfs
As Xen Guest (DomU)
Report your Results
If you have problems with any of the tests, report a bug to bugzilla. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from FIXME as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, if your system worked correctly, simply enter the word PASS
. If you had trouble, enter the word FAIL
, with a link to the bug report for the failure. 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 private LDAP test as you do not have access to an LDAP server), enter the word N/A. In the comments column, you can enter any short, additional information about your testing environment.
Test Results
Each column should be a test case or configuration, and each row should consist of test results. Include a link where to report bugs. For example:
Please report all bugs into Bugzilla against the component listed in the individual test area.
Things that Work Well
User | Smolt Profile | Description | Status | References |
---|---|---|---|---|
Issues that Were Identified
User | Smolt Profile | Description | References |
---|---|---|---|