Test Day:2011-04-14 Virtualization

From FedoraProject

Revision as of 14:18, 14 April 2011 by Jlaska (Talk | contribs)

Jump to: navigation, search
DATE TIME WHERE
Thursday April 14, 2011 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-test-day (webirc)

Contents

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 ...

What's needed to test

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.

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.

Testing

When ready, select a category below and follow the instructions provided in each of the test cases:

General Virt

Spice

libvirt

Hotplug


Report your Results

If you have problems with any of the tests, report a bug to Bugzilla. For instance file a bug report against the component virt-manager if you have problems testing the virt-manager. 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. Also, consult How_to_debug_Virtualization_problems for guidance resolving any issues.

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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

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
Marc-Andre My System [1] @virtualization should pull spice-gtk-python </references>

Cite error: <ref> tags exist, but no <references/> tag was found