Re: [Xen-users] How to build Mini-OS for ARM

[Denis Obrezkov <denisobrezkov@xxxxxxxxx>]

You are right, I again forgot to change the size of the image in the device tree and used the size of a Image.gz.

When I changed it to the Image's size it started to work.

I think I want to automate it and pass the script to u-boot with automatically calculated size.

Could you propose what I should do next? I get to the point when Dom0 crashes when trying to mount rootfs because I don't provide it.

Should I investigate how other interrupt controllers are supported in xen?

чт, 6 июн. 2019 г. в 11:58, Julien Grall <julien.grall@xxxxxxx>:

On 06/06/2019 10:12, Denis Obrezkov wrote:
> H, I did mistake - Image is not booting:
> Starting kernel ...
>
>   Xen 4.12.0
> (XEN) Xen version 4.12.0 (denis@) (aarch64-linux-gnu-gcc (Ubuntu/Linaro
> 7.4.0-1ubuntu1~18.04) 7.4.0) debug=n  Wed Jun  5 14:57:33 CEST 2019
> (XEN) Latest ChangeSet:
> (XEN) Processor: 411fd070: "ARM Limited", variant: 0x1, part 0xd07, rev 0x0
> (XEN) 64-bit Execution:
> (XEN)   Processor Features: 0000000001000222 0000000000000000
> (XEN)     Exception Levels: EL3:No EL2:64+32 EL1:64+32 EL0:64+32
> (XEN)     Extensions: FloatingPoint AdvancedSIMD GICv3-SysReg
> (XEN)   Debug Features: 0000000010305106 0000000000000000
> (XEN)   Auxiliary Features: 0000000000000000 0000000000000000
> (XEN)   Memory Model Features: 0000000000001124 0000000000000000
> (XEN)   ISA Features:  0000000000011120 0000000000000000
> (XEN) 32-bit Execution:
> (XEN)   Processor Features: 00000131:10011001
> (XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
> (XEN)     Extensions: GenericTimer
> (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) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 62500 KHz
> (XEN) GICv3 initialization:
> (XEN)       gic_dist_addr=0x00000008000000
> (XEN)       gic_maintenance_irq=25
> (XEN)       gic_rdist_stride=0
> (XEN)       gic_rdist_regions=1
> (XEN)       redistributor regions:
> (XEN)         - region 0: 0x000000080a0000 - 0x00000009000000
> (XEN) GICv3: 256 lines, (IID 0000043b).
> (XEN) GICv3: CPU0: Found redistributor in region 0 @000000004001c000
> (XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
> (XEN) Initializing Credit2 scheduler
> (XEN) Allocated console ring of 16 KiB.
> (XEN) Bringing up CPU1
> (XEN) GICv3: CPU1: Found redistributor in region 0 @000000004003c000
> (XEN) Bringing up CPU2
> (XEN) GICv3: CPU2: Found redistributor in region 0 @000000004005c000
> (XEN) Bringing up CPU3
> (XEN) GICv3: CPU3: Found redistributor in region 0 @000000004007c000
> (XEN) Brought up 4 CPUs
> (XEN) P2M: 44-bit IPA with 44-bit PA and 8-bit VMID
> (XEN) P2M: 4 levels with order-0 root, VTCR 0x80043594
> (XEN) I/O virtualisation disabled
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Loading Domd0 kernel from boot module @ 0000000047000000
> (XEN) Allocating 1:1 mappings totalling 512MB for dom0:
> (XEN) BANK[0] 0x00000060000000-0x00000080000000 (512MB)
> (XEN) Grant table range: 0x00000049000000-0x00000049040000
> (XEN) Allocating PPI 16 for event channel interrupt
> (XEN) Loading zImage from 0000000047000000 to 0000000060080000-00000000608731ce
> (XEN) Loading dom0 DTB to 0x0000000068000000-0x0000000068001ccc
> (XEN) Initial low memory virq threshold set at 0x4000 pages.
> (XEN) Scrubbing Free RAM in background
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) ***************************************************
> (XEN) No support for ARM_SMCCC_ARCH_WORKAROUND_1.
> (XEN) Please update your firmware.
> (XEN) ***************************************************
> (XEN) PLEASE SPECIFY dom0_mem PARAMETER - USING 512M FOR NOW
> (XEN) ***************************************************
> (XEN) 3... 2... 1...
> (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
> (XEN) Freed 340kB init memory.

I guess Image and Image.gz are both from the same build. I am correct?
My feeling is the Image got overwritten by some other bits.

Could you provide the size of the Image and also the u-boot command your are using?

Cheers,

--
Julien Grall

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users