|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] dmidecode doesn't work under xen 4.1.1 on certain hardwa
On 26/09/2011 20:37, Konrad Rzeszutek Wilk wrote:
>> __ __ _ _ _ _
>> \ \/ /___ _ __ | || | / | / |
>> \ // _ \ '_ \ | || |_ | | | |
>> / \ __/ | | | |__ _|| |_| |
>> /_/\_\___|_| |_| |_|(_)_(_)_|
>>
>> (XEN) Xen version 4.1.1 (@[unknown]) (gcc version 4.4.3 (GCC) ) Wed Sep 21
>> 08:25:36 GMT 2011
>> (XEN) Latest ChangeSet: unavailable
>> (XEN) Bootloader: GNU GRUB 0.97
>> (XEN) Command line:
>> (XEN) Video information:
>> (XEN) VGA is text mode 80x25, font 8x16
>> (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
>> (XEN) Disc information:
>> (XEN) Found 4 MBR signatures
>> (XEN) Found 4 EDD information structures
>> (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?
>> (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'
messages
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|