<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Restoring Uniqueness in MicroVM Snapshots · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2102.12892/</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/2102.12892/feed.xml" rel="self" type="application/rss+xml" /><item><title>Restoring Uniqueness in MicroVM Snapshots — mentioned by mjb</title><link>https://news.ycombinator.com/item?id=32684658</link><guid isPermaLink="false">urn:hackerpapers:mention:2102.12892:32684658</guid><pubDate>Thu, 01 Sep 2022 23:20:25 GMT</pubDate><description>&lt;p&gt;It&amp;#x27;s always great to see different ways folks are using Firecracker. Snapshot-and-restore is a particularly cool capability, especially if you solve the data movement problems (like these folks have). One challenge to clone-and-restore that they don&amp;#x27;t talk about here is making sure that clones don&amp;#x27;t behave too similarly (like returning the same cryptographic random numbers). We wrote a paper about that a while back (https://arxiv.org/abs/2102.12892), and the Linux kernel community has been doing some great work in that area recently too.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2102.12892/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Restoring Uniqueness in MicroVM Snapshots — mentioned by mjb</title><link>https://news.ycombinator.com/item?id=31184906</link><guid isPermaLink="false">urn:hackerpapers:mention:2102.12892:31184906</guid><pubDate>Wed, 27 Apr 2022 19:53:04 GMT</pubDate><description>&lt;p&gt;That&amp;#x27;s a good question! Accelerating cold starts with checkpoint and restore is a good idea. There&amp;#x27;s been a lot of research in academia around it, and some progress in industry too. It&amp;#x27;s one of those things, though, that works really well for specific use-cases or at small scale, but take a lot of work to generalize and scale up. For example, one challenge is making sure that random number generators (RNGs) don&amp;#x27;t ever return the same values ever after cloning (because that completely breaks GCM mode, for example). More details here: https://arxiv.org/abs/2102.12892 As for CRIU specifically…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2102.12892/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
