[haiku-bugs] Re: [Haiku] #18071: Investigate building a haiku unikernel
- From: "Haiku" <trac@xxxxxxxxxxxx>
- To: undisclosed-recipients: ;
- Date: Thu, 17 Nov 2022 16:21:48 -0000
#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 kallisti5):
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.
I think this needs shifted a little. The idea is a running operating
system can boot a unikernel application directly. aka, the linux kernel
hands off a dedicated CPU and memory space temporarily to a unikernel
binary. At that point, the binary can function fully off the ABI of the
unikernel with some basic (likely virtio style?) i/o devices.
You can boot unikernel applications directly on "currently running
hardware" or, you can boot them self-contained within a VM.
It's a wild concept, but represents a desire to get applications closer to
bare metal. I think the most "correct" alignment is paravirtualization
with the focus being offering a kernel + abi for a single application.
If we offer a command line and a base chroot, we could theoretically build
applications on linux in containers, under the Haiku chroot + Haiku
kernel.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/18071#comment:7>
Haiku <
https://dev.haiku-os.org>
The Haiku operating system.
Other related posts:
