Test Day:2013-10-08 Virtualization

Fedora Test Days
Virtualization Test Day
Date	2013-10-08
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 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 20. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 20.

Who's available

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

• Cole Robinson (crobinso)
• Eric Blake (eblake on IRC)
• Kashyap Chamarthy (kashyap on IRC)
• Alexander Todorov (atodorov on IRC)

Known issues

Before you begin testing, there are a few known bugs that should be taken into account:

• libvirt managed save occasionally fails with 'unexpected migration status in setup': https://bugzilla.redhat.com/show_bug.cgi?id=1015636
• virt-manager doesn't correctly report 'current' VM CPUs: https://bugzilla.redhat.com/show_bug.cgi?id=1016318
• Selinux denial on the host when enabling multiqueue nic in the guest: https://bugzilla.redhat.com/show_bug.cgi?id=1016326

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:

Virt Test Day Live CD

There's a Fedora 20 live CD image that already has all the required virtualization packages installed (though you should still yum update after booting). You will probably want a good amount of RAM if using this option (greater than 4G) since you'll be using RAM for both a VM and running the live OS.

• Get the image: wget -c http://fedorapeople.org/groups/virt/virt-testday-2013-10-08.iso
• For Live CD or USB setup instructions, see: FedoraLiveCD#Download_and_Create_Live_image_or_Live_USB
• If you have a really beefy machine, you can probably run the Live CD in a VM using nested virtualization! (see instructions below)
• After booting the livecd, make sure to do a yum update to get all the latest packages

Fedora 20 on a physical machine

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

Install with CD/DVD

You can download the Fedora 20 Alpha in various formats here.

Upgrade from Fedora 19

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

Do you have a new machine with a ton of ram and storage space, running Fedora 19? Nested virt might be an option! This allows you to create KVM guests inside a Fedora 20 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 20 virt packages on Fedora 19

If you aren't ready to make the jump to Fedora 20, this is the next best thing! Run latest virt packages on Fedora 19 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.

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
• Guest install via URL

Standard features

These are recurring tests of standard virt features, they ensure nothing obvious is broken.

• VM Lifecycle (start, stop, save, clone, delete, ...)
• VM serial console login
• Host USB device hotplug
• Enabling nested virtualization for a VM
• Live migration (steps included for doing this with a single physical host)
• Host PCI device assignment
• Change CDROM media for running VM

New features

New or improved features in Fedora 20:

• Virt ACLs
• Import ARM guest on your x86 machine and manage with virt-manager/libvirt
• Snapshot UI in virt-manager
• VM CPU hotplug
• Enable multiqueue virtio networking

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 20 (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 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
• USB Redirection

Misc tests:

• NIC hotplug with virsh
• Virtio SCSI install
• Virtio SCSI hotplug

All tests:

• Complete list of previous tests

Debugging

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

Test Results

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.

Should you encounter any problem while using the web application, please contact jskladan on #fedora-qa channel at freenode, or send an email to jskladan@fedoraproject.org