Re:OSv – Linux binary compatible unikernel for virtualized e...
by dis-sys on Sunday December 13, 2020 @06:54AM
(#25405937)
Interesting project. Just wondering is there any ongoing effort to somehow allow users to build a minimum linux kernel that is just enough to support a specified application?
[ Parent
| on HN ]
Re:OSv – Linux binary compatible unikernel for virtualized e...
by orumin on Sunday December 13, 2020 @07:06AM
(#25406004)
There is project what you say, that's name "Lupine".
paper: https://dl.acm.org/doi/abs/10.1145/3342195.3387526 code: https://github.com/hckuo/Lupine-Linux
Re:OSv – Linux binary compatible unikernel for virtualized e...
by dis-sys on Wednesday December 16, 2020 @01:17AM
(#25439655)
very cool stuff, thanks for sharing
Re:OSv – Linux binary compatible unikernel for virtualized e...
by IfOnlyYouKnew on Sunday December 13, 2020 @09:58AM
(#25406969)
I did once spend a few boring hours on a plane on a genetic-algorithm-based optimiser that (tried to) minimise a Linux image (I believe I used Gentoo), eliminating packages first, followed by files, segments, and individual lines of code.
From what I remember, (a) you can probably get to an extremely low size, (b) it won't be worth it compared to similar efforts taking a different route and getting 90 % there, because (c) your test will never be sufficient for any real-world usage: I remember going through some of the codepaths that had been disabled, and it included handling of specific dates, any unicode character I had not used, handling of networking and disk access failures that I did not even know of, etc.
Re:OSv – Linux binary compatible unikernel for virtualized e...
by carapace on Sunday December 13, 2020 @11:54AM
(#25407911)
That's pretty awesome! Did you write it up anywhere?
Re:OSv – Linux binary compatible unikernel for virtualized e...
by ttul on Sunday December 13, 2020 @11:57AM
(#25407953)
I suppose you could profile your app, watching the syscalls it makes over a full cycle, and then build a stripped kernel with nothing but those calls implemented. Any drivers not touched would also be removed. That would not eliminate the syscall overhead, but it would certainly minimize boot time and improve security somewhat by reducing the attack surface.