Test Day:2012-11-01 Virtualization

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(reference seccomp bug)
(Add more bugsssss)
Line 35: Line 35:
 
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:
  
* 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
+
* 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 bug 870811]
* 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 bug 811967]
* qemu + libvirt + seccomp doesn't work, the qemu guests fail to even start: https://bugzilla.redhat.com/show_bug.cgi?id=855162
+
* qemu + libvirt + seccomp doesn't work, the qemu guests fail to even start: [https://bugzilla.redhat.com/show_bug.cgi?id=855162 bug 855162]
 +
* some graphical corruption if using cirrus virtual card for guests: [https://bugzilla.redhat.com/show_bug.cgi?id=871247 bug 871247]
 +
* virt-manager will backtrace trying to show guests in the 'suspended' state [https://bugzilla.redhat.com/show_bug.cgi?id=871237 bug 871237]
 +
* Closing a graphical window triggers a guest resume [https://bugzilla.redhat.com/show_bug.cgi?id=871240 bug 871240]
 +
* ctrl-alt-f2,3,4 don't have effect in guests (unless xserver is restarted): [https://bugzilla.redhat.com/show_bug.cgi?id=871241 bug 871241]
  
 
== What's needed to test ==
 
== What's needed to test ==

Revision as of 03:10, 30 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 basic virtualization workflow, some cool functionality, as well as new features introduced 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:

  • Pausing a KVM guest can crash that guest. Might be specific to guests using a QXL video device (the default created by virt-manager): bug 870811
  • 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: bug 811967
  • qemu + libvirt + seccomp doesn't work, the qemu guests fail to even start: bug 855162
  • some graphical corruption if using cirrus virtual card for guests: bug 871247
  • virt-manager will backtrace trying to show guests in the 'suspended' state bug 871237
  • Closing a graphical window triggers a guest resume bug 871240
  • ctrl-alt-f2,3,4 don't have effect in guests (unless xserver is restarted): bug 871241

What's needed to test

  • A fully updated Fedora 18 Beta machine.
  • Hardware virtualization support (e.g. Intel VT or AMD-V) (see 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

Do these first!

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!

Next give this a run through, which should ensure things aren't broken in some obvious manner

News tests and features

Previous test cases

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

Migration

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)