Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew issue

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

That means I broke memory allocation when I cleaned up the tools side of
that patch. I will look into it and fix it.

 -- Keir

On 23/5/08 09:06, "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx> wrote:

> Hi, Keir, 
>     This issue is caused by the 2MB superpage patch in Xen C/S 17645. It seems
> that any linux guest (hap=0, using shadow) with more than 4G memory will fail
> to boot (4095M memory can boot successful). I haven't tried EPT guest.
> 
> -- Dongxiao
> 
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
> Sent: 2008年5月23日 15:54
> To: Li, Haicheng; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew
> issue
> 
> On 23/5/08 07:12, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:
> 
>> Old issues:
>> ==============================================
>> 1. linux guest kernel panic when booting up with 4G memory.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255
> 
> Can you provide more info on this one? Linux version, configuration, etc?
> And/or send me the vmlinux/bzImage files privately to try to repro.
> 
>  -- Keir
> 
> 
> 
> _______________________________________________
> 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