AW: Colibri imx8qxp: Missing kernel boot module

[Daniel Wagner2 <Daniel.Wagner2@xxxxxxxxxxxxxxxxxx>]

> -----Ursprüngliche Nachricht-----
> Von: Peng Fan <peng.fan@xxxxxxx>
> Gesendet: Montag, 17. August 2020 12:02
> An: Daniel Wagner2 <Daniel.Wagner2@xxxxxxxxxxxxxxxxxx>; xen-
> users@xxxxxxxxxxxxxxxxxxxx
> Betreff: RE: Colibri imx8qxp: Missing kernel boot module
> 
> > Subject: AW: Colibri imx8qxp: Missing kernel boot module
> >
> >
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Peng Fan <peng.fan@xxxxxxx>
> > > Gesendet: Montag, 17. August 2020 11:47
> > > An: Daniel Wagner2 <Daniel.Wagner2@xxxxxxxxxxxxxxxxxx>; Julien Grall
> > > <julien@xxxxxxx>; xen-users@xxxxxxxxxxxxxxxxxxxx
> > > Betreff: RE: Colibri imx8qxp: Missing kernel boot module
> > >
> > > > Subject: AW: Colibri imx8qxp: Missing kernel boot module
> > > >
> > > >
> > > >
> > > > > -----Ursprüngliche Nachricht-----
> > > > > Von: Xen-users <xen-users-bounces@xxxxxxxxxxxxxxxxxxxx> Im
> > > > > Auftrag von
> > > > Julien
> > > > > Grall
> > > > > Gesendet: Freitag, 14. August 2020 21:46
> > > > > An: Daniel Wagner2 <Daniel.Wagner2@xxxxxxxxxxxxxxxxxx>; xen-
> > > > > users@xxxxxxxxxxxxxxxxxxxx; Peng Fan <peng.fan@xxxxxxx>
> > > > > Betreff: Re: Colibri imx8qxp: Missing kernel boot module
> > > > >
> > > > > On 10/08/2020 16:32, Daniel Wagner2 wrote:
> > > > > > Hello xen-users,
> > > > >
> > > > > Hello,
> > > > >
> > > > > > we are trying to get Xen running on a Toradex "Colibri iMX8X"
> > > > > > module (see [1] at the bottom of this email), which features
> > > > > > the
> > > > > > iMX8 QXP
> > > > prozessor.
> > > > > > We found that NXP has a Xen reference implementation [2][3]
> > > > > > for their MEK Module and tried to port that to the Toradex
module.
> > > > > >
> > > > > > When booting via the bootscript [4], which is unaltered except
> > > > > > for the "dom0fdt_file" and "xenhyper_bootargs" variables, we
> > > > > > get the following
> > > > > > error:
> > > > > >
> > > > > > [...] (See [5] for complete bootlog)
> > > > > > (XEN) *** LOADING DOMAIN 0 ***
> > > > > > (XEN) Missing kernel boot module?
> > > > > > (XEN)
> > > > > > (XEN) ****************************************
> > > > > > (XEN) Panic on CPU 0:
> > > > > > (XEN) Could not set up DOM0 guest OS
> > > > > > (XEN) ****************************************
> > > > > > (XEN)
> > > > > > (XEN) Reboot in five seconds...
> > > > > >
> > > > > > For Dom0 we took the linux-toradex kernel source, ran "make
> > xenconfig"
> > > > > > [6], which should add Xen-support and rebuilt the Image with
> > > > > > "make
> > > > Image".
> > > > > > For dom0 DTB [7] we copied the dom0 DTS NXP uses for their
> > > > MEK-Module
> > > > > > [8] and only adjusted the "bootargs" parameter.
> > > > > > This Linux Image was able to run after we rebuilt and booted
> > > > > > it without
> > > > Xen.
> > > > >
> > > > > Which Device-Tree did you for boot Linux without Xen?
> > > >
> > > > Used the same Device-Tree Binary that we want to use with Xen
> > > > which is described in [7]. In [7] you can see rows 23 and 24,
> > > > which include the Devicetree as it is supplied by Toradex.
> > > > To boot linux with our dom0 DTB, the u-boot variable fdt_file was
> > > > changed from fsl-imx8qxp-colibri-eval-v3.dtb to
> > > > fsl-imx8qxp-colibri-eval-v3-dom0.dtb.
> > >
> > >
> > > Did you use the U-Boot cmd 'xenmmcboot' or 'xennetboot'?
> >
> > To boot linux without Xen the u-boot cmd 'boot' is used.
> > To boot Xen we use 'run xenmmcboot' (in an adjusted form to account
> > for different filenames and bootargs, see [4]).
> 
> So kernel Image loaded to 0x80a00000, right?
> 
> Please load kernel image before run xenmmcboot if not.

