Test Day:2013-05-28 Virtualization

From FedoraProject

Revision as of 16:07, 27 May 2013 by Kashyapc (Talk | contribs)

Jump to: navigation, search
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
MailSubscribeArchives


Warning (medium size).png
Under construction
The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).
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.

Contents

Fedora 19 Live Image tailored for the test day

Here's a Fedora Live image already containing all the packages related to virtualization. You can download the below image, burn it on a USB, install the ISO on a physical machine, and proceed with "Areas to test" section.

 wget -c http://fedorapeople.org/groups/qa/testday-20130528-x86_64.iso 

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

Known issues

Before you begin testing, there are a few known bugs that should be taken into account:

  • running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: bug 811967
  • saving (migrate to file) a guest using spice is crashy bug 962954
  • /dev/vfio/vfio has wrong default permissions. bug 967230
  • Storage migration can fail at the end of the process bug 967242

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

If you already have an F19 machine - as an alternative to above, you could install a minimal set of packages to provide KVM-based virutalation, do:

$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y
$ yum install python-virtinst -y
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y
$ yum install virt-viewer -y

Install a minimal, unattended F18 guest

Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:

$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash


$ ./create-guest-qcow2.bash f18-testday f18 x86_64

Once the install is finished (takes 5 minutes or so), you can can login via virsh serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]


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:

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:

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

At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.

Areas to test

All these tests have an entry in the Test Results table, please record them there.

VM Install

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!

Standard features

These are recurring tests of standard virt features, they ensure nothing obvious is broken.

New features

New or improved features in Fedora 19:


Extra tests

These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.

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

Previous test cases

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

Fedora 18 features:

Misc tests:

All tests:

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
Kashyap Chamarthy
Pass pass
none