From Fedora Project Wiki

m (Add virt category)
(Drop direct Test Days category membership)
 
(49 intermediate revisions by 16 users not shown)
Line 1: Line 1:
{{Infobox_group
{{Infobox_group
| name = Fedora Test Days
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_16_test_days]]
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_18_test_days]]
| caption = Virtualization Test Day
| caption = Virtualization Test Day
| date = 2012-11-01
| date = 2012-11-01
| time = all day
| time = all day
| website = [[Virtualization]]
| website = [[Virtualization]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc] [http://meetbot.fedoraproject.org/fedora-test-day/2012-11-01/fedora-test-day.2012-11-01-12.25.log.txt IRC logs])
| fedora_mailing_list = virt
| fedora_mailing_list = virt}}
}}


{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}


== What to test? ==
== 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.
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 ==
== Who's available ==


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development / general help - [[User:berrange|Daniel Berrange]] (danpb on FreeNode)
<!--
* Development / general help - [[User:rjones|Richard W.M. Jones]] (rwmjones on FreeNode)
Use this format:
* Development / general help - [[User:crobinso|Cole Robinson]] (crobinso on FreeNode)
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)
-->
* [[User:berrange|Daniel Berrange]] (danpb)
* [[User:rjones|Richard W.M. Jones]] (rwmjones)
* [[User:crobinso|Cole Robinson]] (crobinso)
* [[User:stefanha|Stefan Hajnoczi]] (stefanha)
* [[User:mrezanin|Miroslav Rezanina]] (mrezanin)
* [[User:ericb|Eric Blake]] (eblake)
* [[User:laine|Laine Stump]] (laine)


== 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:


* 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 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 ==
* A fully updated Fedora 18 Beta machine.
 
* 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.
For starters, your physical machine should have:
* At least one guest image installed before the test day (suggested reading - [[Virtualization_Quick_Start]])
* 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.
* Up to 10-20Gb free disk space. Guest images take up a lot of space.
* Up to 10-20Gb free disk space. Guest images take up a lot of space.
* Get the packages with <br><pre>yum groupinstall virtualization</pre>
As for getting the latest virt packages, you have a few options:
=== Fedora 18 on a physical machine ===


== Areas to test ==
The preferred testing platform is a fully updated Fedora 18 machine. You have a few options for getting the Fedora 18 bits:
 
* Install with CD/DVD.
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/
** Latest 64 Bit DVD: http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC6/Fedora/x86_64/iso/
 
* Upgrade from Fedora 17
** The supported way is using CD/DVD upgrade. See media links above
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum  <br>This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!
 
=== Fedora 18 virt packages on Fedora 17 ===
 
If you aren't ready to make the jump to Fedora 18, this is the next best thing! Run latest virt packages on Fedora 17 from the virt-preview repo:
 
http://fedoraproject.org/wiki/Virtualization_Preview_Repository
 
=== Run Fedora 18 in a VM with nested virtualization ===


=== News tests and features ===
Do you have a new machine with a ton of ram and storage space, running Fedora 17? Nested virt might be an option!
This allows you to create KVM guests _inside_ a Fedora 18 VM.


FIXME: test cases coming soon
# Install the latest virt packages from virt-preview using the instructions above.
# Install a Fedora 18 guest using one of the test cases below.
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre>


=== Previous test cases ===
Some notes on nested virt with AMD and Intel:


Some test cases used in previous test days. Still useful to test for regressions!
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/


==== General Virt ====
== Areas to test ==


* [[QA:Testcase Virtualization URL Guest Install]]
=== '''VM 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]]
* [[QA:Testcase Offline (paused) Migration using libvirt/virsh]]
* [[QA:Testcase Virtualization PV EOI]]


==== Spice ====
Record your results for these test cases in the '''[[#Test Results |Test Results]]''' section.


* [[QA:Testcase Virtualization Check SPICE password support]]
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!
* [[QA:Testcase Virtualization Manually set spice listening port with TLS port set]]
* [[QA:Testcase Virtualization Setting up a VM with Spice]]
* [[QA:Testcase Virtualization Spice listen on all public network interfaces]]


==== libvirt ====
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]


* [[QA:Testcase Virtualization libvirt create a logical pool]]
Next give this a run through, which should ensure things aren't broken in some obvious manner:
* [[QA:Testcase Virtualization libvirt save and restore with svirt]]
* [[QA:Testcase Virtualization libvirt set guest memory]]


==== Hotplug ====
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, delete, ...)]]


