Re: [Xen-devel] 2.6.27-rc1 >4096MB issue

["Carl Jones" <carl.jones@xxxxxxxxx>]

On Tue, Aug 5, 2008 at 3:07 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Carl Jones wrote:
>>
>> On Sun, Aug 3, 2008 at 4:00 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
>> wrote:
>>
>>>
>>> Carl Jones wrote:
>>>
>>>>
>>>> http://radium.outervoid.net/~carl/boot.log
>>>> http://radium.outervoid.net/~carl/xmlist.log ('xm list test1 --long'
>>>> output, in case that is helpful)
>>>>
>>>>
>>>
>>> Thanks.  Does this fix it?
>>>
>>> iff -r 25bf2d9a2e4c arch/x86/xen/setup.c
>>> --- a/arch/x86/xen/setup.c      Fri Aug 01 17:12:18 2008 -0700
>>> +++ b/arch/x86/xen/setup.c      Sat Aug 02 09:00:02 2008 -0700
>>> @@ -42,7 +42,7 @@
>>>
>>>       e820.nr_map = 0;
>>>
>>> -       e820_add_region(0, PFN_PHYS(max_pfn), E820_RAM);
>>> +       e820_add_region(0, PFN_PHYS((u64)max_pfn), E820_RAM);
>>>
>>>       /*
>>>        * Even though this is normal, usable memory under Xen, reserve
>>>
>>>
>>>  J
>>>
>>>
>>
>> Yep works nicely now. I tested up to 15GB or so with with that patch
>> applied and CONFIG_XEN_MAX_DOMAIN_MEMORY=32 set:
>>
>> testing:~# cat /proc/meminfo
>> MemTotal:     15769832 kB
>>
>
> Excellent, thanks.  That's 32-bit?  (That's a pretty silly amount of memory
> to give to a 32-bit system, but it's nice to know it works.)
>
> Could you try this patch instead to see if it works?  It's a more general
> fix.
>
> Thanks,
>   J
>
>
> Subject: make PFN_PHYS explicitly return 64-bit result

Hi,

Guest is 32bit. That patch works fine too.

Regards,
Carl

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