| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] FW: Weekly VMX status report. Xen: #18711 & Xen0: #711
I have to resend this report since previous one seems lost.
Li, Haicheng wrote:
> Hi all,
>
> This is our weekly test report for Xen-unstable tree. 3 new issues
> were found, bug #1368 got fixed; P1 bug #1339 still blocks our
> save/restore related cases.
>
> New Bugs:
> =====================================================================
> 1. [stubdom]The xm save command hangs while saving <Domain-dm>.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1377
> 2. [stubdom] cannot restore stubdom based domain.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1378
> 3. [VT-d] failed to reassign some PCI-e NICs.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1379
>
> Fixed Bugs:
> =====================================================================
> 1. [vt-d][MSI] some call traces printed to serial port
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1368
>
> Old Bugs:
> =====================================================================
> 1. SMP 32e RHEL5.1 timer would be slow,if under working pressure.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1290
> 2. Guest will hang after Save/Restore.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1339
> 3. with AHCI disk drive, dom S3 resume is failed.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1374
> 4. TSC not accurate in Windows HVM.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1291
> 5. stubdom based guest hangs at starting when using qcow image.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1372
> 6. stubdom based guest hangs when assigning hdc to it.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1373
>
> Testing Environment:
> =====================================================================
> PAE
> CPU : Xeon(r) processor 5300 series
> Dom0 OS : RHEL5.1
> Memory size : 8G
>
> IA32E
> CPU : Xeon(r) processor 5300 series
> Dom0 OS : RHEL5
> Memory size : 8G
>
> Details:
> =====================================================================
> Platform : PAE
> Service OS: Red Hat Enterprise Server Release 5.1(Tikanga)
> Hardware : Clovertown
> Xen package: 18711
> Date: Fri Oct 24 16:00:00
>
> 1. One PAE SMP Linux VMX domain with 256M memory
> PASS
> 2. One PAE SMP Linux VMX domain with 1500M memory
> PASS
> 3. One PAE SMP Linux VMX domain with 4G memory
> PASS
> 4. Create 4 diffierent Linux VMX domain per processor at the
> sametime PASS
> 5. Create 4 same Linux VMX domain one by one
> PASS
> 6. boot up two winxp per processor at the same time
> PASS
> 7. boot up one Linux PAD VMX and 1 winxp VMX
> PASS
> 8. boot up one linux VMX with 2 vcpus
> PASS
> 9. boot up four VMX XenU guest one by one
> PASS
> 10. boot up single domain with single vcpu binds a CPU
> PASS
> 11. Control panel HVM save/restore process continuity test
> FAIL
> 12. Cpu number test after save/restore
> FAIL
> 13. Control panel HVM live/migration process continuity test
> FAIL
> 14. Cpu number test after live/migration
> FAIL
> 15. VBD & VNIF works on an UP VMX domain
> PASS
> 16. VBD & VNIF works on a SMP VMX domain
> PASS
> 17. Boot up 2.6.23-rc4 kernel based linux in REHLE4U1 PAE SMP
> domain PASS
> 18. subset LTP test in RHEL4u2 PAE SMP VMX domain
> PASS
> 19. Kernel build in UP_VMX domain
> PASS
> 20. Boot up UP_Non_ACPI Win 2k3 VMX guest
> PASS
> 21. Boot up UP_Non_ACPI WinXP VMX guest
> PASS
> 22. Boot up UP Win Vista guest
> PASS
> 23. Boot up UP Win 2008 server guest
> PASS
> 24. Boot up UP_Non_ACPI Win 2k VMX guest
> PASS
> 25. Boot up UP_ACPI IA32 Win2k3 VMX guest
> PASS
> 26. Boot up UP_ACPI IA32 XPSP2 VMX guest
> PASS
> 27. Boot up UP_ACPI IA32 Win2k VMX guest
> PASS
> 28. VMX WinXP reboot
> PASS
> 29. VMX fedora6 reboot
> PASS
> 30. Boot up Rhel5u1 VMX guest with time_mode=1
> PASS
> 31. Boot up Fedora9 VMX guest with time_mode=1
> PASS
> 32. Boot up SMP_ACPI win2k VMX guest
> PASS
> 33. Boot up SMP_ACPI ia32 win2k3 VMX guest
> PASS
> 34. Boot up SMP_ACPI winXPSP2 VMX guest
> PASS
> 35. Boot up SMP Win Vista VMX guest
> PASS
> 36. Boot up SMP Win2008 VMX guest
> PASS
> 37. Boot up nevada VMX guest
> PASS
> 38. Boot up indiana VMX guest
> PASS
> 39. Assign 2 NICs to one UP Linux guest with VT-d(nomsi)
> PASS
> 40. Assign 2 NICs to one SMP Linux guest with VT-d(nomsi)
> PASS
> 41. Assign 2 NICs to one UP winxp guest with VT-d(nomsi)
> PASS
> 42. Assign 2 NICs to one SMP winxp guest with VT-d(nomsi)
> PASS
> 43. Scp a big file when NIC is assigned to the linux guest by
> VT-D(nomsi) PASS
> 44. Test UP Linux guest hotplug with VT-d(pci)
> PASS
> 45. Test SMP Linux guest hotplug with VT-d(pci)
> PASS
> 46. Test UP WinXP guest hotplug with VT-d(pci)
> PASS
> 47. Test SMP winXP guest hotplug with VT-d(pci)
> PASS
> 48. Test UP Linux guest hotplug with VT-d(pcie)
> PASS
> 49. Test SMP Linux guest hotplug with VT-d(pcie)
> PASS
> 50. Test UP WinXP guest hotplug with VT-d(pcie)
> PASS
> 51. Test SMP winXP guest hotplug with VT-d(pcie)
> PASS
> 52. Assign 2 NICs to one UP Linux Domain
> PASS
> 53. Assign 2 NICs to one SMP Linux Domain
> PASS
> 54. Scp a big file when NIC is assigned to the linux guest by VT-D
> PASS
> 55. Boot up one Nevada xenU guest with 256M memory
> PASS
> 56. Check if dom0 can enter S3 state
> PASS
> 57. Check if xen can get C-state residency data
> PASS
> 58. Check if xen can get C-state trigger available
> PASS
> 59. Check if xen can get P-state residency data
> PASS
> 60. Check if xen can get P-state trigger available
> PASS
>
> Summary Test Report of Last Session
> =====================================================================
> Total Pass Fail NoResult Crash
> =====================================================================
> vtd 16 16 0 0 0
> device_model 2 2 0 0 0
> control_panel 15 11 4 0 0
> acpi 4 4 0 0 0
> gtest 23 23 0 0 0
> =====================================================================
> vtd 16 16 0 0 0
> :hp_pcie_up_PAE_gPAE 1 1 0 0 0
> :hp_pcie_up_xp_PAE_gPAE 1 1 0 0 0
> :two_dev_scp_nomsi_PAE_g 1 1 0 0 0
> :hp_pci_up_xp_PAE_gPAE 1 1 0 0 0
> :two_dev_up_xp_nomsi_PAE 1 1 0 0 0
> :two_dev_smp_xp_nomsi_PA 1 1 0 0 0
> :hp_pci_smp_xp_PAE_gPAE 1 1 0 0 0
> :two_dev_smp_PAE_gPAE 1 1 0 0 0
> :two_dev_up_nomsi_PAE_gP 1 1 0 0 0
> :two_dev_scp_PAE_gPAE 1 1 0 0 0
> :hp_pcie_smp_xp_PAE_gPAE 1 1 0 0 0
> :hp_pcie_smp_PAE_gPAE 1 1 0 0 0
> :two_dev_up_PAE_gPAE 1 1 0 0 0
> :two_dev_smp_nomsi_PAE_g 1 1 0 0 0
> :hp_pci_up_PAE_gPAE 1 1 0 0 0
> :hp_pci_smp_PAE_gPAE 1 1 0 0 0
> device_model 2 2 0 0 0
> :pv_on_up_PAE_gPAE 1 1 0 0 0
> :pv_on_smp_PAE_gPAE 1 1 0 0 0
> control_panel 15 11 4 0 0
> :XEN_4G_guest_PAE_gPAE 1 1 0 0 0
> :XEN_four_vmx_xenu_seq_P 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_SMP_PAE_gPAE 1 0 1 0 0
> :XEN_Nevada_xenu_PAE_gPA 1 1 0 0 0
> :XEN_LM_SMP_PAE_gPAE 1 0 1 0 0
> :XEN_SR_Continuity_PAE_g 1 0 1 0 0
> :XEN_vmx_vcpu_pin_PAE_gP 1 1 0 0 0
> :XEN_two_winxp_PAE_gPAE 1 1 0 0 0
> :XEN_LM_Continuity_PAE_g 1 0 1 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
> acpi 4 4 0 0 0
> :check_p_residency_PAE_g 1 1 0 0 0
> :check_c_trigger_PAE_gPA 1 1 0 0 0
> :check_p_trigger_PAE_gPA 1 1 0 0 0
> :check_c_residency_PAE_g 1 1 0 0 0
> gtest 23 23 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 1 0 0 0
> :boot_up_vista_PAE_gPAE 1 1 0 0 0
> :boot_fc9_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_nevada_PAE_gPAE 1 1 0 0 0
> :boot_indiana_PAE_gPAE 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_win2008_PAE_gPA 1 1 0 0 0
> :boot_up_noacpi_xp_PAE_g 1 1 0 0 0
> :boot_smp_win2008_PAE_gP 1 1 0 0 0
> :reboot_fc6_PAE_gPAE 1 1 0 0 0
> :kb_nightly_PAE_gPAE 1 1 0 0 0
> =====================================================================
> Total 60 56 4 0 0
>
> =====================================================================
> Platform : 32E
> Service OS: Red Hat Enterprise Server Release 5 (Tikanga)
> Hardware : Clovertown
> Xen package: 18711
> Date: Fri Oct 24 16:00:00
>
> 1. One PAE SMP Linux VMX domain with 256M memory
> PASS
> 2. One PAE SMP Linux VMX domain with 1500M memory
> PASS
> 3. One PAE SMP Linux VMX domain with 4G memory
> PASS
> 4. Create 4 same PAE Linux VMX domain one by one
> PASS
> 5. One xenU guest with 256M memory
> PASS
> 6. One 32E SMP Linux VMX domain with 256M memory
> PASS
> 7. One 32E SMP Linux VMX domain with 1500M memory
> PASS
> 8. One 32E SMP Linux VMX domain with 4G memory
> PASS
> 9. Create 4 diffierent Linux VMX domain per processor at the
> sametime PASS
> 10. Create 4 same Linux VMX domain one by one
> PASS
> 11. Create 2 winXP VMX per processor at the same time
> PASS
> 12. Create one winXP,one linux VMX per processor at the same time
> PASS
> 13. Create 4VM(2VMX and 2 xenU) per processor one by one
> PASS
> 14. Create one VMX who has 2 vcpu
> PASS
> 15. Test a single domain with single vcpu bind a cpu
> PASS
> 16. Control panel HVM save/restore process continuity test
> FAIL
> 17. Cpu number test after save/restore
> FAIL
> 18. Control panel HVM live/migration process continuity test
> FAIL
> 19. Cpu number test after live/migration
> FAIL
> 20. VBD & VNIF works on an UP VMX domain PASS
> PASS
> 21. VBD & VNIF works on a SMP VMX domain
> PASS
> 22. Boot up 2.6.23-rc4 Linux kernel guest
> PASS
> 23. subset LTP test
> PASS
> 24. Testing for build base kernel in UP_VMX domain
> PASS
> 25. Boot up win Vista VMX guest
> PASS
> 26. Boot up win 2008 VMX guest
> PASS
> 27. Boot up UP_Non_ACPI win2k VMX guest
> PASS
> 28. Boot up UP_ACPI IA32 win2k3 VMX guest
> PASS
> 29. Boot up UP_ACPI XPSP2 VMX guest
> PASS
> 30. Boot up UP_ACPI win2k VMX guest
> PASS
> 31. Boot up VMX with acpi=1,vcpu=1
> PASS
> 32. VMX winXP reboot
> PASS
> 33. VMX fedora6 reboot
> PASS
> 34. Boot up rhel5u1 VMX guest with timer_mode=1
> PASS
> 35. Boot up fodora9 VMX guest with timer_mode=1
> PASS
> 36. Boot up ACPI_SMP win2k VMX guest
> PASS
> 37. Boot up ACPI_SMP IA32 win2k3 VMX guest
> PASS
> 38. Boot up ACPI_SMP winXP SP2 VMX guest
> PASS
> 39. Boot up SMP win Vista VMX guest
> PASS
> 40. Boot up SMP win2k8 VMX guest
> PASS
> 41. Boot up Nevada VMX guest
> PASS
> 42. Boot up Indiana VMX guest
> PASS
> 43. Assign two NICs to one UP linux domain(nomsi)
> PASS
> 44. Assign two NICs to one SMP linux domain(nimsi)
> PASS
> 45. Assign two NICs to one UP winXP domain(nomsi)
> PASS
> 46. Assign two NICs to one SMP winXP domain(nomsi)
> PASS
> 47. Scp a big file when nic is assigned to the linux guest by
> vt-d(nomsi) PASS
> 48. Test UP Linux guest hotplug with VT-d(pci)
> PASS
> 49. Test SMP Linux guest hotplug with VT-d(pci)
> PASS
> 50. Test UP WinXP guest hotplug with VT-d(pci)
> PASS
> 51. Test SMP winXP guest hotplug with VT-d.(pci)
> PASS
> 52. Test UP Linux guest hotplug with VT-d(pice)
> PASS
> 53. Test SMP Linux guest hotplug with VT-d(pcie)
> PASS
> 54. Test UP WinXP guest hotplug with VT-d(pcie)
> PASS
> 55. Test SMP winXP guest hotplug with VT-d. (pcie)
> PASS
> 56. Assign two NICs to one UP linux domain
> PASS
> 57. Assign two NICs to one SMP linux domain
> PASS
> 58. Scp a big file when NIC is assigned to linux guest by vt-d
> PASS
> 59. Boot up one Nevada XenU guest with 256M memory
> PASS
> 60. Check if xen can get C-state residency data
> PASS
> 61. Check if xen can get C-state trigger available
> PASS
> 62. Check if xen can get P-state residency data
> PASS
> 63. Check if xen can get P-state trigger available
> PASS
> 64. Check entering S3 case
> PASS
>
> ===========================================================================================
> Summary Test Report of Last Session
> =====================================================================
> Total Pass Fail NoResult Crash
> =====================================================================
> vtd 16 16 0 0 0
> device_model 2 2 0 0 0
> control_panel 20 16 4 0 0
> acpi 5 5 0 0 0
> gtest 21 21 0 0 0
> =====================================================================
> vtd 16 16 0 0 0
> :two_dev_up_xp_nomsi_64_ 1 1 0 0 0
> :hp_pcie_smp_xp_64_g32e 1 1 0 0 0
> :two_dev_smp_nomsi_64_g3 1 1 0 0 0
> :two_dev_scp_64_g32e 1 1 0 0 0
> :hp_pcie_up_xp_64_g32e 1 1 0 0 0
> :two_dev_up_64_g32e 1 1 0 0 0
> :hp_pci_up_64_g32e 1 1 0 0 0
> :two_dev_up_nomsi_64_g32 1 1 0 0 0
> :two_dev_smp_64_g32e 1 1 0 0 0
> :two_dev_smp_xp_nomsi_64 1 1 0 0 0
> :two_dev_scp_nomsi_64_g3 1 1 0 0 0
> :hp_pci_smp_xp_64_g32e 1 1 0 0 0
> :hp_pci_smp_64_g32e 1 1 0 0 0
> :hp_pci_up_xp_64_g32e 1 1 0 0 0
> :hp_pcie_smp_64_g32e 1 1 0 0 0
> :hp_pcie_up_64_g32e 1 1 0 0 0
> device_model 2 2 0 0 0
> :pv_on_up_64_g32e 1 1 0 0 0
> :pv_on_smp_64_g32e 1 1 0 0 0
> control_panel 20 16 4 0 0
> :XEN_1500M_guest_64_g32e 1 1 0 0 0
> :XEN_4G_guest_64_g32e 1 1 0 0 0
> :XEN_LM_Continuity_64_g3 1 0 1 0 0
> :XEN_256M_xenu_64_gPAE 1 1 0 0 0
> :XEN_four_vmx_xenu_seq_6 1 1 0 0 0
> :XEN_vmx_vcpu_pin_64_g32 1 1 0 0 0
> :XEN_SR_Continuity_64_g3 1 0 1 0 0
> :XEN_linux_win_64_g32e 1 1 0 0 0
> :XEN_vmx_2vcpu_64_g32e 1 1 0 0 0
> :XEN_four_dguest_co_64_g 1 1 0 0 0
> :XEN_1500M_guest_64_gPAE 1 1 0 0 0
> :XEN_two_winxp_64_g32e 1 1 0 0 0
> :XEN_4G_guest_64_gPAE 1 1 0 0 0
> :XEN_four_sguest_seq_64_ 1 1 0 0 0
> :XEN_256M_guest_64_gPAE 1 1 0 0 0
> :XEN_LM_SMP_64_g32e 1 0 1 0 0
> :XEN_Nevada_xenu_64_g32e 1 1 0 0 0
> :XEN_256M_guest_64_g32e 1 1 0 0 0
> :XEN_SR_SMP_64_g32e 1 0 1 0 0
> :XEN_four_sguest_seq_64_ 1 1 0 0 0
> acpi 5 5 0 0 0
> :check_c_residency_64_g3 1 1 0 0 0
> :check_p_residency_64_g3 1 1 0 0 0
> :check_c_trigger_64_g32e 1 1 0 0 0
> :Dom0_S3_64_g32e 1 1 0 0 0
> :check_p_trigger_64_g32e 1 1 0 0 0
> gtest 21 21 0 0 0
> :boot_up_acpi_win2k_64_g 1 1 0 0 0
> :boot_up_noacpi_win2k_64 1 1 0 0 0
> :reboot_xp_64_g32e 1 1 0 0 0
> :boot_up_vista_64_g32e 1 1 0 0 0
> :boot_indiana_64_g32e 1 1 0 0 0
> :boot_up_acpi_xp_64_g32e 1 1 0 0 0
> :boot_smp_acpi_xp_64_g32 1 1 0 0 0
> :boot_up_acpi_64_g32e 1 1 0 0 0
> :boot_base_kernel_64_g32 1 1 0 0 0
> :boot_up_win2008_64_g32e 1 1 0 0 0
> :kb_nightly_64_g32e 1 1 0 0 0
> :boot_up_acpi_win2k3_64_ 1 1 0 0 0
> :boot_nevada_64_g32e 1 1 0 0 0
> :boot_smp_vista_64_g32e 1 1 0 0 0
> :ltp_nightly_64_g32e 1 1 0 0 0
> :boot_fc9_64_g32e 1 1 0 0 0
> :boot_smp_win2008_64_g32 1 1 0 0 0
> :boot_smp_acpi_win2k3_64 1 1 0 0 0
> :boot_rhel5u1_64_g32e 1 1 0 0 0
> :reboot_fc6_64_g32e 1 1 0 0 0
> :boot_smp_acpi_win2k_64_ 1 1 0 0 0
> =====================================================================
> Total 64 60 4 0 0
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-devel] FW: Weekly VMX status report. Xen: #18711 & Xen0: #711,
Li, Haicheng <=
|
|
|
| |
|
Home