| Fedora Test Days | |
|---|---|
| |
| Virtualization Test Day | |
| Date | 2012-11-01 |
| Time | all day |
| Website | Virtualization |
| IRC | #fedora-test-day (webirc) |
| Mailing list | virt |
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 ...
- Developer - Daniel Berrange (irc: danpb)
- Developer - Richard W.M. Jones (irc: rwmjones)
- Developer - Cole Robinson (irc: crobinso)
- Developer - Stefan Hajnoczi (irc: stefanha)
- Developer - Miroslav Rezanina (irc: mrezanin)
- Developer - Eric Blake (irc: eblake)
- Developer - Laine Stump (irc: laine)
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.
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:
- Install with CD/DVD.
- Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/
- Latest 64 Bit DVD: http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC6/Fedora/x86_64/iso/
- Upgrade from Fedora 17
- The supported way is using CD/DVD upgrade. See media links above
- Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!
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. You'll want to install the latest virt packages from virt-preview (linked above). Install a Fedora 18 guest (there are test cases below that walk you through it). Then use virt-manager to 'copy host CPU' for your VM. Boot the VM, yum groupinstall @virtualization, and verify that nested virt is working (sudo virt-host-validate).
Areas to test
Do these first!
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
News tests and features
- QA:Testcase Virtualization Live Backup
- QA:Testcase Virtualization Guest Suspend Hibernate
- QA:Testcase Virtualization Seccomp Sandboxing
- QA:Testcase Virtualization IO Throttling
- QA:Testcase Virtualization PV EOI
- QA:Testcase Virtualization USB3 Device Passthrough
- QA:Testcase Virtualization USB Redirection
Previous test cases
Some test cases used in previous test days. Still useful to test for regressions!
Migration
- QA:Testcase Live Migration using libvirt/virsh
- QA:Testcase Offline (paused) Migration using libvirt/virsh
Spice
- QA:Testcase Virtualization Check SPICE password support
- QA:Testcase Virtualization Manually set spice listening port with TLS port set
- QA:Testcase Virtualization Setting up a VM with Spice
- QA:Testcase Virtualization Spice listen on all public network interfaces
libvirt
- QA:Testcase Virtualization libvirt create a logical pool
- QA:Testcase Virtualization libvirt save and restore with svirt
- QA:Testcase Virtualization libvirt set guest memory
Hotplug
- QA:Testcase Virtualization Attach/Detach a SCSI device to guest
- QA:Testcase Virtualization Hotplug USB device to guest
- QA:Testcase Virtualization NIC Hotplug virsh attach detach
virtio-scsi
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.
GuestOS compatibility
- GuestOS compatibility
— test installation of as many different guest operating system as as possible. (You will need a KVM bare metal host & lots of disk space)