| |||||||||||||
And THAT is the problemAnd THAT is the problemPosted Aug 23, 2011 17:19 UTC (Tue) by bronson (subscriber, #4806)In reply to: And THAT is the problem by raven667 Parent article: HP dropping webOS devices
I don't think this is true. Microkernels are a collection of OS processes interacting to provide a rich interface to userland (file systems, networking stack, IPC, etc), while hypervisors don't intend to provide OS services at all. They're just a thin hardware abstraction layer so that multiple operating systems (microkernel or not) can be fooled into coexisting and maybe some very coarse resource management.
Like atoms vs. the solar system, they might look similar if you look from afar. It's certainly possible to cherry-pick theoretical similarities. For real-world work, though, they tend to be quite different.
(Log in to post comments)
And THAT is the problem Posted Aug 25, 2011 20:37 UTC (Thu) by raven667 (subscriber, #5198) [Link]
I was thinking that the combination of the hypervisor and the guest kernel in total formed the microkernel. Each guest has its own personality and file systems, network, ipc, etc. Information is passed back and forth through the hypervisor using interfaces that happen to look a lot like network cards and block devices, or use PV drivers which can do pure message passing. The big thing is that every bit runs in its own protected memory space which I thought was the big difference and value of a microkernel vs. a traditional kernel.
Like you said, I'm certainly standing from afar and squinting more than a little. 8-)
|
|||||||||||||