[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] boot-wrapped xen image barfs with overlapped sections
I finally resolved this issue after hunting around. The clue comes from this page, https://wiki.linaro.org/LEG/Engineering/Virtualization/Xen_ARM_Guide: /chosen/module@1/reg should match bootwrapper model.lds. Basically if I increase memory region for kernel, I should also update dts file on /chosen/module@1/reg. Here is what in model.xen.lds. As you can see, kernel area is increased to 14MB. OUTPUT_FORMAT("elf64-littleaarch64") OUTPUT_ARCH(aarch64) TARGET(binary) INPUT(./boot.xen.o) INPUT(Xen) INPUT(Image) INPUT(./fdt.dtb) SECTIONS { . = 0x80000000; .text : { boot.xen.o } . = 0x80000000 + 0xfff8; mbox = .; .mbox : { QUAD(0x0) } . = 0x80000000 + 0xE00000; xen = .; .xen : { Xen } . = 0x80000000 + 0x80000; kernel = .; .kernel : { Image } . = 0x80000000 + 0x08000000; dtb = .; .dtb : { ./fdt.dtb } .data : { *(.data) } .bss : { *(.bss) } } And here is what in foundation-v8.dts for chosen: chosen { #address-cells = <0x1>; #size-cells = <0x1>; xen,xen-bootargs = "dom0_mem=512M dom0_max_vcpus=2 dtuart=serial0 conswitch=x loglvl=all guest_loglvl=all no-bootscrub"; module@1 { compatible = "xen,linux-zimage", "xen,multiboot-module"; reg = <0x80080000 0xe00000>; bootargs = "earlyprintk=pl011,0x1c090000 console=hvc0 root=/dev/vda2 debug rw"; }; }; Kernels can be any recent 4.x kernel from torvalds, stable or linaro trees. Now move to on to boot kernel with initrd. Jun On Fri, Sep 16, 2016 at 2:44 PM, Jun Sun <jsun@xxxxxxxxxx> wrote:
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |