[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] boot-wrapped xen image barfs with overlapped sections
Hi, all, I have been following the instructions at https://wiki.linaro.org/LEG/Engineering/Virtualization/Xen_on_ARMv8_Foundation to build xen for arm64. When I tried to use the latest kernel instead of v3.13 as suggested, I failed when building boot-wrapped image. See below. ======================= jsun@ubuntu:~/work/xen/linaro-2014-guide/boot-wrapper-aarch64$ make CROSS_COMPILE=aarch64-linux-gnu- FDT_SRC=foundation-v8.dts xen-system.axf aarch64-linux-gnu-ld -o xen-system.axf --script=model.xen.lds aarch64-linux-gnu-ld: section .xen loaded at [0000000080a00000,0000000080ac061f] overlaps section .kernel loaded at [0000000080080000,0000000080c50dff] Makefile:78: recipe for target 'xen-system.axf' failed make: *** [xen-system.axf] Error 1 ======================= Obviously the issue is that linker script gives about 8.5MB space for kernel which is too small. If I modify the linker script to give more space to kernel, the xen will halt during boot up right before Dom0 starts: ========================== (XEN) *** LOADING DOMAIN 0 *** (XEN) Loading kernel from boot module @ 0000000080080000 (XEN) Allocating 1:1 mappings totalling 512MB for dom0: (XEN) BANK[0] 0x000000a0000000-0x000000c0000000 (512MB) (XEN) Grant table range: 0x000000ffe00000-0x000000ffe5e000 (XEN) Loading zImage from 0000000080080000 to 00000000a0080000-00000000a0880000 (XEN) Allocating PPI 16 for event channel interrupt (XEN) Loading dom0 DTB to 0x00000000a8000000-0x00000000a8000fe7 (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) *** Serial input -> DOM0 (type 'CTRL-x' three times to switch input to Xen) (XEN) Freed 276kB init memory. ========================== Any pointers on the right way to get modern kernel working with xen on ARM64? Thanks. Jun _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |