Re: [Xen-users] ARM: Xen on Vexpress

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2014-06-11 at 17:28 +0100, Jeenu Viswambharan wrote:
> On Wed, Jun 11, 2014 at 17:24:49, Ian Campbell wrote:
> > On Wed, 2014-06-11 at 17:12 +0100, Jeenu Viswambharan wrote:
> > > > Can you post your boot logs, perhaps they will give me a clue.
> > >
> > > I only have
> > >
> > >   (XEN) DOM0: Uncompressing Linux... done, booting the kernel.
> >
> > It's all the Xen output from before this which I am interested in.
> > Since that answers the questions I have about where Xen has placed
> > guest RAM etc.
> 
> OK, Xen logs attached.

Thanks. These contain:

(XEN) Populate P2M 0xa8000000->0xb0000000 (1:1 mapping for dom0)
(XEN) Loading kernel from boot module 2
(XEN) Loading zImage from 00000000a0008000 to 00000000afc00000-00000000aff26fb8
(XEN) Loading dom0 DTB to 0x00000000afa00000-0x00000000afa02f10

In that message 0xa0008000 is the *source* address (which makes sense,
since that is where you loaded it to). The kernel is being loaded to
address 0xafc00000 within dom0 RAM, which spans 0xa8000000->0xb0000000.
That load address is about where I would expect given the constraints
(just under 128M).

If you were to try booting natively at that address then I would expect
it to fail because base of the native RAM is 0x80000000 not 0xa8000000,
so the offset is too large.  You could try native boot from 0x87c00000
which is the same offset into RAM that Xen is using, I'm not sure what
that would tell us though TBH.

I've not used a vexpress, so I think I'll have to defer to Julien for
any other debugging tips.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users