Re: [Xen-devel] Problems when creating domU on FastModel Cortex-A15

[XiaoGuang Wang <xjtuwxg@xxxxxxxxx>]

2013/10/16 Ian Campbell <Ian.Campbell@xxxxxxxxxx>

On Tue, 2013-10-15 at 15:58 -0400, XiaoGuang Wang wrote:
> What exact version (i.e. changesets) of Xen and Linux are you running?
>
>                 Have you started the Xen control daemons (xenconsoled
>                 and xenstored)?
>                 What is the contents of your domU-config?
>         I use xen-4.4 unstable (downloaded around Sep 15), and Linux
>         3.11 as dom0 and domU. The xenconsoled and xenstored is
>         running:
>         root@dom0:/root# ps -A |grep xen
>             9 ?        00:00:00 xenwatch
>            10 ?        00:00:00 xenbus
>            14 ?        00:00:00 xenbus_frontend
>            47 ?        00:00:00 xenconsoled
>            53 ?        00:00:02 xenstored
>         domU-config is:
>         root@dom0:/root# cat domU-config
>         kernel = "/root/image"
>         memory = 100
>         name = "domU"
>         vcpus = 1
>         disk = [ 'phy:/dev/loop0,xvda,w' ]
>
> Hi Ian/all,
>
> I tried xen-4.3 and Linux-3.9.11 just now.

Lets stick with xen-unstable (aka 4.4-pre) latest for now rather than
jumping around the versions.

Kernel 3.11 or 3.9 should be fine, I'd be inclined to go for the later
one.

>  There is no "Failed to unmap pfn:86cf6 rc:-2" error. But I still
> cannot create domU. It seems some problems like:
> libxl: verbose:
> libxl_create.c:130:libxl__domain_build_info_setdefault: qemu-xen is
> unavailable, use qemu-xen-traditional instead: No such file or
> directory

This is an x86ism which has leaked into ARM, there should be no qemu at
all. I think this ought to be harmless.

> The whole log from xl create -vvv is in:
> http://hi.baidu.com/supernpu/item/79bc6606e802e01ceafe38cf

FYI it is a lot easier for everyone if you just paste the whole thing
into email...

I see you have used "xl -vvv create <cfg> -c". Although I think it isn't
hurting for now please drop the "-c" to avoid confusion at this stage.
If things were working it would autoconnect the console,  but it would
have to be before <cfg> to work, I think.

I can't see anything untoward in your log, it seems to think it has
started the domain OK but by the time you run xl list it has gone.