* [[QA:Testcase Virtualization Attach/Detach a SCSI device to guest]]
=== '''New tests and features''' ===
* [[QA:Testcase Virtualization Hotplug USB device to guest]]
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach]]


==== virtio-scsi ====
Record your results for these test cases in the '''[[#Test Results|Test Results]]''' section.


* [[QA:Testcase Virtualization Virtio SCSI Install]]
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]
* [[QA:Testcase Virtualization Virtio SCSI Hotplug]]
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]


==== libguestfs and tools ====
=== libguestfs and tools ===


You will need Fedora 18 (host) and at least one guest (but the more the merrier).
You will need Fedora 18 (host) and at least one guest (but the more the merrier).
Line 92: Line 124:
In Fedora 18, we are using [http://libvirt.org libvirt] to launch the appliance, and [http://selinuxproject.org/page/SVirt sVirt] + SELinux to make everything [http://libguestfs.org/guestfs.3.html#security much more secure].  Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.
In Fedora 18, we are using [http://libvirt.org libvirt] to launch the appliance, and [http://selinuxproject.org/page/SVirt sVirt] + SELinux to make everything [http://libguestfs.org/guestfs.3.html#security much more secure].  Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.


==== GuestOS compatibility ====
=== Previous test cases ===
 
Some test cases used in previous test days. Still useful to test for regressions!
 
Migration:
 
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration with virsh]]
* [[QA:Testcase Offline (paused) Migration using libvirt/virsh|Offline migration with virsh]]
 
Hotplug:
 
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]
* [[QA:Testcase Virtualization Attach/Detach a SCSI device to guest|SCSI hotplug with virsh]]
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug with virsh]]
 
virtio-scsi:
 
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]
 
 
== Test Results ==
 
Each tester should add a row for their results.
 
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!
 
<!-- Don't touch this part! -->
{|
! User
! VM Install
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]
! [[QA:Testcase Virtualization Live Backup|Live Backup]]
! [[QA:Testcase Virtualization Guest Suspend Hibernate|Suspend]]
! [[QA:Testcase Virtualization Seccomp Sandboxing|Seccomp]]
! [[QA:Testcase Virtualization IO Throttling|IO Throttling]]
! [[QA:Testcase Virtualization PV EOI|PV EOI]]
! [[QA:Testcase Virtualization USB3 Device Passthrough|USB3]]
! [[QA:Testcase Virtualization USB Redirection|USB Redir]]
! References
|-
 
 
<!-- Copy the block below as a template
 
| [[User:SampleUser|SampleUser]]
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
 
-->
 
| [[User:crobinso|crobinso]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail}} <ref>Guest fails to start {{bz|855162}}</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>USB Device didn't appear in lsusb -t in guest</ref>
| {{result|done}}
| <references/>
|-
 
| [[User:kashyapc|Kashyap Chamarthy]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
 
 
| [[User:mkrizek|mkrizek]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|pass}}
| {{result|pass}} <ref>Reduced only from approx. 15.000 to 12.000</ref>
| {{result|none}}
| {{result|pass}}
| <references/>
|-
 
| [[User:mrezanin|mrezanin]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|pass}}
| <references/>
|-
| [[User:pschindl|pschindl]]
| {{result|warn||872162}}
| {{result|fail||869607}}
|
| {{result|pass}} <ref>I tested only guest functionality, when I try agent I got 'Error starting domain: Unable to read from monitor: Connection reset by peer'</ref>
|
|
|
|
|
| <references/>
|-
| [[User:stefanha|Stefan Hajnoczi]]
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|pass}} <ref group="long">Throttling works but virsh blkdeviotune reports incorrect results.  I have sent patches here: https://www.redhat.com/archives/libvir-list/2012-November/msg00095.html {{bz|872582}}</ref>
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
 
|-
| [[User:ericb|Eric Blake]]
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}} <ref>{{bz|872292}} found by inspection based on an IRC question, latent bug which affects snapshots, among other operations</ref>
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| <references/>
 
|-
| [[User:Sagarun|Arun S A G]]
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|pass}}<ref>{{bz|872343}} Cannot resume RHEL6 vm running at runlevel 3  </ref>
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
 
