shym

> Update, this should work on the [latest (staging) `kraft` version](https://github.com/unikraft/kraftkit/releases/tag/v0.9.2-91-g51efc052) By the way, I’m not sure I understood what you meant. It should work with that version of `kraft`...

First of all, thank you for your investigation! > As of why it fails, I dug deep enough to see that it fails at an `__atomic_fetch_add` called by a reference...

> you're interested in running Unikraft on R-Pi baremetal? Less ambitiously, I was testing it with qemu-kvm on a raspberry pi. That’s how I ended up with telling qemu to...

For the record, I tried to compile explicity for the Cortex A53 (`CONFIG_MCPU_ARM64_CORTEX_A53=y`) instead of the default target: - I had to disable `ukrandom` (as it failed to compile) and...

The [log](https://github.com/shym/unikraft-simple/actions/runs/11363132987/job/31606422658#step:5:2713) of the build ends with: ``` /usr/lib/gcc-cross/aarch64-linux-gnu/13/../../../../aarch64-linux-gnu/bin/ld: /home/runner/work/unikraft-simple/unikraft-simple/.unikraft/build/libukrandom.o: in function `uk_swrand_init': /home/runner/work/unikraft-simple/unikraft-simple/.unikraft/unikraft/lib/ukrandom/chacha.c:176:(.text+0x2c): undefined reference to `ukarch_random_u32' /home/runner/work/unikraft-simple/unikraft-simple/.unikraft/unikraft/lib/ukrandom/chacha.c:176:(.text+0x2c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `ukarch_random_u32' /usr/lib/gcc-cross/aarch64-linux-gnu/13/../../../../aarch64-linux-gnu/bin/ld: /home/runner/work/unikraft-simple/unikraft-simple/.unikraft/build/libukrandom.o:...

I investigated a bit more what happens with the failing build, trying to enable this time `MCPU_ARM64_GENERIC` instead of a specific Cortex. `lib-lwip` force-enables `LIBUKRANDOM` which force-enables `HAVE_RANDOM`. When `HAVE_RANDOM`...

Thank you for the ping, I had missed the new release. I finally found the time to test this. By configuring the unikernel to target a generic ARM but disabling...

Thank you for the pointers. How to properly setup interrupt handling on x86_64 is quite some rabbit hole! To sum up what I learnt: - switching stack automatically on interrupt...

I’ve rebased on `main` (cc @palainp) and added a few small fixes (left explicitly as `fixup!...` commits for now, to make it easier to resync for reviews that were already...

I dug deeper into the usage of `mmap` in the OCaml code base and got reassured: if I understand correctly, `mmap` is used with a (non-`NULL`) address only with `MAP_FIXED`...