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>
Subject: Re: [Xen-devel] [PATCH] support HVM guests with more than 3.75G memory
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Sun, 20 Aug 2006 17:13:10 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Steven.Hand@xxxxxxxxxxxx
Delivery-date: Sun, 20 Aug 2006 09:13:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Message from "Li, Xin B" <xin.b.li@xxxxxxxxx> of "Sun, 20 Aug 2006 22:20:45 +0800." <0EBFB99D260C5B40AC33E0F807B1AD66DA2C5C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
>>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>]
>(XEN) RFLAGS: 0000000000010202   CONTEXT: hypervisor
>(XEN) rax: ffff8140c0000000   rbx: 00000000001aed0d   rcx:
>(XEN) rdx: 0000000000000aa2   rsi: 000000015448d000   rdi:
>(XEN) rbp: ffff8300001a0080   rsp: ffff83000023fc98   r8:
>(XEN) r9:  0000000000000000   r10: 0000000000000000   r11:
>(XEN) r12: ffff828404350a08   r13: 0000000000000001   r14:
>(XEN) r15: 0000000004350a08   cr0: 000000008005003b   cr3:
>(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e010

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 




and recompile. 

It'd also be good to see if you can reproduce the above error on a 
guest with < 4G memory. 

I'll try to take a more detailed look myself when I get a test box 
sorted out. 



Xen-devel mailing list