Hi. It looks great! Since it uses UML, it overcomes the current limitation of LKL Nabla that does not support multi process.
As I described in the next post, Solo5 support in frankenlibc relies on platform abstract layer s (platforms, franken, librumpuser). However, UML deeply depends on arch/x86 and it would be hard to apply LKL Nabla approach directly. I hope it will be much easier if LKL is unified to UML.
Hi. It looks great! Since it uses UML, it overcomes the current limitation of LKL Nabla that does not support multi-process.
Thanks! Although being multi-process makes it not-unikernel like, and it's more like a regular (although limited) VM.
I hope it will be much easier if LKL is unified to UML.
Got it, thanks. Let's wait until that merge is complete then.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi. It looks great! Since it uses UML, it overcomes the current limitation of LKL Nabla that does not support multi process.
As I described in the next post, Solo5 support in frankenlibc relies on platform abstract layer s (platforms, franken, librumpuser). However, UML deeply depends on arch/x86 and it would be hard to apply LKL Nabla approach directly. I hope it will be much easier if LKL is unified to UML.