Re: dmidecode doesn't work under xen 4.1.1 on certain hardware

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Wed, Sep 28, 2011 at 05:07:07PM +0100, Anthony Wright wrote:
> On 28/09/2011 14:28, Konrad Rzeszutek Wilk wrote:
> >>>> (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.
> I tried to get this so work some time ago and failed. Do I need a 64 bit
> Dom0 kernel with a 64 bit xen hypervisor or can I get away with a 32 bit
> Dom0 kernel?

You can get away with a 32-bit dom0 kernel.

> >> 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?
> Not a problem, ship me the patch when you're ready. I'm running 3.0.4 at
> the moment and would prefer to stick with 3.0.x for now, so hope that
> won't be a problem.

Ok. Thx!