Latest revision as of 19:39, 26 June 2015

Virtualization Test Day[edit]

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?[edit]

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[edit]

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

Development / general help - Daniel Berrange (danpb on FreeNode)
Development / general help - Richard W.M. Jones (rwmjones on FreeNode)
Development / general help - Cole Robinson (crobinso on FreeNode)

Known issues[edit]

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

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
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[edit]

A fully updated Fedora 17 Beta machine. See instructions below.
Hardware virtualization support (e.g. Intel VT or AMD-V) (see How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F Is My Guest Using KVM?). If unavailable, you can still help with testing QEMU support.
At least one guest image installed before the test day (suggested reading - Virtualization_Quick_Start)
Up to 10-20Gb free disk space. Guest images take up a lot of space.

Areas to test[edit]

News tests and features[edit]

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

https://fedoraproject.org/wiki/Features/virtio-scsi
- QA:Testcase_Virtualization_Virtio_SCSI_Install
- QA:Testcase_Virtualization_Virtio_SCSI_Hotplug

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

https://fedoraproject.org/wiki/Features/KVM_Guest_PMU (FIXME: no test instructions)
https://fedoraproject.org/wiki/Features/Open_vSwitch (FIXME: no test instructions)
https://fedoraproject.org/wiki/Features/VirtSandbox (Ignore, pending updated RPMs in Fedora)

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[edit]

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

General Virt[edit]

Spice[edit]

libvirt[edit]

Hotplug[edit]

@@ Line 24: / Line 24: @@
 * Development / general help - [[User:rjones|Richard W.M. Jones]] (rwmjones on FreeNode)
 * Development / general help - [[User:crobinso|Cole Robinson]] (crobinso on FreeNode)
+== Known issues ==
+Before you begin testing, there are a few known bugs that should be taken into account
+* 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
+* 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 ==
@@ Line 38: / Line 46: @@
 * https://fedoraproject.org/wiki/Features/virtio-scsi
-* https://fedoraproject.org/wiki/Features/VirtSandbox
+** [[QA:Testcase_Virtualization_Virtio_SCSI_Install]]
+** [[QA:Testcase_Virtualization_Virtio_SCSI_Hotplug]]
 Below are some other F17 virt features which are lacking clear test instructions:
-* https://fedoraproject.org/wiki/Features/KVM_Live_Block_Migration (FIXME: no test instructions)
 * https://fedoraproject.org/wiki/Features/KVM_Guest_PMU (FIXME: no test instructions)
 * https://fedoraproject.org/wiki/Features/Open_vSwitch (FIXME: no test instructions)
+* https://fedoraproject.org/wiki/Features/VirtSandbox (Ignore, pending updated RPMs in Fedora)
-Below are proposed F17 virt features with unclear status:
-* https://fedoraproject.org/wiki/Features/KVMThinProv (FIXME: isn't going to make F17?)
 Other important / general test plans to follow include:
@@ Line 61: / Line 66: @@
 ==== General Virt ====
+* [[QA:Testcase_Virtualization_URL_Guest_Install]]
+* [[QA:Testcase_Virtualization_CDROM_Guest_Install]]
+* [[QA:Testcase_Virtualization_Virt_Manager_Lifecycle]]
 * [[QA:Testcase_Virtualization_Guest_pxeBoot]]
 * [[QA:Testcase Live Migration using libvirt/virsh]]

Search

Test Day:2012-04-12 Virtualization Test Day: Difference between revisions