| [[User:kparal|kparal]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail||872573}}
| {{result|none}}
| {{result|fail||872582}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|
|-
| [[User:knoel|Karen Noel]]
| {{result|pass}} <ref>Installed RHEL6.3 and F18 guests</ref>
| {{result|inprogress}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
 
|}


* [[Test_Day:2012-04-12_Virtualization_Test_Day-GuestOS | GuestOS compatibility]] <br>&mdash; test installation of as many different guest operating system as as possible. (You will need a KVM bare metal host & lots of disk space)
== Long comments ==
<references group="long" />


[[Category:Fedora 18 Test Days]]
  [[Category:Fedora 18 Test Days]]
[[Category:Virtualization]]
[[Category:Virtualization]]

Latest revision as of 19:42, 26 June 2015

Fedora Test Days
Virtualization Test Day
Date 2012-11-01
Time all day
Website Virtualization
IRC #fedora-test-day (webirc IRC logs)
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 in Fedora 18. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 18.

Who's available[edit]

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

Known issues[edit]

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

For starters, your physical machine should have:

  • 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.
  • 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:

Fedora 18 on a physical machine[edit]

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

  • Upgrade from Fedora 17

Fedora 18 virt packages on Fedora 17[edit]

If you aren't ready to make the jump to Fedora 18, this is the next best thing! Run latest virt packages on Fedora 17 from the virt-preview repo:

http://fedoraproject.org/wiki/Virtualization_Preview_Repository

Run Fedora 18 in a VM with nested virtualization[edit]

Do you have a new machine with a ton of ram and storage space, running Fedora 17? Nested virt might be an option! This allows you to create KVM guests _inside_ a Fedora 18 VM.

  1. Install the latest virt packages from virt-preview using the instructions above.
  2. Install a Fedora 18 guest using one of the test cases below.
  3. Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: 
    virt-host-validate

Some notes on nested virt with AMD and Intel:

Areas to test[edit]

VM Install[edit]

Record your results for these test cases in the Test Results section.

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:

New tests and features[edit]

Record your results for these test cases in the Test Results section.

libguestfs and tools[edit]

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.

Previous test cases[edit]

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

Migration:

Hotplug:

virtio-scsi:


Test Results[edit]

Each tester should add a row for their results.

If you have problems with any of the tests, report a bug to Bugzilla. If you have any questions about what component to file against, just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!

User VM Install VM Lifecycle Live Backup Suspend Seccomp IO Throttling PV EOI USB3 USB Redir References
crobinso
Pass pass
Pass pass
Pass pass
Pass pass
Fail fail
[1]
Pass pass
Pass pass
Warning warn
[2]
done
  1. ↑ Guest fails to start RHBZ #855162
  2. ↑ USB Device didn't appear in lsusb -t in guest
Kashyap Chamarthy
Pass pass
Pass pass
Pass pass
none
none
none
none
none
none
mkrizek
Pass pass
Pass pass
Pass pass
Pass pass
none
Pass pass
Pass pass
[1]
none
Pass pass
  1. ↑ Reduced only from approx. 15.000 to 12.000
mrezanin
Pass pass
Pass pass
Pass pass
Pass pass
none
Pass pass
none
none
Pass pass
pschindl
Warning warn [1]
Fail fail [2]
Pass pass
[3]
  1. ↑ RHBZ #872162
  2. ↑ RHBZ #869607
  3. ↑ I tested only guest functionality, when I try agent I got 'Error starting domain: Unable to read from monitor: Connection reset by peer'
Stefan Hajnoczi
Pass pass
none
none
none
none
Pass pass
[long 1]
none
none
none
Eric Blake
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
[1]
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. ↑ RHBZ #872292 found by inspection based on an IRC question, latent bug which affects snapshots, among other operations
Arun S A G
Pass pass
Pass pass
none
Pass pass
[1]
none
none
none
none
none
  1. ↑ RHBZ #872343 Cannot resume RHEL6 vm running at runlevel 3
kparal
Pass pass
Pass pass
Pass pass
Fail fail [1]
none
Fail fail [2]
none
none
none
  1. ↑ RHBZ #872573
  2. ↑ RHBZ #872582
Karen Noel
Pass pass
[1]
Inprogress inprogress
none
none
none
none
none
none
none
  1. ↑ Installed RHEL6.3 and F18 guests

Long comments[edit]

  1. ↑ Throttling works but virsh blkdeviotune reports incorrect results. I have sent patches here: https://www.redhat.com/archives/libvir-list/2012-November/msg00095.html RHBZ #872582
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2012-11-01_Virtualization&oldid=416682"