[Top][All Lists]

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

Re: [Qemu-discuss] big mips64-64 initrd does not boot

From: Dennis Luehring
Subject: Re: [Qemu-discuss] big mips64-64 initrd does not boot
Date: Thu, 29 Sep 2016 16:27:58 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0

solved the memory size problem with the helo of the linux-mips-irc/mailing-list

detailed descrioption: https://people.debian.org/~aurel32/qemu/mips/

using "address@hidden address@hidden" as kernel parameter gives me 1GB and then my big initrd could be loaded

Am 08.09.2016 um 20:54 schrieb Jakob Bohm:
On 08/09/2016 11:29, Dennis Luehring wrote:
> i've got two cleanly build mips64-764 initrds (based on cross linux
> from scratch, gcc 6.1 and linux kernel 4.7) that i want to boot with qemu
> initrd.cpio ~14.5 MB
> big_initrd.cpio ~323.4 MB
> mips64-softmmu/qemu-system-mips64 -M malta -m 1GB -nographic -monitor
> telnet::4440,server,nowait -serial telnet::3000,server -kernel
> clfskernel-4.7.0 -initrd initrd.cpio
> the smaller initrd.cpio (~14.5 MB) boots without any problem and shows
> the output of an test-program at end of the booting
> the big one with ~323.4 MB seems to hang right before the
> ramdisk/initrd extraction
> both initrds are build by the same script - the bigger one just gets
> more programs in - the same script is used for building for
> ppc64, alpha and sparc an both initrds are working on these platforms
> small tests show that this seem not to be a kernel or gcc bug (same
> problem with linux 4.5,4.6.4,4,7, gcc 5.2,5.3,6.1)
> is my big_inird.cpio too large for the malta platform (or my
> linux-conf?) or is this maybe an emulation problem with qemu?
According to your kernel message log, the guest machine only
has 256MiB RAM:

   memory: 0000000010000000 @ 0000000000000000 (usable)


I think you swapped the two log file names.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]