There should be other logs under /var/log/xen/*domU* -- please can you
post them, they may give a clue.

Thanks for you patient reply!

This log shows something like:
Domain 3 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy

So I search for your previous suggestion on this problem, and enable the guest (domU) console log. Now it like this (with "xl dmesg"):
(XEN) Brought up 1 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Populate P2M 0x80000000->0x88000000
(XEN) No boot modules found, trying flash
(XEN) Loading zImage from 0000000000000000 to 0000000080008000-000000008024b578
(XEN) Loading dom0 DTB to 0x0000000087e00000-0x0000000087e01c4b
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 216kB init memory.
(XEN) DOM1: [    0.000000] Booting Linux on physical CPU 0x0
(XEN) DOM1: [    0.000000] Linux version 3.9.11 (xiaoguang@dophine) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #3 Wed Oct 16 15:3
(XEN) DOM1: 7:52 EDT 2013
(XEN) DOM1: [    0.000000] CPU: ARMv7 Processor [412fc0f0] revision 0 (ARMv7), cr=10c53c7d
(XEN) DOM1: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
(XEN) DOM1: [    0.000000] Machine: ARM-Versatile Express, model: XENVM-4.2
(XEN) DOM1: [    0.000000] bootconsole [earlycon0] enabled
(XEN) DOM1: [    0.000000] Memory policy: ECC disabled, Data cache writeback
(XEN) Guest data abort: Translation fault at level 2
(XEN)     gva=c7fff000
(XEN)     gpa=0000000087fff000
(XEN)     instruction syndrome invalid
(XEN)     eat=0 cm=0 s1ptw=0 dfsc=6
(XEN) dom1 IPA 0x0000000087fff000
(XEN) P2M @ 026bae40 mfn:0xb5d72
(XEN) 1ST[0x2] = 0x00000000ffe676ff
(XEN) 2ND[0x3f] = 0x0000000000000000
(XEN) ----[ Xen-4.3.0  arm32  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) PC:     c018b0a4
(XEN) CPSR:   200001d3 MODE:32-bit Guest SVC
(XEN)      R0: c7fff000 R1: 00000fc0 R2: 00000000 R3: 00000000
(XEN)      R4: c7fff000 R5: 00001000 R6: c04688b8 R7: c04515b0
(XEN)      R8: c0463348 R9: 80000200 R10:c03ce4b3 R11:00000000 R12:00000000
(XEN) USR: SP: 00000000 LR: 00000000
(XEN) SVC: SP: c0459f5c LR: 00000000 SPSR:000001d3
(XEN) ABT: SP: c048038c LR: c048038c SPSR:00000000
(XEN) UND: SP: c0480398 LR: c0480398 SPSR:00000000
(XEN) IRQ: SP: c0480380 LR: c0480380 SPSR:00000000
(XEN) FIQ: SP: 00000000 LR: cfdfdfdf SPSR:00000000
(XEN) FIQ: R8: 00000000 R9: 00000000 R10:00000000 R11:00000000 R12:00000000
(XEN)
(XEN) TTBR0 0080004059 TTBR1 0080004059 TCR 00000000
(XEN) SCTLR 10c53c7d
(XEN) IFAR 00000000 DFAR 00000000
(XEN)
(XEN) HTTBR ffed2000
(XEN) HDFAR c7fff000
(XEN) HIFAR 0
(XEN) HPFAR 87fff0
(XEN) HCR 00082835
(XEN) HSR   90000046
(XEN) VTTBR 20000b5d72000
(XEN)
(XEN) DFSR 0 DFAR 0
(XEN) IFSR 0 IFAR 0
(XEN)
(XEN) GUEST STACK GOES HERE
(XEN) domain_crash_sync called from traps.c:1044
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.3.0  arm32  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) PC:     c018b0a4
(XEN) CPSR:   200001d3 MODE:32-bit Guest SVC
(XEN)      R0: c7fff000 R1: 00000fc0 R2: 00000000 R3: 00000000
(XEN)      R4: c7fff000 R5: 00001000 R6: c04688b8 R7: c04515b0
(XEN)      R8: c0463348 R9: 80000200 R10:c03ce4b3 R11:00000000 R12:00000000
(XEN) USR: SP: 00000000 LR: 00000000
(XEN) SVC: SP: c0459f5c LR: 00000000 SPSR:000001d3
(XEN) ABT: SP: c048038c LR: c048038c SPSR:00000000
(XEN) UND: SP: c0480398 LR: c0480398 SPSR:00000000
(XEN) IRQ: SP: c0480380 LR: c0480380 SPSR:00000000
(XEN) FIQ: SP: 00000000 LR: cfdfdfdf SPSR:00000000
(XEN) FIQ: R8: 00000000 R9: 00000000 R10:00000000 R11:00000000 R12:00000000
(XEN)
(XEN) TTBR0 0080004059 TTBR1 0080004059 TCR 00000000
(XEN) SCTLR 10c53c7d
(XEN) IFAR 00000000 DFAR 00000000
(XEN)
(XEN) HTTBR ffed2000
(XEN) HDFAR c7fff000
(XEN) HIFAR 0
(XEN) HPFAR 87fff0
(XEN) HCR 00082835
(XEN) HSR   90000046
(XEN) VTTBR 20000b5d72000
(XEN)
(XEN) DFSR 0 DFAR 0
(XEN) IFSR 0 IFAR 0
(XEN)
(XEN) GUEST STACK GOES HERE
(XEN) mm.c:1096:d0 gnttab_mark_dirty not implemented yet

You could also try "xl -vvv create -F <cfg>" which will cause xl to stay
in the foreground and perhaps let you see more logs.

> So I'm not sure how can I see the domU console?

xl list shows that the domain isn't even running, so you can't.

Once it is the "xl console <domain>" will work. So would "xl create -c
<cfg>" (but as mentioned above not "xl create <cfg> -c", I don't think).

Thanks!

Xiaoguang

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