On Thu, May 25, 2023 at 08:32:46PM +0530, Sunil V L wrote: > On Thu, May 25, 2023 at 01:43:28PM +0000, Andrea Bolognani wrote: > > I have also tried booting an openSUSE Tumbleweed "JeOS" image, since > > that's the only distro I'm aware of that uses UEFI boot on RISC-V at > > this point - though they use U-Boot's UEFI support rather than edk2. > > > > During that attempt, I ended up in the edk2 shell. Running > > > > fs0:\efi\boot\bootriscv64.efi > > > > brings up GRUB just fine, but selecting the default boot entry > > results in > > > > Loading Linux 6.3.2-1-default ... > > Loading initial ramdisk ... > > EFI stub: Booting Linux Kernel... > > EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path > > EFI stub: Generating empty DTB > > EFI stub: Exiting boot services... > > > > being printed, after which it's back to OpenSBI and from there to > > edk2 again. > > Thanks!. Please add -machine acpi=off in qemu command to boot the > kernel.
Yup, that worked! It booted all the way to the login prompt :) Note that libvirt automatically adds acpi=off, so that won't be a concern for libvirt users. > > > > Going further and testing libvirt integration. After hacking around > > > > other issues, I finally stumbled upon this error: > > > > > > > > qemu-system-riscv64: Property 'virt-machine.pflash0' not found > > > > > > Thanks!. This needs some investigation. Let me look into supporting > > > this. > > > > Yes please! It's critical to libvirt integration. Feel free to CC me > > when you post patches and I'll gladly test them. > > Sure, I have the fix ready. I need to convert this into a patch series > now. Will send it soon and thanks in advance for helping with testing. Excellent! Looking forward to it :) -- Andrea Bolognani / Red Hat / Virtualization
