From Fedora Project Wiki

Line 63: Line 63:
* [[Test_Day:2010-09-23_Virtualization_VHostNet|VHostNet]]
* [[Test_Day:2010-09-23_Virtualization_VHostNet|VHostNet]]
* [[Test_Day:2010-09-23_Virtualization_VirtioSerial|VirtioSerial]]
==== libvirt ====
==== libvirt ====

Revision as of 13:23, 23 September 2010

Thursday September 23, 2010 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 14. 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 14

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



None sumbitted

libguestfs, guestfish

Read more about this here: Features/libguestfs

As Xen Guest (DomU)

Network interface management

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
Sample User Sample Smolt Profile Sample Description Sample Status
David Ramsey put my smolt profile here with URL put testing description here put testing status here
Inprogress inprogress
Will report component entries with additional details.
• General Virt - post results
• KVM - later post results
• libvirt - later post results
• libguestfs, guestfish - post result
• Xen Guest - post result
• Interface management with virt-manager - later post result

Issues that Were Identified

User Smolt Profile Description Status References
Sample User Sample Smolt Profile Sample Description Sample Status
quintela domxml-to-native always set rtl8139 Don't work bz636832