Re:Unikernels: Rise of the Virtual Library Operating System
by stormbrew on Monday January 13, 2014 @07:21PM
(#7054557)
As mentioned in a sibling you still have the hypercalls, and you definitely need those to still be present if you're running at ring 0 since, essentially, direct access to the hardware is probably an opportunity to attack the whole physical system (since hardware often has arbitrary bus access). Never mind the need to arbitrate access between multiple VMs.
And this is what I mean when I say that taken to its conclusion you're just reinventing processes.
I think this kind of performance claim needs to be solidly proven by something at least vaguely like a real running application to be taken as a given.
Re:Unikernels: Rise of the Virtual Library Operating System
by michaelmior on Monday January 13, 2014 @08:59PM
(#7054911)
Fair point. More benchmarks need to happen before it's obvious this is really a win. A real application would be nice. I'm biased because I worked on a similar idea myself and I've been waiting for this to come. I think it's a potential win now for running on public clouds.
However, as Docker PaaS gains popularity, that may be a better alternative. Only benchmarks will tell :)
Re:Unikernels: Rise of the Virtual Library Operating System
by justincormack on Tuesday January 14, 2014 @04:18AM
(#7056106)
What did you work on?
Re:Unikernels: Rise of the Virtual Library Operating System
by michaelmior on Tuesday January 14, 2014 @08:52AM
(#7056991)
A similar yet much simpler idea of porting some simple application code to MiniOS. Although I never ended up with anything of value.
Re:Unikernels: Rise of the Virtual Library Operating System
by cwzwarich on Monday January 13, 2014 @10:34PM
(#7055205)
You can use I/O virtualization to allow direct hardware access in a safe fashion, assuming that your CPU and peripherals support it.
Re:Unikernels: Rise of the Virtual Library Operating System
by stormbrew on Tuesday January 14, 2014 @06:02PM
(#7060423)
This isn't the attack I'm referring to. The peripherals themselves have, potentially at least, complete access to the bus through DMA, so being able to convince them to, say, write to an inappropriate physical address (say the hypervisor's kernel), could lead to a significant breach of the security model. As far as I know, no processor-level features actually protect against this.
Re:Unikernels: Rise of the Virtual Library Operating System
by wmf on Monday January 13, 2014 @06:48PM
(#7054430)
You've eliminated system calls but you have hypercalls; it's not clear whether this is faster than a container-based system that has system calls but no hypercalls.
Re:Unikernels: Rise of the Virtual Library Operating System
by michaelmior on Monday January 13, 2014 @07:05PM
(#7054497)
True. Of course one other advantage is that you can run a unikernel on a public cloud. You can of course run OS to serve as a host for containers on a public cloud, but then you have an additional layer of overhead.
You can achieve the isolation with jails and cgroups, but not the performance improvements.