[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Booting dom0 on OMAP5432 board

 That's what I have in FDT before bootm command:

U-Boot# fdt print /chosen
chosen {
        xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug
ignore_loglevel root=/dev/mmcblk0p2 rw rootwait fixrtc";
        xen,xen-bootargs = "sync_console console=dtuart dtuart=serial2";
        modules {
                #size-cells = <0x00000001>;
                #address-cells = <0x00000001>;
                module@0 {
                        reg = <0xa0000000 0x00a00000>;
                        compatible = "xen,linux-zimage", "xen,multiboot-module";

Also I tried to add more options for Xen (which I took from Arndale
setup): "loglvl=all guest_loglvl=all sync_console console_to_ring"
but this didn't add any extra info.


On Wed, Sep 24, 2014 at 1:48 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Wed, 2014-09-24 at 13:35 +0400, Konstantin Belov wrote:
>> (XEN) MODULE[1]: 00000000a0000000 - 00000000a0a00000 Kernel
> This should have the kernel command line after it, which suggests it is
> not making it through for some reason.
> If you add just before the bootm or bootz:
>         fdt chosen
>         fdt print /chosen
> Then that should show what was actually passed in the FDT which might
> give a hints as to whether the  problem is with the u-boot runes or with
> Xen itself.
> Ian.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.