#18071: Investigate building a haiku unikernel
----------------------------+----------------------------
Reporter: kallisti5 | Owner: nobody
Type: bug | Status: new
Priority: low | Milestone: Unscheduled
Component: System/Kernel | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Platform: All |
----------------------------+----------------------------
Comment (by pulkomandy):
If I understand these things correctly, an unikernel is a way to run a
single binary application inside a virtual machine. So I don't understand
the relation with Docker, which is not using a virtual machine at all.
And I also don't understand how running our kernel as an unikernel would
make sense, because then you have the kernel and... nothing else (since
this is a single process system).
The idea of unikernels is basically to statically link EVERYTHING: the
application, the C library, and the kernel into a single executable that
is able to boot on a machine. You cannot have multiple processes. So you
couln't use it to run app_server, registrar, net_server, etc in addition
to your app? How would that be useful for running Haiku apps on Linux?
If your goal is to run Haiku apps on Linux, I don't see why you would take
this approach (which requires special-compiling of basically everything)
instead of either a virtual machine, or an API compatibility layer (such
as our own libbe_build or something based on Cosmoe, V\OS, or Haiku-On-
Genode).
--
Ticket URL: <https://dev.haiku-os.org/ticket/18071#comment:6>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
