3 ms·
The problem with Unikernels is that there is no middle ground between a button smashing user and a kernel hacker. If you open the hood everything is part of the
by crest 3y ago
The problem with Unikernels is that there is no middle ground between a button smashing user and a kernel hacker. If you open the hood everything is part of the kernel and most (all?) existing examples of Unikernels lack proper tracing and debugging support. It will feel like debugging an eight bit MCU (printf() and GPIO writes) running a far larger (and complex) code base through upward emulation.
- eyberg 3y agoThis is a rather old and incorrect talking point. Nanos has had strace/ftrace/gdb, plenty of apm/monitoring such as cloudwatch and all sorts of tools in/around that realm for years now. https://docs.ops.city/ops/debugging https://docs.ops.city/ops/debugging https://nanovms.com/dev/tutorials/using-netconsole-for-debug-logging-unikernels https://nanovms.com/dev/tutorials/using-netconsole-for-debug... https://nanovms.com/dev/tutorials/debugging-unikernels-using-new-native-tfs-tools https://nanovms.com/dev/tutorials/debugging-unikernels-using... https://nanovms.com/dev/tutorials/profiling-unikernel-syscall-execution-time https://nanovms.com/dev/tutorials/profiling-unikernel-syscal... https://nanovms.com/dev/tutorials/debugging-nanos-unikernels-with-gdb-and-ops https://nanovms.com/dev/tutorials/debugging-nanos-unikernels... https://nanovms.com/dev/tutorials/profiling-and-tracing-nanos-unikernel https://nanovms.com/dev/tutorials/profiling-and-tracing-nano...
- fhuici 3y agoActually this isn't a fundamental issue with unikernels, but rather an implementation one. For instance, check out debugging in Unikraft: https://unikraft.org/docs/internals/debugging https://unikraft.org/docs/internals/debugging .
- pjmlp 3y agoA matter of tooling, nothing related to unikernels.