|Fedora Test Days|
|Virtualization Test Day|
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.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
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
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:
- Install with CD/DVD.
- Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/
- Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-TC4/Fedora/x86_64/iso/
- Upgrade from Fedora 18
- The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F
- Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!
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.
- Install the latest virt packages from virt-preview using the instructions above.
- Install a Fedora 19 guest using one of the test cases below.
- 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:
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:
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.
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:
These are recurring tests of standard virt features.
- USB hotplug
- Live migration (steps included for doing this with a single physical host)
- Host PCI device assignment
New or improved features in Fedora 19:
- Virtio RNG (Random Number Generator)
- Live migration without shared storage (steps included for doing this with a single physical host)
- Host PCI device assignment using VFIO
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).
# 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:
- Live VM disk backup
- VM suspend/hibernate
- VM sandboxing w/ syscall filters
- VM IO throttling
- VM PV EOI performance optimization
- USB3 device assignment
- USB Redirection
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|