Li, Haicheng
2008-Mar-27 13:11 UTC
[Xen-devel] VMX status report for Xen-3.2.1-rc1. Xen: #16821 & Xen0: #488
Hi all,
Here is our testing report for Xen-3.2.1-rc1; since pv build was failed
against this c/s, device model cases were aborted.
Actually we conducted two rounds of nightly testing on this c/s; in 1st
round we met dom0 crash on IA32E, but it cannot be reproduced in 2nd
round of testing or manually retesting; the case " boot up 1 winXP VMX
and 1 linux VMX" caused this crash, we captured serial log of this crash
and attached it with this email, hopefully it could provide some hint of
this failure. Other failed cases can get pass by manually retesting.
Testing environments:
=============================================PAE
Dom0 OS Fedora6
CPU Clovertown
Memory size 8G
IA32E
Dom0 OS RHEL5
CPU Clovertown
Memory size 8G
IA32PAE test result:
=======================================================Platform : PAE
Service OS : Fedora Core release 6 (Zod)
Hardware : Clovertown
1. 2 PAE SMP VMX domains and 2 xenU domains coexist FAIL
2. Live and migration PASS
3. Save and Restore PASS
4. one PAE SMP Linux VMX domain with memory 256M PASS
5. one PAE SMP Linux VMX domain with memory 1500M PASS
6. one PAE SMP Linux VMX domain with memory 4G PASS
7. boot 4 VMX per processor at the same time PASS
8. boot up 1 winXP VMX and 1 linux PAE VMX PASS
9. Single domain with single vcpu bind a CPU PASS
10. boot up two winXP per processor at the same time PASS
11. boot up one linux VMX with 4 vcpus PASS
12. boot up four linux VMX one by one PASS
13. boot up VMX with acpi=1, vcpu=1 PASS
14. subset LTP test in RHEL4U2 PAE SMP VMX domain PASS
15. Boot Linux 2.6.23 base kernel in RHEL4U1 PAE SMP Linux VMX domain
PASS
16. one IA32 UP ACPI Windows 2K VMX domain PASS
17. one IA32 UP ACPI Windows 2K3 VMX domain PASS
18. one IA32 UP ACPI Windows XP VMX domain PASS
19. one IA32 UP ACPI Vista VMX domain
PASS
20. one IA32 SMP ACPI Windows 2K VMX domain PASS
21. one IA32 SMP ACPI Windows 2K3 VMX domain PASS
22. one IA32 SMP ACPI Windows XP VMX domain PASS
23. one IA32 SMP ACPI Vista VMX domain
PASS
24. one IA32 UP NOACPI Windows 2K VMX domain PASS
25. one IA32 UP NOACPI Windows 2K3 VMX domain PASS
26. one IA32 UP NOACPI Windows XP VMX domain PASS
27. kernel build in one linux VMX PASS
28. startx in dom0 PASS
29. boot up one IA32 RHEL5u1 VMX domain. PASS
30. boot up one IA32 Fedora 7 VMX domain PASS
31. boot up one IA32 Fedora 8 VMX domain PASS
32. reboot Windows xp after it boot up. FAIL
33. reboot Fedora core 6 after it boot up. PASS
34. VBD and VNIF works on UP VMX domain
NORESULT
35. VBD and VNIF works on SMP VMX domain
NORESULT
36. assign one pcie nic to one UP Linux guest with vtd. PASS
37. assign one pcie nic to one SMP Linux guest with vtd. PASS
38. assign one pcie nic to one UP WinXP guest with vtd. PASS
39. assign one pci nic to one SMP Linux guest with vtd. PASS
40. assign one pci nic to one UP WinXP guest with vtd. PASS
41. assign one pci nic to one UP Linux guest with vtd PASS
42. scp a big file in Linux guest via the pci nic assigned with vt-d.
PASS
43. assign one pcie nic to one SMP WinXP guest with vtd.
PASS
44. assign one pci nic to one SMP WinXP guest with vtd.
PASS
45. scp a big file in Linux guest via the pcie nic assigned with vt-d.
PASS
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd
10 10 0 0 0
device_model 2 0 0 2 0
control_panel 12 11 1 0 0
Restart 1 1 0 0 0
gtest 21 20 1 0 0
====================================================================vtd
10 10 0 0 0
:one_pcie_scp_PAE_gPAE 1 1 0 0 0
:one_pci_smp_xp_PAE_gPAE 1 1 0 0 0
:one_pcie_up_xp_PAE_gPAE 1 1 0 0 0
:one_pci_smp_PAE_gPAE 1 1 0 0 0
:one_pci_up_xp_PAE_gPAE 1 1 0 0 0
:one_pcie_smp_PAE_gPAE 1 1 0 0 0
:one_pcie_smp_xp_PAE_gPA 1 1 0 0 0
:one_pci_scp_PAE_gPAE 1 1 0 0 0
:one_pcie_up_PAE_gPAE 1 1 0 0 0
:one_pci_up_PAE_gPAE 1 1 0 0 0
device_model 2 0 0 2 0
:pv_on_up_PAE_gPAE 1 0 0 1 0
:pv_on_smp_PAE_gPAE 1 0 0 1 0
control_panel 12 11 1 0 0
:XEN_4G_guest_PAE_gPAE 1 1 0 0 0
:XEN_four_vmx_xenu_seq_P 1 0 1 0 0
:XEN_LM_PAE_gPAE 1 1 0 0 0
:XEN_four_dguest_co_PAE_ 1 1 0 0 0
:XEN_linux_win_PAE_gPAE 1 1 0 0 0
:XEN_SR_PAE_gPAE 1 1 0 0 0
:XEN_vmx_vcpu_pin_PAE_gP 1 1 0 0 0
:XEN_two_winxp_PAE_gPAE 1 1 0 0 0
:XEN_256M_guest_PAE_gPAE 1 1 0 0 0
:XEN_1500M_guest_PAE_gPA 1 1 0 0 0
:XEN_vmx_2vcpu_PAE_gPAE 1 1 0 0 0
:XEN_four_sguest_seq_PAE 1 1 0 0 0
Restart 1 1 0 0 0
:GuestPAE_PAE_gPAE 1 1 0 0 0
gtest 21 20 1 0 0
:boot_fc7_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_PAE_gPAE 1 1 0 0 0
:ltp_nightly_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_xp_PAE_gPA 1 1 0 0 0
:reboot_xp_PAE_gPAE 1 0 1 0 0
:boot_up_vista_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_win2k3_PAE 1 1 0 0 0
:boot_smp_acpi_win2k3_PA 1 1 0 0 0
:boot_smp_acpi_win2k_PAE 1 1 0 0 0
:boot_up_acpi_win2k_PAE_ 1 1 0 0 0
:boot_smp_acpi_xp_PAE_gP 1 1 0 0 0
:boot_up_noacpi_win2k_PA 1 1 0 0 0
:boot_smp_vista_PAE_gPAE 1 1 0 0 0
:boot_up_noacpi_win2k3_P 1 1 0 0 0
:boot_rhel5u1_PAE_gPAE 1 1 0 0 0
:boot_base_kernel_PAE_gP 1 1 0 0 0
:boot_up_noacpi_xp_PAE_g 1 1 0 0 0
:bootx_PAE_gPAE 1 1 0 0 0
:reboot_fc6_PAE_gPAE 1 1 0 0 0
:boot_fc8_PAE_gPAE 1 1 0 0 0
:kb_nightly_PAE_gPAE 1 1 0 0 0
====================================================================Total
46 42 2 2 0
IA32E test result:
===============================================================Platform : x86_64
Service OS : Red Hat Enterprise Linux Server release 5 (Tikanga)
Hardware : Clovertown
1. boot up four PAE linux VMX one by one
PASS
2. one PAE xenU domain with memory 256M PASS
3. one PAE SMP Linux VMX domain with memory 1500M PASS
4. one PAE SMP Linux VMX domain with memory 4G PASS
5. one PAE SMP Linux VMX domain with memory 256M PASS
6. 2 ia32E SMP VMX domains and 2 xenU domains coexist PASS
7. Live and migration PASS
8. Save and Restore PASS
9. one ia32E SMP Linux VMX domain with memory 1500M PASS
10. one ia32E SMP Linux VMX domain with memory 4G
PASS
11. one ia32E SMP Linux VMX domain with memory 256M PASS
12. boot 4 VMX per processor at the same time PASS
13. boot up 1 winXP VMX and 1 linux VMX PASS
14. Single domain with single vcpu bind a CPU PASS
15. boot up two winXP per processor at the same time PASS
16. boot up one linux VMX with 4 vcpus PASS
17. boot up four linux VMX one by one PASS
18. Boot up VMX with acpi=1, vcpu=1 PASS
19. subset LTP test in RHEL4U2 ia32E SMP VMX domain PASS
20. one IA32E UP ACPI Windows 2K3 VMX domain PASS
21. one IA32E UP ACPI Windows 2K VMX domain PASS
22. one IA32E UP ACPI Windows XP VMX domain PASS
23. one IA32E UP ACPI Vista VMX domain
PASS
24. one IA32E SMP ACPI Windows 2K3 VMX domain PASS
25. one IA32E SMP ACPI Windows 2K VMX domain PASS
26. one IA32E SMP ACPI Windows XP VMX domain PASS
27. one IA32E SMP ACPI Vista VMX domain
PASS
28. one IA32E UP NOACPI Windows 2K VMX domain PASS
29. boot Linux 2.6.23 base kernel in ia32E SMP Linux VMX domain PASS
30. kernel build in one ia32E linux VMX PASS
31. startx in dom0 PASS
32. boot up one IA32E RHEL5u1 VMX domain. PASS
33. boot up one IA32E Fedora 7 VMX domain PASS
34. boot up one IA32E Fedora 8 VMX domain PASS
35. reboot Windows xp after it boot up. FAIL
36. reboot Fedora core 6 after it boot up. PASS
37. VBD and VNIF works on UP VMX domain
NORESULT
38. VBD and VNIF works on SMP VMX domain
NORESULT
39. assign one pcie nic to one UP Linux guest with vtd. PASS
40. assign one pcie nic to one SMP Linux guest with vtd. PASS
41. assign one pcie nic to one UP WinXP guest with vtd. PASS
42. assign one pci nic to one SMP Linux guest with vtd. PASS
43. assign one pci nic to one UP WinXP guest with vtd. PASS
44. assign one pci nic to one UP Linux guest with vtd PASS
45. scp a big file in Linux guest via the pci nic assigned with vt-d.
PASS
46. assign one pcie nic to one SMP WinXP guest with vtd.
PASS
47. assign one pci nic to one SMP WinXP guest with vtd.
PASS
48. scp a big file in Linux guest via the pcie nic assigned with vt-d.
PASS
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd
10 10 0 0 0
device_model 2 0 0 2 0
control_panel 17 17 0 0 0
Restart 2 2 0 0 0
gtest 19 18 1 0 0
====================================================================vtd
10 10 0 0 0
:one_pcie_smp_xp_64_g64 1 1 0 0 0
:one_pci_smp_xp_64_g64 1 1 0 0 0
:one_pcie_up_xp_64_g64 1 1 0 0 0
:one_pcie_up_64_g64 1 1 0 0 0
:one_pcie_scp_64_g64 1 1 0 0 0
:one_pci_scp_64_g64 1 1 0 0 0
:one_pci_up_xp_64_g64 1 1 0 0 0
:one_pci_smp_64_g64 1 1 0 0 0
:one_pcie_smp_64_g64 1 1 0 0 0
:one_pci_up_64_g64 1 1 0 0 0
device_model 2 0 0 2 0
:pv_on_smp_64_g64 1 0 0 1 0
:pv_on_up_64_g64 1 0 0 1 0
control_panel 17 17 0 0 0
:XEN_1500M_guest_64_g64 1 1 0 0 0
:XEN_256M_xenu_64_gPAE 1 1 0 0 0
:XEN_1500M_guest_64_gPAE 1 1 0 0 0
:XEN_4G_guest_64_gPAE 1 1 0 0 0
:XEN_256M_guest_64_g64 1 1 0 0 0
:XEN_SR_64_g64 1 1 0 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
:XEN_vmx_2vcpu_64_g64 1 1 0 0 0
:XEN_vmx_vcpu_pin_64_g64 1 1 0 0 0
:XEN_linux_win_64_g64 1 1 0 0 0
:XEN_256M_guest_64_gPAE 1 1 0 0 0
:XEN_LM_64_g64 1 1 0 0 0
:XEN_two_winxp_64_g64 1 1 0 0 0
:XEN_four_vmx_xenu_seq_6 1 1 0 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
:XEN_4G_guest_64_g64 1 1 0 0 0
:XEN_four_dguest_co_64_g 1 1 0 0 0
Restart 2 2 0 0 0
:Guest64_64_gPAE 1 1 0 0 0
:GuestPAE_64_g64 1 1 0 0 0
gtest 19 18 1 0 0
:boot_smp_acpi_xp_64_g64 1 1 0 0 0
:boot_fc7_64_g64 1 1 0 0 0
:boot_base_kernel_64_g64 1 1 0 0 0
:ltp_nightly_64_g64 1 1 0 0 0
:boot_up_acpi_64_g64 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:boot_fc8_64_g64 1 1 0 0 0
:bootx_64_g64 1 1 0 0 0
:reboot_xp_64_g64 1 0 1 0 0
:boot_smp_acpi_win2k_64_ 1 1 0 0 0
:boot_up_vista_64_g64 1 1 0 0 0
:boot_up_noacpi_win2k_64 1 1 0 0 0
:boot_smp_vista_64_g64 1 1 0 0 0
:boot_up_acpi_win2k_64_g 1 1 0 0 0
:reboot_fc6_64_g64 1 1 0 0 0
:boot_up_acpi_xp_64_g64 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_rhel5u1_64_g64 1 1 0 0 0
:kb_nightly_64_g64 1 1 0 0 0
====================================================================Total
50 47 1 2 0
-- haicheng
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2008-Mar-27 13:53 UTC
Re: [Xen-devel] VMX status report for Xen-3.2.1-rc1. Xen: #16821 & Xen0: #488
On 27/3/08 13:11, "Li, Haicheng" <haicheng.li@intel.com> wrote:> Actually we conducted two rounds of nightly testing on this c/s; in 1st > round we met dom0 crash on IA32E, but it cannot be reproduced in 2nd > round of testing or manually retesting; the case " boot up 1 winXP VMX > and 1 linux VMX" caused this crash, we captured serial log of this crash > and attached it with this email, hopefully it could provide some hint of > this failure. Other failed cases can get pass by manually retesting.Somehow you ended up in ipv6 code in the dom0 kernel. Probably not something you want, and not something that''s particularly well tested. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2008-Mar-27 13:54 UTC
Re: [Xen-devel] VMX status report for Xen-3.2.1-rc1. Xen: #16821 & Xen0: #488
On 27/3/08 13:11, "Li, Haicheng" <haicheng.li@intel.com> wrote:> Here is our testing report for Xen-3.2.1-rc1; since pv build was failed > against this c/s, device model cases were aborted.This is fixed. I''ll do a -rc2 later this week. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel