Hi Qiang, thanks for the great feedback.
It's correct, the L4Re microerkernel Fiasco runs in EL2 only. It runs both VMs and L4Re applications side by side, so yes, it is a hypervisor too. Best regards, Adam On Tue Jan 07, 2025 at 19:34:20 +0800, qiang xu wrote: > Hi Adam, > > Thank you very much for your support. The explanation was very clear. From > the printed information, it seems to be running fine. I have one more > question: Can Fiasco be used as a hypervisor? From the example of > l4re_VM-multi, it seems to have the ability to run multiple operating > systems on a single platform, and in L4Re, only Fiasco runs in EL2 > privilege level. I'm not sure if I understand this correctly, so I wanted > to confirm with you. If it cannot be used as a hypervisor, what > functionality does it lack that a hypervisor would typically have? > > Regards, > Qiang > > > On Tue, Jan 7, 2025 at 7:53 AM Adam Lackorzynski <[email protected]> wrote: > > > Hi Qiang, > > > > If I'm not mistaken, the provided BSP is using u-boot. With u-boot, the > > uimage file is a good fit. When booting up, you can stop at the u-boot > > prompt and do something like this: > > # fatload mmc 0 0x80f00000 fsl-s32g274a-evb.dtb > > # fatload mmc 0 0x80ffffc0 l4re_vm-multi-p2p_s32g.uimage > > # bootm 0x80ffffc0 - 0x80f00000 > > > > You need to copy the l4re_vm-multi-p2p_s32g.uimage file to the mmc first > > of course, for example, through Linux. > > Alternative you could also load the elf-image or raw-image into memory > > via your hardware debugger, whatever method the debugger supports. Do it > > by intercepting at the u-boot prompt. > > > > A third option is to use the tftp network capabilities of u-boot to load > > the uimage via network. > > > > > > > > Adam > > > > On Mon Jan 06, 2025 at 11:04:35 +0800, qiang xu wrote: > > > Hi Adam, > > > > > > Thank you for your response. > > > > > > I found the following images in the L4Re pre-built images folder: > > > “l4re_vm-multi-p2p_s32g.efi,” “l4re_vm-multi-p2p_s32g.elf,” and > > > “l4re_vm-multi-p2p_s32g.uimage.” I would like to understand how these > > > images can be combined with the BSP built using Yocto and placed on the > > SD > > > card for booting. > > > > > > I have been following the examples from the L4Re wiki > > > <https://github.com/kernkonzept/manifest/wiki/MultipleVMs> to get > > started > > > with L4Re. These examples run very well on QEMU, but there is an issue—I > > am > > > unable to use GDB to debug the Fiasco kernel.I noticed that L4Re can also > > > run on the S32G platform, so I would like to run L4Re on S32G and use a > > > hardware debugging tool to debug the Fiasco kernel during its execution. > > > However, the wiki does not provide instructions on how to run L4Re on > > real > > > hardware.Therefore, I would like your guidance on how to run the examples > > > from the wiki <https://github.com/kernkonzept/manifest/wiki/MultipleVMs> > > on > > > the S32G platform and boot from an SD card. > > > > > > Regards, > > > Qiang > > > > > > On Mon, Jan 6, 2025 at 9:56 AM Adam Lackorzynski <[email protected]> wrote: > > > > > > > Hi Qiang, > > > > > > > > On Sat Jan 04, 2025 at 17:03:21 +0800, qiang xu wrote: > > > > > I would like to know how to run L4Re on the S32G. I couldn’t find any > > > > > related documentation. I’m a beginner in this technical field, so > > could > > > > you > > > > > provide friendly step-by-step instructions? > > > > > > > > One option is to use the snapshot from l4re.org as it has a > > menu-driven > > > > target selection which includes the S32G. This hides quite a few of the > > > > details but gives examples for the S32G right away. > > > > How do you boot your S32G? _______________________________________________ l4-hackers mailing list -- [email protected] To unsubscribe send an email to [email protected]
