| Fedora Test Days | |
|---|---|
| |
| SPICE Test Day | |
| Date | 2013-05-30 |
| Time | all day |
| Website | Features/Spice |
| IRC | #spice, #fedora-test-day (webirc) |
| Mailing list | spice-devel@lists.freedesktop.org |
The Test Day page is yet in construction. It will be ready for the Test Day - when this message is removed :) .
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's instalment of Fedora Test Day will focus on Spice, the protocol to access remote VMs and physical linux systems.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Jeremy White (jwhite)
- Quality Assurance - David Jaša (djasa),
What do I need for testing?
An updated Fedora 19 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
prerequisites for SSL/TLS
prerequisites for connection to Xspice
You only need any Fedora system (physical or virtual) with xorg-x11-server-Xspice and virt-viewer packages installed.
prerequisites for connection to VMs
prerequisites for migration testing
How to get generic system?
This system is good just for testing client and/or Xspice. Generic Fedora Test Day guidelines apply:
Update your machine
If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
How to get virtualization-capable system?
For starters, your physical machine should have:
- Hardware virtualization support (e.g. Intel VT or AMD-V) (see Is My Guest Using KVM?). If unavailable, you can still help with testing QEMU support.
- Up to 10-20Gb free disk space. Guest images take up a lot of space.
- Get the packages with
yum groupinstall virtualization
As for getting the latest virt packages, you have a few options:
Fedora 19 on a physical machine
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:
- Install with CD/DVD.
- Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/
- Latest 64 Bit DVD: <<FIXME>>
- Upgrade from Fedora 18
- The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F
- Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!
Fedora 19 virt packages on Fedora 18
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:
http://fedoraproject.org/wiki/Virtualization_Preview_Repository
Run Fedora 19 in a VM with nested virtualization
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option! This allows you to create KVM guests _inside_ a Fedora 19 VM.
- Install the latest virt packages from virt-preview using the instructions above.
- Install a Fedora 19 guest using one of the test cases below.
- Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root:
virt-host-validate
Some notes on nested virt with AMD and Intel:
- http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/
- http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/
- http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/
<<FIXME>>: still a template from now on
How to test?
High level details on how a contributor can get involved. This can include (but not limited to):
- Areas to target with exploratory testing
- A list of pre-defined test cases to execute
- How to report back results
Test Cases
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.
Test Results
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, 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 the first line 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, use the result template to enter your result, as shown in the example result line.
| User | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|
| Sample User |  |
 |
 |