RE: [Xen-devel] [PATCH] support HVM guests with more than 3.75G memory

["Li, Xin B" <xin.b.li@xxxxxxxxx>]

>So our HVM e820 table should also comply to this, and the 256M RAM that
>falls into that range should be moved to 4G above, that's the "real
>changes" in my patch.

Thanks, I saw it's checked in as changeset 11186.

But it can not work with shadow2, when I assigned 4096M memory, I got:

(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    3
(XEN) RIP:    e010:[<ffff83000013c267>]
sh2_guess_wrmap__shadow_3_guest_3+0x67/0xd0
(XEN) RFLAGS: 0000000000010202   CONTEXT: hypervisor
(XEN) rax: ffff8140c0000000   rbx: 00000000001aed0d   rcx:
00000000e8000001
(XEN) rdx: 0000000000000aa2   rsi: 000000015448d000   rdi:
ffff8300001a0080
(XEN) rbp: ffff8300001a0080   rsp: ffff83000023fc98   r8:
00000000001aed0d
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11:
0000000000000000
(XEN) r12: ffff828404350a08   r13: 0000000000000001   r14:
00000000c0881008
(XEN) r15: 0000000004350a08   cr0: 000000008005003b   cr3:
0000000080b7f000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e010
(XEN) Xen stack trace from rsp=ffff83000023fc98:
(XEN)    0000000000000000 ffff830000134533 00000001aed0d663
0000000000000000
(XEN)    ffff8300001a0080 ffff8300001ad080 00000000c0881008
0000000000000000
(XEN)    0000000000000000 ffff83000013f60b ffff83000023ff28
00000000c0881008
(XEN)    ffff818000603020 0000000000000003 00000000002234f3
0000000000223444
(XEN)    0000000000001e00 ffff8300001ad080 00000001001ad080
0000000080000000
(XEN)    0000000000000000 0000000080000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 00000000ba63eb40
00000000c05d3740
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000001000
0000000000000000
(XEN)    00000000c05d3748 000000f000000002 0000000000100000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 ffff8300001a0080 00000000001531de
ffff83000013cdff
(XEN)    00000000c0881008 ffff8301531de178 ffff8301aec8e020
0000000000000000
(XEN)    0000000000000000 00000000001531de 00000000001aec8e
00000000001aed0d
(XEN)    ffff8300001d7744 ffff83000015bd60 ffff830000000004
ffff8300001a0080
(XEN)    00000001aed0d067 0000000000003000 ffff83000011d1d4
ffff83000023ff28
(XEN)    ffff8300001906c0 ffff8300001a0080 00000000c0881008
0000000000000000
(XEN)    0000000000000000 ffff83000015d003 ffff8300001baf80
0000000000000000
(XEN)    ffff8300001a0080 ffff830000156e38 ffff830000115545
ffff8300001ad080
(XEN)    0000000000000000 00000000ba63eb48 0000000000000000
0000000000000000
(XEN) Xen call trace:
(XEN)    [<ffff83000013c267>]
sh2_guess_wrmap__shadow_3_guest_3+0x67/0xd0
(XEN)    [<ffff830000134533>] shadow2_remove_write_access+0x173/0x2f0
(XEN)    [<ffff83000013f60b>]
sh2_page_fault__shadow_3_guest_3+0x33b/0x10c0
(XEN)    [<ffff83000013cdff>]
sh2_update_cr3__shadow_3_guest_3+0x39f/0x4a0
(XEN)    [<ffff83000015bd60>] vmx_cr_access+0x680/0xfa0
(XEN)    [<ffff83000011d1d4>] context_switch+0x624/0x640
(XEN)    [<ffff83000015d003>] vmx_vmexit_handler+0x4b3/0xe20
(XEN)    [<ffff830000156e38>] vmx_intr_assist+0xf8/0x400
(XEN)    [<ffff830000115545>] do_softirq+0x55/0x70
(XEN)    [<ffff83000015d995>] vmx_asm_vmexit_handler+0x25/0x30
(XEN)    
(XEN) Pagetable walk from ffff8140c0005510:
(XEN)  L4[0x102] = 0000000080b7f063 000000000000011b
(XEN)   L3[0x103] = 0000000080b7f063 000000000000011b
(XEN)    L2[0x0] = 0000000080b7e063 000000000000011c 
(XEN)     L1[0x5] = 0000000000000000 ffffffffffffffff
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 3:
(XEN) CPU3 FATAL PAGE FAULT
(XEN) [error_code=0000]

I'm not familiar with new shadow yet, can anyone help to take a look?
-Xin

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