I think the biggest problem with Unikernels that I haven't seen addressed is hypervisor inefficiency.

I think the biggest problem with Unikernels that I haven't seen addressed is hypervisor inefficiency. Emulating any part of a kernel or multiple kernels will just be slower. You have 20 guests on your hosts? That's 20 probably-overlapping (uni)kernels running. Sure you could optimize the heck out of the hypervisor, but now you've created a kernel. And your applications run on that kernel. With containers, you have one kernel that won't have to instantiate 20 drivers for the disk subsystem. It can be smarter because it knows more about the loads. It's what kernels have been built to do since day 0. My main concern with unikernels is that eventually the hypervisor will need to be a kernel to be any more optimized. I just worry it will be come something of a self-defeating concept.

Posted by andrewstuart2 on Nov 14, 2014, 9:22 PM

Tags

• hackernews (Other)

Related issues

• Not sure what you suggest to do.
• Why is this not yet published on the official website and why is there no CVE?
• The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained&#x2...
• The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
• (My comment is about detached houses).
• The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...