[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen not working with stock Debian Wheezy 3.2 kernel on a Core 2 Duo box
>>> On 08.07.13 at 15:42, Wei Liu <wei.liu2@xxxxxxxxxx> wrote: > On Mon, Jul 08, 2013 at 02:16:07PM +0100, Jan Beulich wrote: > [...] >> >> > 3.2.0-4-amd64 (just found out that there's actually backtrace in dmesg): >> > [ 0.000000] BIOS-provided physical RAM map: >> > [ 0.000000] BIOS-e820: 0000000000000000 - 000000000008f000 (usable) >> > [ 0.000000] BIOS-e820: 000000000008f000 - 00000000000a0000 (reserved) >> > [ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) >> > [ 0.000000] BIOS-e820: 0000000000100000 - 00000000ce69a000 (usable) >> > [ 0.000000] BIOS-e820: 00000000ce69a000 - 00000000ce6f1000 (ACPI NVS) >> > [ 0.000000] BIOS-e820: 00000000ce6f1000 - 00000000cf5fb000 (usable) >> > [ 0.000000] BIOS-e820: 00000000cf5fb000 - 00000000cf608000 (reserved) >> > [ 0.000000] BIOS-e820: 00000000cf608000 - 00000000cf6a5000 (usable) >> > [ 0.000000] BIOS-e820: 00000000cf6a5000 - 00000000cf6aa000 (ACPI data) >> > [ 0.000000] BIOS-e820: 00000000cf6aa000 - 00000000cf6ab000 (usable) >> > [ 0.000000] BIOS-e820: 00000000cf6ab000 - 00000000cf6f2000 (ACPI NVS) >> > [ 0.000000] BIOS-e820: 00000000cf6f2000 - 00000000cf6ff000 (ACPI data) >> > [ 0.000000] BIOS-e820: 00000000cf6ff000 - 00000000cf700000 (usable) >> > [ 0.000000] BIOS-e820: 00000000cf700000 - 00000000d0000000 (reserved) >> > [ 0.000000] BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) >> > [ 0.000000] BIOS-e820: 0000000100000000 - 000000022c000000 (usable) >> >> So no such block right off the BIOS. You're not using Xen TXT code >> by chance? Off the top of my head I don't recall any other place >> where multiple RAM pages might get turned into "unusable". >> > > I don't think so but I'm not sure. I don't see any TXT option in BIOS > setting, so I presume that mother board doesn't have such thing -- it's > pretty old. Odd - the only other place where we do such conversion is when clipping memory, which shouldn't be the case here (unless you have a strange "mem=" option on your command line). And with TXT, you'd at least have one line starting "TBOOT: " in your hypervisor log. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |