3 ms·
All the replies so far miss amluto's point: A unikernel running on a hypervisor is a process, just with an awkward syscall interface and inflexible memory manag
by rwmj 9y ago
All the replies so far miss amluto's point: A unikernel running on a hypervisor is a process, just with an awkward syscall interface and inflexible memory management. Especially when the hypervisor is KVM which runs VMs as regular Linux processes, this is very clear.
- eeZah7Ux 9y ago> A unikernel running on a hypervisor is a process, just with an awkward syscall interface and inflexible memory management. ...and with no way to run ancillary scripts and cronjobs e.g. log management, backups, security tools... Nor ssh into the VM to inspect it and run debuggers or monitoring and metric agents. Essentially you are giving away all the practical advantages of modern OSes. There's a reason why the usual famous tech companies don't use unikernels, generally speaking.
- anonymousDan 9y agoNot the case, Google for example are looking at using the Linux Kernel Library: https://netdevconf.org/1.2/session.html?jerry-chu https://netdevconf.org/1.2/session.html?jerry-chu
- mato 9y agoVM interfaces are awkward due to emulating hardware so that they can run existing operating systems. A VT-backed unikernel interface does not need to inherit this awkwardness. As for memory management, in the Solo5/ukvm case the amount of memory you grant to the guest (monitor process) is essentially the maximum you expect the guest to need, ever. So it's similar in terms of overhead to many usermode allocators which just mmap() a huge block of memory at start and then hand out to the application from that.
- amscanne 9y agoThat's how a regular KVM works as well (mmap a physical memory block) and the mismatch comes from the fact that all the regular OS memory management mechanisms -- reclaim, swap, page cache, etc. -- are all broken by the abstraction provided. FV guests can similarly have a balloon driver, that doesn't mean the interface isn't awkward.