The xenmmcboot script [4] line 25 loads the linux image.
Inserting the values for the variables in this line gives:
'fatload mmc 0:1 0x92000000 image'
So we load the kernel image to 0x92000000. Is this not the right adress? 
How can the right adress, to load the kernel image to, be determined?
Loading it to 0x80a00000 yields the same error ("Missing kernel boot
module?")

Regards,
Daniel

> Regards,
> Peng.
> 
> >
> > >
> > > Regards,
> > > Peng.
> > >
> > > >
> > > > >
> > > > > >
> > > > > > Question 1:
> > > > > > The xen dokumentation always states, that the Dom0- and DomU-
> > > > > > Images have to be in zImage format, but according to [9] arm64
> > > > > > doesn't use zImage and [10] says the arm64/Image is equivalent
> > > > > > to
> > zImage.
> > > > > > Can we assume that our arm64/Image should work, if everything
> > > > > > else was
> > > > > fine?
> > > > >
> > > > > This is a mistake in the documentation. Xen is able to load
> > arm64/Image.
> > > >
> > > > Thanks for the confirmation!
> > > >
> > > > >
> > > > > Can you give me a pointer to the documentation you are using? I
> > > > > will
> > > > update it.
> > > > >
> > > >
> > > > ' where "/root/image" is a Linux zImage.'
> > > > https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Exten
> > > > sion
> > > > s#D
> > > > omU
> > > > _kernel_and_DTS
> > > >
> > > > > >
> > > > > > Question 2:
> > > > > > Our Xen was build with imx-xen repository [11] as source via
> > > > > > NXP's BSP according to [1] with MACHINE=imx8qxpmek.
> > > > > > Can we use the resulting Xen Hypervisor-Image for the Toradex
> > > > > > IMX8X Module, as it uses the same Processor (i.MX 8 QXP)?
> > > > >
> > > > > I am afraid this tree is not maintained by Xen Project but,
> > > > > IIRC, NXP. I
> > > > have CCed
> > > > > one person that may be able to help you.
> > > >
> > > > Thanks for connecting!
> > > >
> > > > > >
> > > > > > Question 3:
> > > > > > If the answers to Question 1 and Question 2 are yes, then what
> > > > > > else could we be missing?
> > > > > >
> > > > > >
> > > > > >
> > > > > > [1]
> > > > > >
> > > >
> > https://www.toradex.com/de/computer-on-modules/colibri-arm-family/nxp-
> > > > > > imx-8x [2]
> > > > > > https://www.nxp.com/docs/en/user-
> > > > > guide/IMX_YOCTO_PROJECT_USERS_GUIDE.p
> > > > > > df [3]
> > > > > >
> > > >
> > https://www.nxp.com/docs/en/user-guide/IMX_LINUX_USERS_GUIDE.pdf
> > > > > >
> > > > > > Bootscript:
> > > > > > [4] https://pastebin.com/dcj0K3Xb
> > > > > >
> > > > > > Complete Bootlog:
> > > > > > [5] https://pastebin.com/eLpZvd29
> > > > > >
> > > > > > Xenconfig according to Xen Wiki [6]
> > > > > >
> > > >
> > https://wiki.xenproject.org/wiki/Compiling_Xen_From_Source#Compiling_l
> > > > > > atest_
> > > > > > Linux_kernel_support
> > > > > >
> > > > > > fsl-imx8qxp-colibri-eval-v3-dom0.dts:
> > > > > > [7] https://pastebin.com/f4dGCYFf
> > > > > >
> > > > > > fsl-imx8qxp-mek-dom0.dts:
> > > > > > [8] https://pastebin.com/c3Ukc6mZ
> > > > > >
> > > > > > No arm64/zImage:
> > > > > > [9] https://community.nxp.com/thread/482861#comment-1051436
> > > > > >
> > > > > > arm64/Image is equivalent to zImage:
> > > > > > [10] http://markmail.org/message/advnw6lk5rcfyabp
> > > > > >
> > > > > > iMX-XEN Repo:
> > > > > > [11]
> > > > > >
> > > >
> > https://source.codeaurora.org/external/imx/imx-xen/tree/?h=imx_4.19.35
> > > > > > _1.1.0
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thank you very much for your reading this mail and helping
> > > > > > with our
> > > > issue!
> > > > > >
> > > > > > Best regards,
> > > > >
> > > > > Best regards,
> > > > >
> > > > > --
> > > > > Julien Grall
> > > >
> > > > Best regards,
> > > >
> > > > Daniel Wagner

Attachment: smime.p7s
Description: S/MIME cryptographic signature