Re: [Xen-users] Booting Xen on ARM Juno r0

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Wed, 2015-07-15 at 11:25 -0400, John Paul Walters wrote:
> Hi all,
> 
> I'm trying to boot Xen on the ARM Juno r0 board and I'm running into
> some difficulties.  I've built xen and a Xen-enabled Dom0 kernel.
> I've confirmed that the dom0 kernel boots outside of Xen.
> 
> I'm aware of a prior thread involving issues booting Xen from the EFI boot 
> menu:
> http://lists.xenproject.org/archives/html/xen-devel/2014-10/msg02525.html
> 
> As you can see from below, I'm avoiding this issue by starting Xen
> directly from the EFI shell.  I'm using ARM's latest distributed
> firmware as opposed to Linaro's.  Are there particular Xen
> dependencies on one versus the other?

Not AFAIK.

> It appears that I'm running into at least a couple of issues.  First
> is that only a single CPU is brought up.  Second is that the dom0
> kernel appears to crash early in the boot process.  Has anyone
> successfully booted Xen on the Juno board recently?

I've not tried for several months I'm afraid.

Building Xen with CONFIG_EARLY_PRINTK=juno might get some useful extra
info. It would also be useful to see your file "cfg", in particular the
various command lines which it will contain.

I take it your dom0 kernel binary boot successfully with all CPUs
natively?

> 
> thanks,
> JP
> 
> UEFI firmware (version v3.0-rc0 built at 21:19:44 on Apr  8 2015)
> [1] Linux from NOR Flash
> [2] Debian ARMv8
> [3] KVM
> [4] Xen from NOR Flash
> [5] Shell
> [6] Boot Manager
> Start: 5
> UEFI Interactive Shell v2.1
> EDK II
> UEFI v2.40 (ARM Juno EFI Apr  8 2015 21:19:51, 0x00000000)
> Mapping table
>       FS2: Alias(s):F10:;BLK1:
>           VenHw(E7223039-5836-41E1-B542-D7EC736C5E59)
>       FS0: Alias(s):F3:
>           MemoryMapped(0xB,0xE0000000,0xE00EFFFF)
>       FS1: Alias(s):F4:
>           MemoryMapped(0xB,0xFEBC2000,0xFEDC693F)
>      BLK0: Alias(s):
>           VenHw(02118005-9DA7-443A-92D5-781F022AEDBB)
> Shell> fs2:
> FS2:\> xen -cfg=cfg
> 3hXen 4.5.1 (c/s Mon Jun 22 14:12:56 2015 +0100 git:6e865a4) EFI loader
> junoX: 0x00000009faf87000-0x00000009faf89b89
> ImageX: 0x00000009fa3ce000-0x00000009fac07000
>  Xen 4.5.1
> (XEN) Xen version 4.5.1 (root@xxxxxxxxxxxxxxxxx) (gcc (Debian/Linaro
> 4.9.2-20) 4.9.2) debug=n Tue Jul 14 18:20:46 UTC 2015
> (XEN) Latest ChangeSet: Mon Jun 22 14:12:56 2015 +0100 git:6e865a4
> (XEN) Processor: 410fd030: "ARM Limited", variant: 0x0, part 0xd03, rev 0x0
> (XEN) 64-bit Execution:
> (XEN)   Processor Features: 0000000000002222 0000000000000000
> (XEN)     Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
> (XEN)     Extensions: FloatingPoint AdvancedSIMD
> (XEN)   Debug Features: 0000000010305106 0000000000000000
> (XEN)   Auxiliary Features: 0000000000000000 0000000000000000
> (XEN)   Memory Model Features: 0000000000001122 0000000000000000
> (XEN)   ISA Features:  0000000000011120 0000000000000000
> (XEN) 32-bit Execution:
> (XEN)   Processor Features: 00000131:00011011
> (XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
> (XEN)     Extensions: GenericTimer Security
> (XEN)   Debug Features: 03010066
> (XEN)   Auxiliary Features: 00000000
> (XEN)   Memory Model Features: 10101105 40000000 01260000 02102211
> (XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
> (XEN) Error: PSCI version 0x10000 is not supported.
> (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
> (XEN) Using generic timer at 50000 KHz
> (XEN) GICv2 initialization:
> (XEN)         gic_dist_addr=000000002c010000
> (XEN)         gic_cpu_addr=000000002c02f000
> (XEN)         gic_hyp_addr=000000002c04f000
> (XEN)         gic_vcpu_addr=000000002c06f000
> (XEN)         gic_maintenance_irq=25
> (XEN) GICv2: 352 lines, 6 cpus, secure (IID 0200143b).
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) I/O virtualisation disabled
> (XEN) Allocated console ring of 16 KiB.
> (XEN) Bringing up CPU1
> (XEN) Failed to bring up CPU1
> (XEN) Failed to bring up CPU 1 (error -1)
> (XEN) Bringing up CPU2
> (XEN) Failed to bring up CPU2
> (XEN) Failed to bring up CPU 2 (error -1)
> (XEN) Bringing up CPU3
> (XEN) Failed to bring up CPU3
> (XEN) Failed to bring up CPU 3 (error -1)
> (XEN) Bringing up CPU4
> (XEN) Failed to bring up CPU4
> (XEN) Failed to bring up CPU 4 (error -1)
> (XEN) Bringing up CPU5
> (XEN) Failed to bring up CPU5
> (XEN) Failed to bring up CPU 5 (error -1)
> (XEN) Brought up 1 CPUs
> (XEN) P2M: 40-bit IPA with 40-bit PA
> (XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Loading kernel from boot module @ 00000009fa3ce000
> (XEN) Allocating 1:1 mappings totalling 128MB for dom0:
> (XEN) BANK[0] 0x000000d0000000-0x000000d8000000 (128MB)
> (XEN) Loading zImage from 00000009fa3ce000 to 
> 00000000d0080000-00000000d08b9000
> (XEN) Loading dom0 DTB to 0x00000000d7e00000-0x00000000d7e0204f
> (XEN) Scrubbing Free RAM on 1 nodes using 1 CPUs
> (XEN) ................................................................done.
> (XEN) Initial low memory virq threshold set at 0x4000 pages.
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) *** Serial input -> DOM0 (type 'CTRL-x' three times to switch
> input to Xen)
> (XEN) Freed 280kB init memory.
> (XEN) *** Serial input -> Xen (type 'CTRL-x' three times to switch
> input to DOM0)
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users



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