2 ms·
Keep in mind Xen is bloated beyond belief, and all of this bloat is running in supervisor mode. It being an actual type 1 hypervisor makes it significantly bett
by snvzz 9y ago
Keep in mind Xen is bloated beyond belief, and all of this bloat is running in supervisor mode. It being an actual type 1 hypervisor makes it significantly better than approaches such as Linux KVM or freebsd bhyve, but the TCB is still too big.
A better approach is to run the VMM (which handles VM exceptions) as a normal user process under a microkernel. seL4 implements such an approach, with the added benefits of capabilities; the VMM doesn't get any more privileges than it actually needs, thus a successful attack against the VMM from within the VM could not actually provide anything beyond what supervisor mode execution within the VM would.
A lot more on this to be found here: https://ts.data61.csiro.au/projects/TS/virtualisation/ https://ts.data61.csiro.au/projects/TS/virtualisation/
More papers (not restricted to virtualization): https://ts.data61.csiro.au/projects/TS/publications.pml https://ts.data61.csiro.au/projects/TS/publications.pml
And, while at it, I also recommend reading Gernot Heiser's blog, which has plenty on this. https://microkerneldude.wordpress.com/ https://microkerneldude.wordpress.com/
- xelxebar 9y agoInteresting. I my knowledge of hypervisors and virtualization is quite superficial. What makes Xen so bloated? The seL4 kernel has piqued my interest a lot. Though, shamefully, I have to admit the interest isn't backed by many technical reasons. I'm on a vague, pesonal quest to run as minimal a system (both hardware and software) as possible while also keeping things as secure as possible. seL4 hits both those buttons, philosophically. Thanks for the links. This gives some good places to turn my interest into actual knowledge.
- snvzz 9y ago>What makes Xen so bloated? Size, in kLOC, of the hypervisor itself, which runs entirely in supervisor mode and, as such, is part of the TCB.