|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [ANNOUNCE] Xen 3.1.2 first release candidate
Hi Keir,
We have tested Xen 3.1.2 on IA32pae, IA32e and IA64.
Except we didn't test PV drivers on 32 side, the other parts are all pass.
The detailed testing results.
---------------------------------------------
Platform : PAE
Service OS : Fedora Core release 5 (Bordeaux)
Hardware : paxville
Xen 3.1.1: 15487: aabd60597239
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
device_model 2 0 0 2 0
control_panel 12 12 0 0 0
Restart 1 1 0 0 0
gtest 14 14 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 12 0 0 0
:XEN_four_vmx_xenu_seq_P 1 1 0 0 0
:XEN_4G_guest_PAE_gPAE 1 1 0 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_256M_guest_PAE_gPAE 1 1 0 0 0
:XEN_1500M_guest_PAE_gPA 1 1 0 0 0
:XEN_two_winxp_PAE_gPAE 1 1 0 0 0
:XEN_vmx_4vcpu_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 14 14 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
:boot_up_vista_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_win2k3_PAE 1 1 0 0 0
:boot_base_kernel_PAE_gP 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_up_noacpi_win2k3_P 1 1 0 0 0
:boot_up_noacpi_xp_PAE_g 1 1 0 0 0
:kb_nightly_PAE_gPAE 1 1 0 0 0
=====================================================================
Total 29 27 0 2 0
Platform : x86_64
Service OS : Red Hat Enterprise Linux AS release 4 (Nahant Update 3)
Hardware : clovertown
Xen 3.1.1: 15487: aabd60597239
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
device_model 2 0 0 2 0
control_panel 17 17 0 0 0
Restart 2 2 0 0 0
gtest 13 13 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_vmx_4vcpu_64_g64 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_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 13 13 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:boot_smp_acpi_xp_64_g64 1 1 0 0 0
:bootx_64_g64 1 1 0 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_base_kernel_64_g64 1 1 0 0 0
:boot_up_acpi_win2k_64_g 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
:ltp_nightly_64_g64 1 1 0 0 0
:boot_up_acpi_64_g64 1 1 0 0 0
:kb_nightly_64_g64 1 1 0 0 0
=====================================================================
Total 34 32 0 2 0
Platform : IA64
Service OS : RHEL4u3 IA64 with 2 CPUs
Guest os: RHEL4u2/RHEL4u3 VTI
Hardware : Montecito C0/C1
PAL: 9.08
Guest firmware: Flash.fd.2007-4-11
Xen package: 3.1.2
xen0's sched: credit
Summary Test Report of Last Session
================================================
Case status case scene
device_model:pv pass
Win_PV pass
Two_UP_VTI_Co pass Create 2 UP_VTI domain (256M memory each)
One_UP_VTI pass Create 1 UP_VTI domain with 256M memory
One_UP_XenU pass Create 1 UP_xenU domain (256M memory)
SMPVTI_LTP pass Create 1 VTI (vcpus=2 mem=512M) to run LTP
SMPVTI_and_SMPXenU pass Create 1 VTI + 1 xenU with 256M memory
Two_SMPXenU_Coexist pass Create 2 xenU with 256M memory each
One_SMPVTI_4096M pass Create 1 VTI (vcpus=2, mem=4096M)
SMPVTI_Network pass Create a VTI (mem=256M) and ping hostname
SMPXenU_Network pass Create a xenU (vcpus=2) and ping hostname
One_SMP_XenU pass Create a smp xenU with vcpus=2
One_SMP_VTI pass Create a smp VTI with vcpus=2
SMPVTI_Kernel_Build pass Create a VTI domain (vcpus=4) and test KB
Four_SMPVTI_Coexist pass Create four VTI domains with 256M each
SMPVTI_Windows pass Create SMPVTI windows
SMPWin_SMPVTI_SMPxenU_Co pass Create VTI, xenU and VTI_Windows
UPVTI_Kernel_Build pass Create UPVTI and test kernel build in it
Best Regards,
Yongkang You
>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
>Sent: Wednesday, October 24, 2007 2:56 AM
>To: xen-devel
>Subject: [Xen-devel] [ANNOUNCE] Xen 3.1.2 first release candidate
>
>Folks,
>
>Following the big 3.1.1 release we have gathered together a
>number of minor
>fixes and now seems a good time to roll out 3.1.2. This is a
>much smaller
>release (in terms of amount of code added or modified) than
>3.1.1, so I hope
>that this will be the only release candidate that we require.
>However I do
>want to make sure that this release works properly in
>configurations that we
>do not cover in our automatic tests. So, please test and ack
>this release
>candidate!
>
> -- Keir
>
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|