From Fedora Project Wiki

(Added missing category)
m (date fix)
Line 3: Line 3:
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
| caption = Virtualization Test Day
| caption = Virtualization Test Day
| date = 2013-05-30
| date = 2013-05-28
| time = all day
| time = all day
| website = [[Virtualization]]
| website = [[Virtualization]]

Revision as of 14:49, 17 May 2013

Fedora Test Days
Echo-testing-48px.png
Virtualization Test Day

Date 2013-05-28
Time all day

Website Virtualization
IRC #fedora-test-day (webirc)
Mailing list virt


Note.png
Can't make the date?
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 installment of Fedora Test Day will focus on Virtualization in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...


What's needed to test

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 18 bits:

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.

  1. Install the latest virt packages from virt-preview using the instructions above.
  2. Install a Fedora 19 guest using one of the test cases below.
  3. 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:

Areas to test

VM Install

Record your results for these test cases in the Test Results section.

If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!

Next give this a run through, which should ensure things aren't broken in some obvious manner:

New tests and features

Record your results for these test cases in the Test Results section.

FIXME

libguestfs and tools

You will need Fedora 19 (host) and at least one guest (but the more the merrier).

Install libguestfs:

# yum install '*guestf*'

and run through the tests here: http://libguestfs.org/guestfs-testing.1.html

In Fedora 19, we are using libvirt to launch the appliance, and sVirt + SELinux to make everything much more secure. Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.

Previous test cases

Some test cases used in previous test days. Still useful to test for regressions!

Fedora 17 features:

Migration:

Hotplug:

virtio-scsi:


Test Results

Each tester should add a row for their results.

If you have problems with any of the tests, report a bug to Bugzilla. If you have any questions about what component to file against, just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!

User VM Install VM Lifecycle References
Cole Robinson
Inprogress inprogress
none