Unable to boot the sample hello project on ubuntu machine.

[AshwinKrishn]

Hello All ,

I am trying to boot an AMD64 and ARM64 machine using fiasco. The Fiasco and L4 build works fine. We are able to generate the final elf also successfully. However the QEMU is unable to boot the machine. IT just freezes at startup with the comment "ROM booting".

1. Fiasco building successfully

2. L4 runtime built successfully

3. Able to give boot command. However the system requires video card. So I moved to my Linux laptop and observed that the system boots beyond this error, but is not printing hello world.

In my local laptop it just says booting from ROM and freezes.

Is there an alternate instruction for booting examples for ARM64 and AMD64 ?

[jermar]

Yes, it appears to me that you have used the L4Re snapshot, which is not necessarily a bad thing, but you may be more on your own then than with the GitHub release.

I would therefore suggest you try using the L4Re public release on GitHub and the build and usage tutorials written for it at:

• https://github.com/kernkonzept/manifest/wiki

In particular, here is the Building L4Re tutorial which also includes a section on starting hello on ARM build of L4Re in QEMU:

• https://github.com/kernkonzept/manifest/wiki/BUILDING

If you follow the tutorial and run into an issue, reporting the issue and the exact step where the tutorial failed for you will make it easier for us to figure out what went wrong.

In addition, I wasn't able to figure out what went wrong from your description as the interesting screenshot was not linked from it, neither what was the host platform.

Next time, it would be useful to have the actual command line and bootscreen which failed and also the output of 'make report' run in the build-arm or build-x86_64 directory.

Lastly, note that QEMU can be passed various options such as "-nographic" and "-display none" that can be used for running L4Re over a serial console instead of a graphical display.

[jermar]

Closing due to inactivity and as a possible configuration issue on the side of the reporter.