From Fedora Project Wiki

(Fix testday app-generated results to use {{result}} template for bug references)
(Move long comments to a separate section at end of page)
Line 255: Line 255:
| {{result|none}}  
| {{result|none}}  
| {{result|none}}
| {{result|none}}
| {{result|pass}} <ref>Throttling works but virsh blkdeviotune reports incorrect results.  I have sent patches here: https://www.redhat.com/archives/libvir-list/2012-November/msg00095.html {{bz|872582}}</ref>
| {{result|pass}} <ref group="long">Throttling works but virsh blkdeviotune reports incorrect results.  I have sent patches here: https://www.redhat.com/archives/libvir-list/2012-November/msg00095.html {{bz|872582}}</ref>
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 315: Line 315:


|}
|}
== Long comments ==
<references group="long" />


[[Category:Test Days]]  [[Category:Fedora 18 Test Days]]
[[Category:Test Days]]  [[Category:Fedora 18 Test Days]]
[[Category:Virtualization]]
[[Category:Virtualization]]

Revision as of 06:22, 26 December 2014

Fedora Test Days
Virtualization Test Day

Date 2012-11-01
Time all day

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


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 18. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 18.

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:

  • Pausing a KVM guest can crash that guest. Might be specific to guests using a QXL video device (the default created by virt-manager): bug 870811
  • 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
  • qemu + libvirt + seccomp doesn't work, the qemu guests fail to even start: bug 855162
  • some graphical corruption if using cirrus virtual card for guests: bug 871247
  • virt-manager will backtrace trying to show guests in the 'suspended' state bug 871237
  • Closing a graphical window triggers a guest resume bug 871240
  • ctrl-alt-f2,3,4 don't have effect in guests (unless xserver is restarted): bug 871241

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 18 on a physical machine

The preferred testing platform is a fully updated Fedora 18 machine. You have a few options for getting the Fedora 18 bits:

  • Upgrade from Fedora 17

Fedora 18 virt packages on Fedora 17

If you aren't ready to make the jump to Fedora 18, this is the next best thing! Run latest virt packages on Fedora 17 from the virt-preview repo:

http://fedoraproject.org/wiki/Virtualization_Preview_Repository

Run Fedora 18 in a VM with nested virtualization

Do you have a new machine with a ton of ram and storage space, running Fedora 17? Nested virt might be an option! This allows you to create KVM guests _inside_ a Fedora 18 VM.

  1. Install the latest virt packages from virt-preview using the instructions above.
  2. Install a Fedora 18 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.

libguestfs and tools

You will need Fedora 18 (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 18, 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!

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 Live Backup Suspend Seccomp IO Throttling PV EOI USB3 USB Redir References
crobinso
Pass pass
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
Pass pass
Warning warn
[2]
done
  1. Guest fails to start RHBZ #855162
  2. USB Device didn't appear in lsusb -t in guest
Kashyap Chamarthy
Pass pass
Pass pass
Pass pass
none
none
none
none
none
none
mkrizek
Pass pass
Pass pass
Pass pass
Pass pass
none
Pass pass
Pass pass
[1]
none
Pass pass
  1. Reduced only from approx. 15.000 to 12.000
mrezanin
Pass pass
Pass pass
Pass pass
Pass pass
none
Pass pass
none
none
Pass pass
pschindl
Warning warn [1]
Fail fail [2]
Pass pass
[3]
  1. RHBZ #872162
  2. RHBZ #869607
  3. I tested only guest functionality, when I try agent I got 'Error starting domain: Unable to read from monitor: Connection reset by peer'
Stefan Hajnoczi
Pass pass
none
none
none
none
Pass pass
[long 1]
none
none
none
Eric Blake
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
[1]
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. RHBZ #872292 found by inspection based on an IRC question, latent bug which affects snapshots, among other operations
Arun S A G
Pass pass
Pass pass
none
Pass pass
[1]
none
none
none
none
none
  1. RHBZ #872343 Cannot resume RHEL6 vm running at runlevel 3
kparal
Pass pass
Pass pass
Pass pass
Fail fail [1]
none
Fail fail [2]
none
none
none
  1. RHBZ #872573
  2. RHBZ #872582
Karen Noel
Pass pass
[1]
Inprogress inprogress
none
none
none
none
none
none
none
  1. Installed RHEL6.3 and F18 guests

Long comments

  1. Throttling works but virsh blkdeviotune reports incorrect results. I have sent patches here: https://www.redhat.com/archives/libvir-list/2012-November/msg00095.html RHBZ #872582