Editing Test Day:2010-04-08 Virtualization XenDomU

{|border="1"
|-style="color: white; background-color: #3074c2; font-weight: bold" 
| DATE || TIME || WHERE
|-
| [[Test_Day:2010-04-08_Virtualization|Thursday Apr 08, 2010]] || All day || [irc://irc.freenode.net/fedora-test-day #fedora-test-day]  ([http://webchat.freenode.net/?channels=fedora-test-day webchat])
|-
|}


=== What to test? ===

This part of [[Test_Day:2010-04-08_Virtualization|today's Fedora Test Day]] will focus on testing the area concerned with Xen DomU functionality, which is based on the [[Features/XenPvops|pv_ops]] work in upstream Linux.

If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test Fedora as a Xen DomU and provide feedback.

=== Who's available ===

[[User:drjones|Andrew Jones (Drew)]] is your host for today.

The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:

* [[User:jforbes|Justin Forbes]]

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

* A distribution with Xen Dom0 support. This can either be Red Hat Enterprise Linux 5, CentOS 5, Suse, Fedora, etc. We also highly recommend that your distribution is fully updated to the latest released packages. See instructions on the [[Test_Day:2010-04-08_Virtualization|main test day page]].
* At least one guest image installed before the test day (suggested reading - [[Virtualization_Quick_Start]]).

=== Known issues and workarounds ===

Console may not work ('xm console <domain>') until 'console=hvc0' has been added to the kernel command line in grub.conf.

Note, the following list of issues were compiled while testing on RHEL 5.4. Other host platforms and/or Xen packages may have varying results.  Please test :-)

* RHEL specific: pygrub does not support ext4, however rawhide defaults to ext4. Therefore this must be manually changed to ext3 (at least for /boot) during the installation, or an appropriate kickstart can be used.
* RHEL specific on machines with GB pages: add 'nogbpages' to the guest kernel command-line for guests with >2GB memory, see [https://bugzilla.redhat.com/show_bug.cgi?id=502826 bz502826]
* RHEL specific on machines with xsave: add 'noxsave' to the guest kernel command-line for hvm guests, see [https://bugzilla.redhat.com/show_bug.cgi?id=524052 bz524052]

If the above workarounds are done, or RHEL 5.5 is used, then these known issues will still be present.

* Installing from the F13 compose will fail for PV guests since it uses the 2.6.33 kernel (see [https://bugzilla.redhat.com/show_bug.cgi?id=571241 bz571241]). Workaround this by updating an F12 guest to F13, and then updating the kernel to 2.6.33.2. After updating the kernel for F13 PV guests, ensure also that plymouth is rev. 0.8.1-3.fc13 and that the initrd contains this rev as well (see [https://bugzilla.redhat.com/show_bug.cgi?id=578633 bz578633]).
* Installing a FV guest from the F13 boot.iso or attempting to boot the F13 Virt-Test LiveCD will fail (see [https://bugzilla.redhat.com/show_bug.cgi?id=570496 bz570496]). Workaround this by rewriting the iso with 'nohalt 1' added to the top of the isolinux.cfg file.
* Installing a FV guest will appear to have hung since the graphics in anaconda's virtual terminal 'F6' do not work. Watch the progress on virtual terminal 'F1' to see that the installation is progressing.

=== Test cases ===

Execute the list of test cases for each of the following configurations:

32-bit Dom0
* 32-bit PV DomU
* 32-bit HVM DomU

64-bit Dom0
* 32-bit PV DomU
* 32-bit HVM DomU
* 64-bit PV DomU
* 64-bit HVM DomU

Test cases:

# [[QA:Testcase_Virtualization_XenDomU_Guest_installation|Guest install]]
# [[QA:Testcase_Virtualization_XenDomU_Memory_Ballooning|Memory ballooning]]
# [[QA:Testcase_Virtualization_XenDomU_Save_and_restore|Save/restore]]
# [[QA:Testcase_Virtualization_XenDomU_Live_migration|Live migration]]
# [[QA:Testcase_Virtualization_XenDomU_Pause|Guest pause/unpause]]
# [[QA:Testcase_Virtualization_XenDomU_CPU_hotplug|CPU hotplug]]
# [[QA:Testcase_Virtualization_XenDomU_Network|Network devices]]
# [[QA:Testcase_Virtualization_XenDomU_Network_Performance|Network Performance]]
# [[QA:Testcase_Virtualization_XenDomU_Block_attach|Block attach/detach]]
# [[QA:Testcase_Virtualization_XenDomU_File_IO_Performance|File IO Performance]]
# [[QA:Testcase_Virtualization_XenDomU_PVFB|Paravirt framebuffer]]
# [[QA:Testcase_Virtualization_XenDomU_Crash_dump|Guest crash dump]]
# [[QA:Testcase_Virtualization_XenDomU_Execshield|Execshield]]
# [[QA:Testcase_Virtualization_XenDomU_GDB|GDB]]
# [[QA:Testcase_Virtualization_XenDomU_Static_binaries|Statically linked binaries]]
# [[QA:Testcase_Virtualization_XenDomU_Cmdline_params|Kernel command line parameters]]
# [[QA:Testcase_Virtualization_XenDomU_No_NX|Host machine lacking NX support]]
# [[QA:Testcase_Virtualization_XenDomU_LDT|Attempt to use the modify_ldt syscall]]

See [[How to debug Virtualization problems|Reporting Virtualization bugs]] for a guide to reporting bugs.

=== Issues that were identified ===

{| border="1"
|-style="color: white; background-color: #3074c2; font-weight: bold" 
| Tester || Description || Bug references || Status
|-
| || || [http://bugzilla.redhat.com/XXXXXX #XXXXX] || '''ASSIGNED'''
|}

[[Category:Fedora_13_Test_Days]]
[[Category:Virtualization]]