3 ms·
I can't seem to shake the first thought i had when reading about unikernels. That they are DOS in a VM. Maybe it is overly simplified, but as i understand it w
by digi_owl 12y ago
I can't seem to shake the first thought i had when reading about unikernels. That they are DOS in a VM.
Maybe it is overly simplified, but as i understand it we are looking at a "kernel" stripped down to handling the disk and network interfaces provided by the VM. No user separation (there is only a single "user"), no memory protection (it is only running a single process as best i can tell), and resource provisioning is done by the VM.
- vog 12y agoThe point is that you only run a single application in the VM anyway. And if you do that, you should make your VM as slick as possible, because anything in there that doesn't serve your application is just increasing the attack surface and the probability of errors through side effects. That's what is already done today, and unikernels are just the natural progression towards that goal. So you essentially don't separate your applications via users within your OS, but via VMs in your hypervisor. Not sure if this turns out to be a good idea or not, but it's an interesting approach that shouldn't be put down easily.
- digi_owl 12y agoYeah i may be coming across as overly dismissive.