From Fedora Project Wiki

(Change a bug number)
Line 31: Line 31:
* firewalld service running on an F17 host can break guest network access if using libvirt virtual networks. work around is to disable or remove firewalld: https://bugzilla.redhat.com/show_bug.cgi?id=796479
* firewalld service running on an F17 host can break guest network access if using libvirt virtual networks. work around is to disable or remove firewalld: https://bugzilla.redhat.com/show_bug.cgi?id=796479
* restarting libvirtd (which is also done on a package update) will forcibly stop all kvm guests and virtual networks: https://bugzilla.redhat.com/show_bug.cgi?id=805942
* restarting libvirtd (which is also done on a package update) will forcibly stop all kvm guests and virtual networks: https://bugzilla.redhat.com/show_bug.cgi?id=805942
* 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: https://bugzilla.redhat.com/show_bug.cgi?id=802475
* 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: https://bugzilla.redhat.com/show_bug.cgi?id=811967


== What's needed to test ==
== What's needed to test ==

Revision as of 12:20, 12 April 2012

Virtualization Test Day

Fedora Test Days
Virtualization Test Day

Date 2012-04-12
Time all day

Website QA/Fedora_17_test_days
IRC #fedora-test-day (webirc)
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 improvements in Fedora 17. There is a large list of virtualization improvements coming in Fedora. To simplify things, testing will be divided up into a number of sections.

Who's available

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

Known issues

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

What's needed to test

Areas to test

News tests and features

Below are the some of the virt features accepted for F17 which should each have test notes documented:

Below are some other F17 virt features which are lacking clear test instructions:

Below are proposed F17 virt features with unclear status:

Other important / general test plans to follow include:

  • libguestfs
    — libguestfs, image inspection, virt tools, V2V, P2V (you will need at least one guest to test this)
  • 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)

Previous test cases

Some test cases used in previous test days. Still useful to test for regressions!

General Virt

Spice

libvirt

Hotplug