WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] dmidecode doesn't work under xen 4.1.1 on certain hardwa

> >> (XEN) WARNING: Only the first 16 GB of the physical memory map can be 
> >> accessed by Xen in 32-bit mode.
> > That bites ^^^^
> >> (XEN) Truncating RAM from 17825792kB to 16777216kB
> Does this mean that 32 bit Xen can only use a maximum of 16GB of RAM?
> 
> If so, is there a way to use 32 bit Xen tools with a 64 bit Xen hypervisor?

Yes. I've been doing that without any trouble.
> 
> >> (XEN) Xen-e820 RAM map:
> >> (XEN)  0000000000000000 - 0000000000099800 (usable)
> >> (XEN)  0000000000099800 - 00000000000a0000 (reserved)
> >> (XEN)  00000000000e4000 - 0000000000100000 (reserved)
> >> (XEN)  0000000000100000 - 00000000bf780000 (usable)
> >> (XEN)  00000000bf78e000 - 00000000bf790000 type 9
> > Ok, so this patch should shed some light and potentially fix your problem. 
> > Please
> > try it out and attach the serial log for Linux kernel. Thx.
> The patch works perfectly. I've attached a copy of the kernel log with
> 'debug loglevel=8'

Yeeey! Great. Thanks for testing it. We are re-doing that whole E820 parsing
for the next version of Linux (3.2) so will integrate the "essence" of that
patch.

Would you be up for testing a different variant of that patch just to make
sure?

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