Re: [Xen-devel] XEN[ARM] Master not working on Allwinner A20

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2013-12-17 at 10:25 +0100, peter wrote:
> Well I managed to boot the current master
> Version: d96392361cd05a66b385f0153e398128b196e480 (xen: arm: correct
> return value of raw_copy_{to/from}_guest_*, raw_clear_guest).
> 
> This was done by removing the initrd in chosen.
> 
> When my chosen is like this, it will successfully boot
>     chosen {
>         bootargs = "dom0_mem=128M sync_console console=dtuart dtuart=serial0";
>         xen,dom0-bootargs = "console=hvc0,115200n8 debug ignore_loglevel
> rw rootwait earlyprintk=xen clk_ignore_unused root=/dev/nfs
> nfsroot=10.31.5.161:/export/cubie/rootfs,v3,tcp
> ip=10.31.5.165:10.31.5.161:10.31.4.1:255.255.252.0:cubie:eth0:off";
>         modules {
>             module@0 {
>                 compatible = "xen,linux-zimage", "xen,multiboot-module";
>                 reg = <0x50000000 0xf00000>;
>             };
>         };
>     };
>  
> When my chosen is:
>     chosen {
>         bootargs = "dom0_mem=128M sync_console console=dtuart dtuart=serial0";
>         xen,dom0-bootargs = "console=hvc0,115200n8 debug ignore_loglevel
> rw rootwait earlyprintk=xen clk_ignore_unused root=/dev/nfs
> nfsroot=10.31.5.161:/export/cubie/rootfs,v3,tcp
> ip=10.31.5.165:10.31.5.161:10.31.4.1:255.255.252.0:cubie:eth0:off";
>         modules {
>             module@0 {
>                 compatible = "xen,linux-zimage", "xen,multiboot-module";
>                 reg = <0x50000000 0xf00000>;
>             };
>             module@1 {
>                 compatible = "xen,linux-initrd", "xen,multiboot-module";
>                 reg = <0x60000000 0x6000000>;
>                 linux,initrd-start = <0x60000000>;
>                 linux,initrd-end = <0x66000000>;

FWIW you either need reg here or the linux,initrd-* in the same scope as
bootargs and xen,dom0-bootargs. Having both here is wrong, but probably
harmless (I think the linux,initrd-* will be ignored).

>             };
>         };
>     };
> It fails to boot, it stays stuck on (XEN) Freed 264kB init memory.

Can you provide a full log for this case please.

> And when my chosen is:
>     chosen {
>         bootargs = "dom0_mem=128M sync_console console=dtuart dtuart=serial0";
>         xen,dom0-bootargs = "console=hvc0,115200n8 debug ignore_loglevel
> rw rootwait earlyprintk=xen clk_ignore_unused";
>         modules {
>             module@0 {
>                 compatible = "xen,linux-zimage", "xen,multiboot-module";
>                 reg = <0x50000000 0xf00000>;
>             };
>             module@1 {
>                 compatible = "xen,linux-initrd", "xen,multiboot-module";
>                 reg = <0x60000000 0x6000000>;
>                 linux,initrd-start = <0x60000000>;
>                 linux,initrd-end = <0x66000000>;
>             };
>         };
>     };
> It successfully boots, I guess it somehow has to do with the allocation of
> the DTB. 

The only difference here is the shorter dom0-bootargs?

A diff of the log of this vs the non-working version might be
interesting.

> 
> When I want to create domU (on Master) it fails to allocate memory for it.
> Log:
> root@cubie:~# xl create -d domU
> Parsing config from domU
> unable to format domain config as JSON (YAJL:1)

What does your domU cfg file contain?

> [ 1358.109755] Failed to map pfn to mfn rc:-14:0 pfn:5c42c mfn:80008
> [ 1358.115910] Failed to map pfn to mfn rc:-14:0 pfn:5c42b mfn:80009

-14 is EFAULT. AFAICT this means that the argument to the hypercall
called from linux/arch/arm/xen/enlighten.c:map_foreign_page couldn't be
mapped/read, which is pretty unusual.

Which dom0 kernel version is this?

[...]
> xc: error: panic: xc_dom_boot.c:191: xc_dom_boot_domU_map: failed to mmap
> domU pages 0x80008+0x2f9 [mmap, errno=14 (Bad address)]: Internal error
> libxl: error: libxl_dom.c:403:libxl__build_pv: xc_dom_build_image failed:
> Bad address
> libxl: error: libxl_create.c:906:domcreate_rebuild_done: cannot (re-)build
> domain: -3

"xl -vvv cr [...]" might give some more hints on where things are going
wrong.

Ian


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