Test Day:2015-04-16 Virtualization

Fedora Test Days
Virtualization Test Day
Date	Thursday 2015-04-16
Time	all day
Website	Virtualization
IRC	#fedora-test-day
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 [on Fedocal] 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 22. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 22.

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.

• Cole Robinson (crobinso)
• Jeff E. Nelson (jenelson)

Known issues

• ejecting CDROM media from a VM hits 'tray locked' error, but succeeds on the second attempt: http://bugzilla.redhat.com/show_bug.cgi?id=1211761

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

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

Install with CD/DVD

You can download the latest Fedora 22 Beta composes here:

• Workstation live .ISO: https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC1/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-22_Beta-1.iso
• Server DVD: https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC1/Server/x86_64/iso/Fedora-Server-DVD-x86_64-22_Beta.iso
• Alpha cloud image: https://dl.fedoraproject.org/pub/fedora/linux/releases/test/22_Alpha/Cloud/x86_64/Images/Fedora-Cloud-Base-22_Alpha-20150305.x86_64.qcow2

Upgrade from Fedora 21

• 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 22 in a VM with nested virtualization

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

Use the virt-preview instructions below, install a guest using one of the install test cases, and follow the nested virt test case to finish the setup and verify things are working correctly.

Fedora 22 virt packages on Fedora 21

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

http://fedoraproject.org/wiki/Virtualization_Preview_Repository

Areas to test

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

Ensure you are using the latest virt packages!

Several updated packages were pushed to Fedora 22 only recently. The recommended versions are:

• qemu-system-x86-2.3.0-0.3.rc2.fc22.x86_64 (same version for all qemu* packages)
• libvirt-daemon-1.2.13-2.fc22.x86_64
• virt-manager-1.1.0-7.git6dbe19bd8.fc22

If a 'yum update' isn't pulling these packages in, try 'sudo yum clean all', then 'sudo yum update'.

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!

• 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)

Standard features

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

New features

No test cases yet

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 22 (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 21 features:

• Q35 Chipset
• Import AArch64 image as a VM on x86
• Install VM using OVMF/UEFI

Fedora 20 features:

• Virt ACLs
• VM CPU hotplug
• Enable multiqueue virtio networking

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

Misc tests:

• 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

All tests:

• Complete list of previous tests

Debugging

• https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems

Test Results

This section will have more info when we are closer to the test day. 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.