|Fedora Test Days|
|Virtualization Test Day|
|Mail • Subscribe • Archives|
- 1 What to test?
- 2 Who's available
- 3 Known issues
- 4 What's needed to test
- 5 Areas to test
- 6 Extra tests
- 7 Debugging
- 8 Test Results
What to test?
Today's installment of Fedora Test Day will focus on Virtualization in Fedora 21. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 21.
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.
- Cole Robinson (crobinso)
- Fedora 21 Workstation media is not detected as Fedora 21 by boxes/virt-manager: bug 1145264
- USB hotplug doesn't work (fixed in libvirt-1.2.8-5): bug 1145968
- SPICE auto guest resize isn't working: bug 1146175
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?).
- 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 21 on a physical machine
The preferred testing platform is a fully updated Fedora 21 machine. You have a few options for getting the Fedora 21 bits:
Install with CD/DVD
You can download the Fedora 21 Alpha in various formats here.
Upgrade from Fedora 20
- The supported way is using 'fedup': FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F You may also find the instructions in the fedup test case useful for using fedup to upgrade to a pre-release.
- Upgrade 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 21 in a VM with nested virtualization
Do you have a new machine with a ton of ram and storage space, running Fedora 21? Nested virt might be an option! This allows you to create KVM guests inside a Fedora 21 VM.
Fedora 21 virt packages on Fedora 20
If you aren't ready to make the jump to Fedora 21, this is the next best thing! Run latest virt packages on Fedora 20 from the virt-preview repo:
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!
- Guest install via CDROM/ISO
- Guest install via URL
- Import existing VM image (your own disk image, or Fedora cloud image, or virt-builder image)
These are recurring tests of standard virt features, they ensure nothing obvious is broken.
- VM Lifecycle (start, stop, save, clone, delete, ...)
- VM snapshot management
- Spice features: copy/paste, drag/drop, USB redirection, auto guest resize
- Change CDROM media for running VM
- Host USB device hotplug
- Host PCI device assignment
- Enabling nested virtualization for a VM
- Live migration (steps included for doing this with a single physical host)
- Run Fedora ARM image as a VM on x86
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 21 (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 20 features:
Fedora 19 features:
- 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
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 passthrough
- Guest install via PXE (only if you have a pre-existing PXE setup)
- NIC hotplug with virsh
- Virtio SCSI install
- Virtio SCSI hotplug
- VM serial console login
We are tracking test results in a web application over here
Results from this web application will be automatically transferred to the Wiki a week after the test day, and the reporting system will be shutdown. Feel free to continue testing and filling the wiki even after this date.