Hi all,

I'm using yocto to generate a riscv32 image but qemu seems to be ignoring
the -m argument from the command line and forcing the image to run with
988MB of RAM. I'm trying to track down where the issue comes from and maybe
it's from the linux-yocto kernel?

Here's also the boot log: https://pastebin.com/b7ZEP659

I see that the kernel prints:


   1. [ 0.000000] OF: fdt: Ignoring memory range 0x80000000 - 0x80400000
   2. [ 0.000000] Memory limited to 1024MB


I'm using linux-yocto 5.19.17+gitAUTOINC+239a6c0d3c_84f2f8e7a6-r0.

Is there any way I can increase it to 4G?

I'm using the following cmdline to start qemu:

qemu-system-riscv32 -nographic -machine virt -m 2G -smp 8 -bios
/home/mgadelha/tools/poky/build/tmp/deploy/images/qemuriscv32/fw_jump.elf
-kernel /home/mgadelha/tools/poky/build/tmp/deploy/images/qemuriscv32/Image
-append "root=/dev/vda rw mem=2G" -drive
id=disk0,file=/home/mgadelha/tools/poky/build/tmp/deploy/images/qemuriscv32/core-image-full-cmdline-qemuriscv32-20230415202008.rootfs.ext4,if=none,format=raw
-device virtio-net-device,netdev=usernet -netdev
user,id=usernet,hostfwd=tcp::22222-:22 -device
virtio-blk-device,drive=disk0 -object
rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0
-device virtio-tablet-pci -device virtio-keyboard-pci

It doesn't even start if I use -m 4G. It boots for lower values but memory
is still 988MB.

If I remove the mem=2G kernel argument, I don't get the "memory limited"
message but the memory still is 988MB.

Thank you,

-- 

Mikhail Ramalho.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59727): https://lists.yoctoproject.org/g/yocto/message/59727
Mute This Topic: https://lists.yoctoproject.org/mt/98363564/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to