Re: [Xen-devel] Debugging Dom0 on OMAP5

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2013-10-24 at 06:17 -0400, Vaibhav Bedia wrote:
> Hi Ian,
> 
> On Thu, Oct 24, 2013 at 4:18 AM, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote:
> > On Wed, 2013-10-23 at 20:13 -0400, Vaibhav Bedia wrote:
> >
> >> Looking at the logs i noticed that the initrd is located outside the
> >> phys area that kernel
> >> is aware of and hence getting ignored.
> >>
> >> [...]
> >> [0.000000] INITRD: 0x83000000+0x01000000 is not a memory region -
> >> disabling initrd
> >>
> >> In the bootargs i have specified the initrd
> >
> > Do you mean the bootargs given to Xen or the ones given to dom0? How
> > exactly did you do this.
> >
> 
> I specified that in the bootargs being passed to Dom0.
> U-Boot# fdt set /chosen xen,dom0-bootargs \"console=hvc0,115200n8
> vram=16M root=/dev/ram initrd=0x83000000,16M ramdisk_size=65536 rw
> earlyprintk=xen lpj=61440 nohlt\"

OK, this won't work.You've told dom0 that there is an initrd at
0x83000000 but nothing here will actually be causing that to be the
case.

You need to pass an initrd boot module to Xen, using the fdt based
protocol described in
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/booting.txt;h=9802e5e20fd8c7da94eaa7b639b7530b951760eb;hb=HEAD
Xen will then take care of passing things to dom0.

Ian.


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