This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>, "Steven Hand" <Steven.Hand@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] support HVM guests with more than 3.75G memory
From: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Date: Sat, 2 Sep 2006 16:09:47 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 02 Sep 2006 01:10:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbEc4rTIP6JcWimSKqrdIDVmJs4CgAjDWLgAlnNn0A=
Thread-topic: [Xen-devel] [PATCH] support HVM guests with more than 3.75G memory
>>Interesting - the crash is in the [optional] 'guess_wrmap' function
>>which is trying to fast path the lookup of a particular va.  Can you 
>>try temporarily disabling this optimization and retrying? Just edit 
>>xen/include/asm-x86/shadow2.c to replace 
>>#define SHADOW2_OPTIMZATIONS 0x03 
>>#define SHADOW2_OPTIMZATIONS 0x02 
>Your suggestion works for me, and windows 2003 server can boot with 5G
>memory on 64bit xen.
>But after I played with it for some time, qemu dm window disappeared,
>and xen console reported:
>(XEN) sh2 error: sh2_remove_shadows(): can't find all shadows of mfn
>1b2ddd (shadow2_flags=00000100)
>(XEN) domain_crash called from shadow2-common.c:2251
>(XEN) Domain 8 (vcpu#0) crashed on cpu#3:
>(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
>(XEN) CPU:    3
>(XEN) RIP:    0008:[<0000000080862ca2>]
>(XEN) RFLAGS: 0000000000010256   CONTEXT: hvm
>(XEN) rax: 0000000067e97001   rbx: 0000000000000000   rcx:
>(XEN) rdx: 00000000ba482b68   rsi: 0000000000000000   rdi:
>(XEN) rbp: 00000000ba482b94   rsp: 00000000ba482b54   r8:
>(XEN) r9:  0000000000000000   r10: 0000000000000000   r11:
>(XEN) r12: 0000000000000000   r13: 0000000000000000   r14:
>(XEN) r15: 0000000000000000   cr0: 0000000080010031   cr3:
>(XEN) ds: 0023   es: 0023   fs: 0030   gs: 0000   ss: 0010   cs: 0008
>(XEN) sh2_update_paging_modes: postponing determination of shadow2 mode
>(XEN) vmx_do_launch(): GUEST_CR3<=001a17a0, HOST_CR3<=222b8b000

Hi Steven, I still saw this bug, I think it should be fixed for xen

>With less than 4G RAM, I didn't see this error.
>Xen-devel mailing list

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>