<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unikraft: Fast, Specialized Unikernels the Easy Way · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2104.12721/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2104.12721/feed.xml" rel="self" type="application/rss+xml" /><item><title>Unikraft: Fast, Specialized Unikernels the Easy Way — mentioned by nderjung</title><link>https://news.ycombinator.com/item?id=40354509</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.12721:40354509</guid><pubDate>Tue, 14 May 2024 12:31:22 GMT</pubDate><description>&lt;p&gt;Containers are perfect for build environments and for creating the root filesystem. The issue is that the kernel these days are super bulky and are intended for multi-user, multi-process environments. Running a container runtime on top just makes it worse when you&amp;#x27;re looking for &amp;quot;isolation&amp;quot;. This paper argues that when you build a extremely minimal kernel (i.e. ditch Linux entirely) and link your application against necessary bits of code to execute _as_ a VM, then you&amp;#x27;ll get better performance than a container and you&amp;#x27;ll get that isolation. This is in fact true based on performance studies…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.12721/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.OS</category></item><item><title>Unikraft: Fast, Specialized Unikernels the Easy Way — mentioned by nderjung</title><link>https://news.ycombinator.com/item?id=39907238</link><guid isPermaLink="false">urn:hackerpapers:mention:2104.12721:39907238</guid><pubDate>Tue, 02 Apr 2024 15:57:47 GMT</pubDate><description>&lt;p&gt;In fact this is not true with Linux. We did a study of this[0] and found that there are too many interdependencies between Linux kernel subsystems. The smallest, usable Linux kernel we test with sometimes is around 30MB. In comparison, compiling NGINX together with Unikraft results in a kernel size of under 2MB. This means that there is 28MB of kernel we didn&amp;#x27;t need or want. [0]: https://arxiv.org/abs/2104.12721 (See Figure 1)&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2104.12721/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.OS</category></item><item><title>Unikraft: Fast, Specialized Unikernels the Easy Way — HN submission</title><link>https://news.ycombinator.com/item?id=26954547</link><guid isPermaLink="false">urn:hackerpapers:submission:2104.12721:26954547</guid><pubDate>Tue, 27 Apr 2021 11:31:46 GMT</pubDate><description>&lt;p&gt;Unikraft – Fast, Specialized Unikernels&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;138 points; 72 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2104.12721/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.OS</category></item></channel></rss>
