Test Day:2012-11-01 Virtualization

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (More underscore removal)
(Add known issues section)
Line 22: Line 22:
 
* Development / general help - [[User:rjones|Richard W.M. Jones]] (rwmjones on FreeNode)
 
* Development / general help - [[User:rjones|Richard W.M. Jones]] (rwmjones on FreeNode)
 
* Development / general help - [[User:crobinso|Cole Robinson]] (crobinso on FreeNode)
 
* Development / general help - [[User:crobinso|Cole Robinson]] (crobinso on FreeNode)
<!--
+
 
 
== Known issues ==
 
== Known issues ==
  
 
Before you begin testing, there are a few known bugs that should be taken into account
 
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
+
* Pausing a KVM guest can crash that guest. Might be specific to guests using a QXL video device (the default created by virt-manager): https://bugzilla.redhat.com/show_bug.cgi?id=870811
* 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
 
* 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 22:12, 28 October 2012

Fedora Test Days
Echo-testing-48px.png
Virtualization Test Day

Date 2012-11-01
Time all day

Website Virtualization
IRC #fedora-test-day (webirc)

Mailing list
MailSubscribeArchives


Note.png
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.

Contents

What to test?

Today's installment of Fedora Test Day will focus on Virtualization in Fedora 18. Test cases will cover basic virtualization functionality, as well as tests for new features in Fedora 18.

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

FIXME: test cases coming soon

Previous test cases

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

General Virt

Spice

libvirt

Hotplug

virtio-scsi

libguestfs and tools

You will need Fedora 18 (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

In Fedora 18, we are using libvirt to launch the appliance, and sVirt + SELinux to make everything much more secure. Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.

GuestOS compatibility

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