On Sun, Aug 14, 2022 at 10:23 PM Heinrich Schuchardt <heinrich.schucha...@canonical.com> wrote: > > The ELF U-Boot image produced by qemu-riscv64_smode_defconfig can be > used to boot with QEMU and KVM. > > Signed-off-by: Heinrich Schuchardt <heinrich.schucha...@canonical.com> > --- > doc/board/emulation/qemu-riscv.rst | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/doc/board/emulation/qemu-riscv.rst > b/doc/board/emulation/qemu-riscv.rst > index 782f37251c..7a21e12953 100644 > --- a/doc/board/emulation/qemu-riscv.rst > +++ b/doc/board/emulation/qemu-riscv.rst > @@ -133,6 +133,19 @@ An attached disk can be emulated in RISC-V virt machine > by adding:: > > You will have to run 'scsi scan' to use it. > > +Running with KVM > +---------------- > + > +Running with QEMU using KVM requires an S-mode U-Boot binary as created by > +qemu-riscv64_smode_defconfig. > + > +Provide the U-Boot S-mode ELF image as *-kernel* parameter, and do not add a > +*-bios* parameter e.g. > + > +.. code-block:: bash > + > + qemu-system-riscv64 -accel kvm -nographic -machine virt -kernel u-boot > + > Debug UART > ----------
Reviewed-by: Bin Meng <bmeng...@gmail.com> Should we add the kernel version that contains the fix? Or we assume the latest and greatest kernel should be used? Regards, Bin
