To reproduce the issue, we can simply run these cases in LTP for 10 times. The
failure will definitely occur. And the "xm dmesg" shows that:
(XEN) sh2_update_paging_modes: postponing determination of shadow2 mode
(XEN) vmx_do_launch(): GUEST_CR3<=ae69e000, HOST_CR3<=af51b000
(XEN) (GUEST: 8) HVM Loader
(XEN) (GUEST: 8) Detected Xen v3.0-unstable
(XEN) (GUEST: 8) Loading ROMBIOS ...
(XEN) (GUEST: 8) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 8) Writing SMBIOS tables ...
(XEN) (GUEST: 8) Loading VMXAssist ...
(XEN) (GUEST: 8) VMX go ...
(XEN) (GUEST: 8) VMXAssist (Aug 22 2006)
(XEN) (GUEST: 8) Memory size 512 MB
(XEN) (GUEST: 8) E820 map:
(XEN) (GUEST: 8) 0000000000000000 - 000000000009F000 (RAM)
(XEN) (GUEST: 8) 000000000009F000 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 8) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 8) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 8) 0000000000100000 - 000000001FFF0000 (RAM)
(XEN) (GUEST: 8) 000000001FFF0000 - 000000001FFFA000 (ACPI Data)
(XEN) (GUEST: 8) 000000001FFFA000 - 000000001FFFD000 (ACPI NVS)
(XEN) (GUEST: 8) 000000001FFFD000 - 000000001FFFE000 (Type 19)
(XEN) (GUEST: 8) 000000001FFFE000 - 000000001FFFF000 (Type 18)
(XEN) (GUEST: 8) 000000001FFFF000 - 0000000020000000 (Type 17)
(XEN) (GUEST: 8) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 8)
(XEN) (GUEST: 8) Start BIOS ...
(XEN) (GUEST: 8) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 8) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 8) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 8) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 8) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp
$
(XEN) (GUEST: 8) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07
15:55:26 $
(XEN) (GUEST: 8)
(XEN) (GUEST: 8) ata0-0: PCHS=10240/16/63 translation=none LCHS=1024/16/63
(XEN) (GUEST: 8) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (5040 MBytes)
(XEN) (GUEST: 8) ata0 slave: Unknown device
(XEN) (GUEST: 8) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 8) ata1 slave: Unknown device
(XEN) (GUEST: 8)
(XEN) (GUEST: 8) Booting from Hard Disk...
(XEN) (GUEST: 8) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 8) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 8) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 8) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 8) KBD: unsupported int 16h function 03
(XEN) (GUEST: 8) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 8) *** int 15h function AX=E980, BX=E6F5 not yet supported!
(XEN) (GUEST: 8) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 8) int13_harddisk: function 41, unmapped device for ELDL=81
Best Regards,
Jiajun
>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ian Pratt
>Sent: 2006年8月22日 22:05
>To: Zheng, Jeff; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-devel] VMX Status Report 11218:f681ffc9b01a
>
>> We have tested the latest xen on VT platform with Intel
>> 915/E8500 chipset.
>> Here is the test summary:
>>
>> Issues:
>>
>> IA32: 4 LTP math cases(float_bessel, float_exp_log, float_power and
>> float_trigo) sometime fail.
>
>OK -- this is very interesting. This is a possible manifestation of a
>shadow2 bug that we're trying to track down.
>
>Please could you post the output of 'xm dmesg'.
>
>Also, please could you try running these benchmarks individually and see
>if you can get a nice reliable repro case.
>
>Thanks,
>Ian
>
>> IA32: Kernel build in VMX may meet kernel panic
>> IA32PAE: Cannot bootup pae SMP VMX domain. We can bootup UP VMX domain
>> IA32E: "xen0+xenU" build fails, see attachment for
>> details. but can be
>> built by default (2.6.16-xen) configuration.
>> IA32E: We built with default build. 32/32e SMP VMX can startup. But
>> 32pae
>> SMP VMX cannot bootup either.
>>
>>
>> details:
>>
>> IA-32:
>>
>> + Build&Boot SMP xen0 without problem
>> + Can bootup unmodified IA-32 2.6 linux in SMP VMX domain Can bootup
>> + unmodified IA-32 WindowsXP SP1/SP2 in VMX domain Can bootup
>> SMP VMX &
>> + XenU with different memory size
>> (VMX:64MB,128MB,196MB,256MB,512MB.XenU:256MB)
>> + A selected subset of xm-test runs well A selected subset of
>> LTP runs
>> + well in SMP VMX domain(2.6) Can startX in Dom0 Can bootup IA-32 2.6
>> + linux in SMP VMX domain with acpi enable Can startX in VMX
>> Network is
>> + OK in VMX
>>
>> For details
>> ------------------------------------------------------------
>>
>> Platform: IA-32
>> Service OS: FC5, IA-32, SMP
>> Hardware: Grandstale
>> Default guest OS: IA-32-SMP, 2.6 kernel
>>
>> 1, one vmx with memory 512M PASS
>> 2, one xenU with memory 256M PASS
>> 3, 2 vmx and 2 xenU coexist PASS
>> 4, four vmx coexist(64M,128M,196M,256M) PASS
>> 5, network in VMX domain PASS
>> 6, network in XenU domain PASS
>> 7, one window domain PASS
>> 8, 1 xpsp1 and 1 xpsp2 windows domains coexist PASS
>> 9, XenU migration PASS
>> 10,subset LTP test in VMX domain PASS
>> 11,one vmx boot with base kernel(2.6.16) PASS
>> 12,xm-test PASS
>> 13,kernel build in smp guest FAIL
>> 14,StartX in Dom0 PASS
>> 15,one vmx with acpi enable PASS
>>
>> Xm test on ia32:
>> ====================================================
>> Xm-test execution summary:
>> PASS: 44
>> FAIL: 5
>> XPASS: 0
>> XFAIL: 3
>>
>>
>> Details:
>>
>> XFAIL: 02_network_local_ping_pos
>> ping loopback failed for size 65507. ping eth0 failed for size
>> 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
>>
>> XFAIL: 05_network_dom0_ping_pos
>> Ping to dom0 failed for size 1 48 64 512 1440 1500 1505 4096
>> 4192 32767 65507.
>>
>> XFAIL: 11_network_domU_ping_pos
>> Ping failed for size 1 48 64 512 1440 1500 1505 4096
>> 4192 32767 65507.
>>
>> FAIL: 01_reboot_basic_pos
>> [Errno 5] Input/output error
>>
>> FAIL: 01_sedf_multi_pos
>> [0] xm sedf returned invalid 256 != 0
>>
>> LTP test on ia32:
>> =======================================
>> Detail Test Report of Last Session
>> =====================================================================
>> The following testcases do Not pass:
>> Suite : Scenario TC No. TP No.
>> ltp:math 0 3 FAIL 23:16:50
>> Starting LTP math Test Case float_bessel
>> ltp:math 0 6 FAIL 23:17:38
>> Starting LTP math Test Case float_power
>> ltp:math 0 7 FAIL 23:17:54
>> Starting LTP math Test Case float_trigo
>> Summary Test Report of Last Session
>> Summary Test Report of Last Session
>> ==============================================================
>> ==========
>> ======
>> = Total Pass Fail NoResult Crash
>> ==============================================================
>> ==========
>> ======
>> =ltp 194 191 3 0 0
>> ==============================================================
>> ==========
>> ======
>> =ltp 194 191 3 0 0
>> mm 21 21 0 0 0
>> dio 28 28 0 0 0
>> nptl 1 1 0 0 0
>> math 10 7 3 0 0
>> ipc 8 8 0 0 0
>> pty 3 3 0 0 0
>> quickhit 120 120 0 0 0
>> sched 3 3 0 0 0
>> ==============================================================
>> ==========
>> ======
>> =Total 194 191 3 0 0
>>
>> The three failed ltp cases can pass if run them in separate
>> rather than in whole ltp test.
>>
>>
>>
>> Xm test on ia32pae:
>> ===========================================================
>> Xm-test execution summary:
>> PASS: 44
>> FAIL: 5
>> XPASS: 0
>> XFAIL: 3
>>
>>
>> Details:
>>
>> XFAIL: 02_network_local_ping_pos
>> ping loopback failed for size 65507. ping eth0 failed for size
>> 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
>>
>> XFAIL: 05_network_dom0_ping_pos
>> Ping to dom0 failed for size 1 48 64 512 1440 1500 1505 4096
>> 4192 32767 65507.
>>
>> XFAIL: 11_network_domU_ping_pos
>> Ping failed for size 1 48 64 512 1440 1500 1505 4096
>> 4192 32767 65507.
>>
>> FAIL: 01_reboot_basic_pos
>> [Errno 5] Input/output error
>>
>> FAIL: 01_sedf_multi_pos
>> [0] xm sedf returned invalid 256 != 0
>>
>>
>>
>> Best Regards
>> Larry
>>
>>
>>
>
>_______________________________________________
>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
|