From Fedora Project Wiki

No edit summary
m (changed category)
 
(40 intermediate revisions by 5 users not shown)
Line 10: Line 10:
=== What to test? ===
=== What to test? ===


This part of [[Test_Day:2009-09-17_Virtualization|today's Fedora Test Day]] will focus on testing the area concerned with Xen DomU functionality, which is based on the pv_ops work in upstream Linux.
This part of [[Test_Day:2009-09-17_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.
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.
Line 16: Line 16:
=== Who's available ===
=== Who's available ===


[[User:drjones|Andrew (Drew) Jones]] is your host for today.
[[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:
The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:
Line 24: Line 24:
=== What's needed to test ===
=== What's needed to test ===


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


=== Test Cases ===
=== Known issues and workarounds ===


Follow each of these test cases:
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.
* 'xm console <domain>' will not work until 'console=hvc0' has been added to the kernel command line in grub.conf, see [https://bugzilla.redhat.com/show_bug.cgi?id=523623 bz523623].
* 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]
 
=== 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
* 64-bit PV DomU
* 64-bit HVM DomU
 
Test cases:


# [[QA:Testcase_Virtualization_XenDomU_Guest_installation|Guest install]]
# [[QA:Testcase_Virtualization_XenDomU_Guest_installation|Guest install]]
Line 38: Line 57:
# [[QA:Testcase_Virtualization_XenDomU_CPU_hotplug|CPU hotplug]]
# [[QA:Testcase_Virtualization_XenDomU_CPU_hotplug|CPU hotplug]]
# [[QA:Testcase_Virtualization_XenDomU_Network|Network devices]]
# [[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_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_PVFB|Paravirt framebuffer]]
# [[QA:Testcase_Virtualization_XenDomU_Crash_dump|Guest crash dump]]
# [[QA:Testcase_Virtualization_XenDomU_Crash_dump|Guest crash dump]]
Line 46: Line 67:
# [[QA:Testcase_Virtualization_XenDomU_Cmdline_params|Kernel command line parameters]]
# [[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_No_NX|Host machine lacking NX support]]
# [[QA:Testcase_Virtualization_XenDomU_LDT|Attempt to use the modify_ldt syscall]]


If possible each of the tests should be repeated for:
See [[How to debug Virtualization problems|Reporting Virtualization bugs]] for a guide to reporting bugs.
 
# 32-bit DomU on a 32-bit Dom0
# 32-bit DomU on a 64-bit Dom0
# 64-bit DomU on a 64-bit Dom0
 


=== Issues that were identified ===
=== Issues that were identified ===
Line 60: Line 77:
| Tester || Description || Bug references || Status
| Tester || Description || Bug references || Status
|-  
|-  
| || || [http://bugzilla.redhat.com/XXXXXX #XXXXX] || '''ASSIGNED'''
| [[User:Jdenemar|jdenemar]] || Mouse doesn't work in Fedora running as a Xen PV guest || [https://bugzilla.redhat.com/523914 #523914] || '''NEW'''
|-
| [[User:Jdenemar|jdenemar]] || 32b kernel doesn't boot in Xen PV guest on 64b host || [https://bugzilla.redhat.com/523941 #523941] || '''NEW'''
|-
| [[User:Jdenemar|jdenemar]] || xm save hangs with kernel-2.6.31-14.fc12 running as a Xen PV guest || [https://bugzilla.redhat.com/523971 #523971] || '''NEW'''
|-
| mrezanin || Save on restored machine failed || [https://bugzilla.redhat.com/523939 #523939] || '''NEW'''
|-
| [[User:Drjones|drjones]] || add console=hvc0 to grub.conf || [https://bugzilla.redhat.com/523623 #523623] || '''NEW'''
|-
| [[User:Drjones|drjones]] || boot hang when installing 64-bit HVM || [https://bugzilla.redhat.com/524052 #524052] || '''NEW'''
|-
| [[User:Drjones|drjones]] || block device cannot be detached || [https://bugzilla.redhat.com/524039 #524039] || '''NEW'''
|}
|}


[[Category:Test Days]]
[[Category:Fedora_12_Test_Days]]
[[Category:Virtualization]]
[[Category:Virtualization]]

Latest revision as of 14:21, 3 February 2010

DATE TIME WHERE
Thursday Sep 17, 2009 All day #fedora-test-day (webchat)


What to test?[edit]

This part of today's Fedora Test Day will focus on testing the area concerned with Xen DomU functionality, which is based on the 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[edit]

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:

  • add your name here

What's needed to test[edit]

  • 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 main test day page.
  • At least one guest image installed before the test day (suggested reading - Virtualization_Quick_Start).

Known issues and workarounds[edit]

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.
  • 'xm console <domain>' will not work until 'console=hvc0' has been added to the kernel command line in grub.conf, see bz523623.
  • RHEL specific on machines with GB pages: add 'nogbpages' to the guest kernel command-line for guests with >2GB memory, see bz502826

Test cases[edit]

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
  • 64-bit PV DomU
  • 64-bit HVM DomU

Test cases:

  1. Guest install
  2. Memory ballooning
  3. Save/restore
  4. Live migration
  5. Guest pause/unpause
  6. CPU hotplug
  7. Network devices
  8. Network Performance
  9. Block attach/detach
  10. File IO Performance
  11. Paravirt framebuffer
  12. Guest crash dump
  13. Execshield
  14. GDB
  15. Statically linked binaries
  16. Kernel command line parameters
  17. Host machine lacking NX support
  18. Attempt to use the modify_ldt syscall

See Reporting Virtualization bugs for a guide to reporting bugs.

Issues that were identified[edit]

Tester Description Bug references Status
jdenemar Mouse doesn't work in Fedora running as a Xen PV guest #523914 NEW
jdenemar 32b kernel doesn't boot in Xen PV guest on 64b host #523941 NEW
jdenemar xm save hangs with kernel-2.6.31-14.fc12 running as a Xen PV guest #523971 NEW
mrezanin Save on restored machine failed #523939 NEW
drjones add console=hvc0 to grub.conf #523623 NEW
drjones boot hang when installing 64-bit HVM #524052 NEW
drjones block device cannot be detached #524039 NEW