[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] How to build Mini-OS for ARM
Oh, my mistake was that I was loading Image instead of Image.gz.
And the latter didn't work because I specified a wrong load address. So, now it works (loads the kernel and hangs on VFS because no disk is provided)
On 05/06/2019 14:18, Denis Obrezkov wrote:
> Hi,
Hi,
> I got an error:
> 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) Missing kernel boot module?
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Could not set up DOM0 guest OS
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
>
> I configured Linux with defconfig and on wiki-page I can see:
>
> In general the same kernel configuration as used to boot natively, plus turning
> on the Xen specific options should work. A good starting point is often the
> "multi_v7_defconfig" + Xen options.
>
> but what are those Xen options?
The Xen options are most of the one following the pattern CONFIG_*XEN*. But not
having those options in the kernel should still allow you to boot.
The problem here is you haven't specified to Xen where the kernel is loaded.
This should be done in the Device-Tree. How do you boot Xen? Are you using
U-boot? If so, what's your commands?
Cheers,
--
Julien Grall
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users
|
