[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen-ARM couldn't boot up

Hi Ian,
Thanks for your help. With your guide,  I tried to re-compile the xen:
(1)    make dist-xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-unknown-linux-gnueabi- CONFIG_DTB_FILE=/home/joshzhao/project/xen/vexpress-v2p-ca15-tc1.dtb.
(2)    model_shell cadi_system_Linux-Release-GCC-4.1.so /home/joshzhao/project/xen/xen/xen/xen -C motherboard.flashloader0.fname=/home/joshzhao/project/xen/dom0/linux/arch/arm/boot/zImage

Finally,the FastModel shows 2 terminals, terminal0 prints kernel panic at kernel/irq/irqdomain.c: 137 and terminal1 has a kernel panic because of mmcblk0 device node unknown. The linux kernel's command line is "earlyprintk=xenboot console=ttyAMA1 root=/dev/mmcblk0 debug rw ".
Hence I has 2 questions:
(1) How I pass the FS image to Dom0 kernel?
(2) I am wondering how to redirect model_shell's terminals output into a file?  Because I couldn't  copy the output from the terminals.

Thanks a lot.

josh zhao 

2013/3/5 Ian Campbell <ian.campbell@xxxxxxxxxx>
On Tue, 2013-03-05 at 08:46 +0000, Josh Zhao wrote:
> Hi,
> There is no xen infomation output from Fastmodel.

So no output at all?

>    make dist-xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-unknown-linux-gnueabi-

Did you supply a DTB? Normally this would involve setting
CONFIG_DTB_FILE as described by

> 3)  model_shell
> cadi_system_Linux-Release-GCC-4.1.so/project/xen/xen/dist/install/boot/xen-syms-4.3-unstable -C motherboard.flashloader0.fname=/project/xen/dom0/linux/arch/arm/boot/zImage

You need to use xen-4.3-unstable not the xen-syms version. I don't know
if that is what is causing your issue though.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.