RE: [Xen-devel] Test report for Xen-3.3.0-rc4 (#18314)

["Xu, Jiajun" <jiajun.xu@xxxxxxxxx>]

On Wednesday, August 13, 2008 4:31 PM
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote:

> Do the new P1s still occur if you change SHADOW_OPTIMIZATIONS in
> arch/x86/mm/shadow/private.h to 0xff? (i.e., disable out-of-sync
> optimisation). 

After change SHADOW_OPTIMIZATIONS to 0xff, the two issues disappear.

But we found two phenomena:
1. Indiana HVM may reboot when loading grub, serial grub shows:
(XEN) sh error: sh_remove_shadows(): can't find all shadows of mfn
1e4490 (shadow_flags=00000040)
(XEN) domain_crash called from common.c:2714
(XEN) Domain 10 (vcpu#0) crashed on cpu#4:
(XEN) ----[ Xen-3.3.0-rc1  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    4
(XEN) EIP:    0158:[<fa58e185>]
(XEN) EFLAGS: 00000282   CONTEXT: hvm
(XEN) eax: 0000000c   ebx: 00000007   ecx: d947eba0   edx: 00000000
(XEN) esi: d947e7a0   edi: fa5886c0   ebp: d947e768   esp: d947e748
(XEN) cr0: 8005003b   cr4: 000006b8   cr3: 023cb020   cr2: d32daea5
(XEN) ds: 0160   es: 0160   fs: 0000   gs: 01b0   ss: 0160   cs: 0158
(XEN) sh error: sh_remove_shadows(): can't find all shadows of mfn
1e45de (shadow_flags=00000080)
(XEN) domain_crash called from common.c:2714

2. "xm destroy" Indiana HVM may cause xen call trace. But there is no
xen crash.
(XEN) Xen WARN at domain.c:1814
(XEN) ----[ Xen-3.3.0-rc1  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    2
(XEN) EIP:    e008:[<ff12f70f>] domain_relinquish_resources+0x17f/0x1a0
(XEN) EFLAGS: 00210202   CONTEXT: hypervisor
(XEN) eax: 00000001   ebx: ff1c2090   ecx: ff1c2080   edx: 00000000
(XEN) esi: ff1c2080   edi: ff1c2080   ebp: ffbf7e44   esp: ffbf7dcc
(XEN) cr0: 8005003b   cr4: 000026f0   cr3: 00bdcc80   cr2: 080554c8
(XEN) ds: e010   es: e010   fs: 0000   gs: 0033   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ffbf7dcc:
(XEN)    00000020 ff1c2080 fffffff5 fffffff3 ff1c2080 00000000 ffbf7e44
ff10416d
(XEN)    ff1c2080 00000005 ff116a57 2709497e 0000012f 513c6fff 00000202
000000ff
(XEN)    fffffff3 b33fc518 0000007b ff1030ad ff1c2080 b33fc518 00000090
00000020
(XEN)    ff1d9100 00000296 8d654ad1 ff1c2080 ff1d0080 ff1c2326 00000002
00000005
(XEN)    b79a000b b79d04fc b79d952c 447c7f77 b33fc54c 46257b48 b7f116a0
0000007f
(XEN)    00000000 b8b08ac8 081215a8 447c7f77 b7f116a0 b7b59d74 b33fc578
447c77d3
(XEN)    b7b59d74 a5dba1ee b7ba8140 0000001f a5dba1ee 00000000 0836e4f0
448738e4
(XEN)    b7ba8140 08399b54 b33fc5a8 447c77d3 08399b54 b7ba8140 a5dba1ee
448738e4
(XEN)    b7ba8140 b7ba8140 43841a1c ff1d9100 00200296 00200296 43841a15
00000006
(XEN)    00000003 00000004 ffbf7fb4 ffbf7f5c ff149cfd ffbf7fb4 43841a16
00000001
(XEN)    0000f800 ff111284 ff1dd044 ffbe6900 ff1dd104 000f0003 0000000f
ff1fa43c
(XEN)    000002e0 00000002 ffbdc080 ffbdc080 00200296 00200296 00000004
00000033
(XEN)    00009695 0000012f 00000004 43841a17 5a2f1fe8 909090ff 90909090
c3900390
(XEN)    f95f30d8 ff10f4d2 ff1dd044 53d22d15 0000012f ffbf7f03 5328e111
ffbdc080
(XEN)    0000007b 0000007b 00305000 ff19a7a4 b33fc518 357f4700 b7f49430
b33fc5e8
(XEN)    00000000 00305000 b33fc518 357f4700 b7f49430 b33fc5e8 00000000
00305000
(XEN)    00000024 000d0000 c0101487 00000061 00200282 ca1ebe94 00000069
0000007b
(XEN)    0000007b 00000000 00000033 00000002 ffbdc080
(XEN) Xen call trace:
(XEN)    [<ff12f70f>] domain_relinquish_resources+0x17f/0x1a0
(XEN)    [<ff1c2080>] get_edd+0x4/0x10
(XEN)    [<ff1c2080>] get_edd+0x4/0x10
(XEN)    [<ff10416d>] domain_kill+0x6d/0x160
(XEN)    [<ff1c2080>] get_edd+0x4/0x10
(XEN)    [<ff116a57>] add_entry+0x57/0x140
(XEN)    [<ff1030ad>] do_domctl+0x10d/0xc40
(XEN)    [<ff1c2080>] get_edd+0x4/0x10
(XEN)    [<ff1c2080>] get_edd+0x4/0x10
(XEN)    [<ff1d0080>] smp_prepare_cpus+0x2d0/0x800
(XEN)    [<ff1c2326>] boot_edd_info+0x170/0x200
(XEN)    [<ff149cfd>] do_general_protection+0x42d/0x1310
(XEN)    [<ff111284>] csched_tick+0x154/0x5e0
(XEN)    [<ff10f4d2>] page_scrub_softirq+0x132/0x160
(XEN)    [<ff19a7a4>] hypercall+0x94/0x9b

> 
> On 13/8/08 08:43, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:
> 
>> All,
>> 
>> We've finished a round of nightly testing and bug verification on RC4
>> (#18314). There are still 5 P1 open bugs. Bug #1322 and bug #1323
>> were found by extended testing with Solaris HVM guest.
>> 
>> New P1 bugs:
>> ==============================================
>> 1. Xen HV crashes while booting up Indiana HVM guest
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1322
>> 
>> 2. Booting Nevada 81 PAE HVM may cause Xen crash.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1323
>> 
>> Old P1 bugs:
>> ==============================================
>> 1. One 32e, hotplug attaching VT-d NIC to guest failed.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1316.
>> 
>> 2. On PAE, failed to hotplug attach USB EHCI device to linux guest.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1318
>> 
>> 3. UHCI hotplug can not work on Montevina platform.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1319
>> 
>> 
>> 
>> -- haicheng
>> 
>> _______________________________________________
>> 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



Best Regards
Jiajun

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel