:That's what I was saying: It's a debugging tool to develop a driver,
:and once it's done, it can just be loaded into the host kernel
:instead of the virtual kernel. If that virtual kernel is there for the
:express purpose of hosting drivers and not untrusted processes and
:users, then security
:One question I am surprised not to find asked is: how do virtual
:kernels work on SMP systems? A layered question I suppose; how would
:the virtual kernel itself scale, and also how would its processes
:scale, and how would the threads of those processes scale? The first
:thing I think when I
On 1/28/07, Matthew Dillon [EMAIL PROTECTED] wrote:
No. Frankly I do not think it is a good idea to allow any
production virtualization mechanism to ever have direct access
to hardware. It destroys the layering that gives virtualization
stability and security... no matter how
One question I am surprised not to find asked is: how do virtual
kernels work on SMP systems? A layered question I suppose; how would
the virtual kernel itself scale, and also how would its processes
scale, and how would the threads of those processes scale? The first
thing I think when I hear of
I'd like to write a quick news article about the virtual kernel support. I
haven't used it myself yet.
I have a few questions for my article. Feel free to email me off-list by
Monday morning. (And I will try to publish and promote/submit the article
by Tuesday morning.)
What existing
:I'd like to write a quick news article about the virtual kernel support. I
:haven't used it myself yet.
:
:I have a few questions for my article. Feel free to email me off-list by
:Monday morning. (And I will try to publish and promote/submit the article
:by Tuesday morning.)
:
:What existing