Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Summary Test Report of Last Session ===================================================================== Total Pass Fail NoResult Crash ===================================================================== nightly 1 1 0 0 0 control_panel 29 1 0 0 28 ===================================================================== nightly 1 1 0 0 0 :subset_LTP 0 0 0 0 0 :dom0x11 1 1 0 0 0 control_panel 29 1 0 0 28 :ia32e_vistartm 1 0 0 0 1 :acpi_nightly 1 0 0 0 1 :ia32up_acpi_win2k3 1 0 0 0 1 :ia32up_two_noacpi_ 1 0 0 0 1 :fourG_2linux 1 0 0 0 1 :ia32_smp_win2k3 1 0 0 0 1 :ia32_smp_winxp 1 0 0 0 1 :ia32up_noacpi_win 1 0 0 0 1 :fourG_linuxwindows 1 0 0 0 1 :four_vmx_seq 1 0 0 0 1 :ia32up_acpi_winxp 1 0 0 0 1 :ia32e_smp_winxp 1 0 0 0 1 :ia32e_up_win2k3 1 0 0 0 1 :ia32_guest_256M 1 0 0 0 1 :one_VMX 1 0 0 0 1 :base_kernel 1 0 0 0 1 :ia32e_up_winxp 1 0 0 0 1 :ia32_vistartm 1 0 0 0 1 :ia32pae_VMX_1500M 1 0 0 0 1 :fourG_paelinux 1 0 0 0 1 :ia32e_smp_win2k3 1 0 0 0 1 :fourG_linux 1 0 0 0 1 :one_XENU 1 1 0 0 0 :fourG_windows 1 0 0 0 1 :ia32_smp_vista 1 0 0 0 1 :two_xenu_vmx_seq 1 0 0 0 1 :guestx11 1 0 0 0 1 :ia32up_acpi_win2k 1 0 0 0 1 :ia32e_smp_vista 1 0 0 0 1 ===================================================================== Total 30 2 0 0 28 ===================================================================== Case ID Based Summary Test Report of Last Session ===================================================================== Total Pass Fail NoResult Crash ===================================================================== Non_CaseID 30 2 0 0 28 ===================================================================== Total 30 2 0 0 28 Detail Test Report of Last Session Failed Cases ===================================================================== The following testcases do Not pass: Suite : Scenario TC No. IC No. control_panel:ia32e_vistartm 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:acpi_nightly 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_acpi_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_two_noacpi_win 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_2linux 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_smp_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_smp_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_noacpi_win 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_linuxwindows 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:four_vmx_seq 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_acpi_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_smp_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_up_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_guest_256M 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:one_VMX 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:base_kernel 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_up_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_vistartm 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32pae_VMX_1500M 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_paelinux 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_smp_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_linux 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_windows 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:ia32_smp_vista 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:two_xenu_vmx_seq 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:guestx11 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:ia32up_acpi_win2k 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:ia32e_smp_vista 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... Detail Test Report of Last Session ===================================================================== Detailed test cases info: Suite : Scenario TC No. IC No. nightly:dom0x11 0 31 PASS 11:00:50 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: control_panel:ia32e_vistartm 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:acpi_nightly 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_acpi_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_two_noacpi_win 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_2linux 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_smp_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_smp_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_noacpi_win 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_linuxwindows 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:four_vmx_seq 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32up_acpi_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_smp_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_up_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_guest_256M 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:one_VMX 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:base_kernel 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_up_winxp 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32_vistartm 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32pae_VMX_1500M 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_paelinux 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:ia32e_smp_win2k3 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:fourG_linux 0 31 CRASH 11:00:49 Fri Mar 9 11:00:49 CST 2007 Check whether dom0's X is started X is sucessfully started Fri Mar 9 11:00:50 CST 2007 tet result: Inside cleanup... control_panel:one_XENU 0 1 PASS 06:06:37 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: control_panel:fourG_windows 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:ia32_smp_vista 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:two_xenu_vmx_seq 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:guestx11 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:ia32up_acpi_win2k 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup... control_panel:ia32e_smp_vista 0 1 CRASH 06:05:34 Linux vt-dp6 2.6.18-xen #1 SMP Fri Mar 9 02:22:46 CST 2007 x86_64 x86_64 x86_64 GNU/Linux xen-hg_xen_unstable_r14287_20070309-1 Service OS is Red Hat Enterprise Linux AS release 4 (Nahant Update 3) Service OS has 4 CPUs Fri Mar 9 06:05:34 CST 2007 Testing for Startup a XENU domain XVS uses Test_NetUp_Domain to start domain Creating utp1_1173391534 with memory 256... VMX tp1 is up in 21 sec(s) MAC 00:16:3e:35:94:b4 gets IP address 192.168.88.82, and ping is OK Destroy utp1_1173391534 OK Fri Mar 9 06:06:37 CST 2007 tet result: Inside cleanup...