On 7/4/22 11:55, Bin Meng wrote:
Hi Heinrich,
On Sun, Jul 3, 2022 at 8:09 PM Heinrich Schuchardt
<heinrich.schucha...@canonical.com> wrote:
On 7/3/22 13:28, Heinrich Schuchardt wrote:
Consider which boot devices are enabled in the definition of the
BOOT_TARGET_DEVICES() macro.
Signed-off-by: Heinrich Schuchardt <heinrich.schucha...@canonical.com>
Hello Bin,
With the patch I can run U-Boot
qemu-riscv_smode_defconfig
CONFIG_MTD_NOR_FLASH=n
CONFIG_CMD_NET=n
with QEMU 7.0 using KVM using command
qemu-system-riscv64
-M virt -accel kvm -m 2G -smp 2
-nographic
-kernel u-boot
-device virtio-net-device,netdev=eth0
-netdev user,id=eth0,hostfwd=tcp::8022-:22
-drive file=riscv64.img,format=raw,if=none,id=NVME1
-device nvme,drive=NVME1,serial=nvme-1
and boot Linux from it.
I see you specifically wanted to run U-Boot with KVM, and it did not
work. If without KVM it boots then it's a problem of KVM/QEMU.
Booting with KVM works if U-Boot does not touch virtio. Linux accessing
virtio does not cause a crash.
So it looks like a U-Boot issue.
I have set CONFIG_MTD_NOR_FLASH=n, CONFIG_CMD_NET=n to avoid touching
virtio before reaching the command prompt.
But whenever virtio is accessed by U-Boot QEMU crashes without output.
E.g. after 'virtio scan' even CTRL+A,C is ignored.
Did you have more success? Any clue how to debug this?
Which QEMU/KVM (Linux kernel version) did you use for the testing?
From:
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/develop/+packages
https://launchpad.net/~ubuntu-risc-v-team/+archive/ubuntu/develop/+files/qemu-system-misc_7.0+dfsg-7ubuntu1~ppa3_riscv64.deb
From:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-image-5.17.0-1003-starfive_5.17.0-1003.4_riscv64.deb
Best regards
Heinrich
Regards,
Bin
