[GSoC] Virtualization Using Hurd Mechanisms

[Pierre Thierry]

Hi all,

this year I applied for a slot in Google's Summer of Code on the
Hurd[1], to tackle virtualization à la Hurd. As I currently have no
other commitments during the summer, I will be able work on this
project between half-time and full-time, during the whole summer.

  1. 
http://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2012/nowhereman/1

As I describe it in my application, I'll start from user stories (or
scenarii). I have a few in mind, but if you have your own ideas, I'll
take them gladly; the more the merrier, and foremost, the more stories
I get, the least I risk missing an important piece of requirement for
the tool.

My main user stories are:

  1. I create a virtualized Hurd, able to communicate with the outside
    world in the same way the parent Hurd can (option: cannot
    communicate at all)

  2. I create a few virtualized Hurds and they are able to communicate
     between themselves and the parent Hurd only

  3. I create a minimalist virtualized Hurd, with the bare minimum
     needed to run a program (option: with the ability to add features
     to the virtualized Hurd on demand)

Funny thing is, I almost started writing Hurd0 for parent Hurd, and I
immediately realized one of the huge advantages of Hurd against
paravirtualization: a virtualized Hurd can be the parent Hurd for
another virtualized Hurd. It's turtles all the way down!

Story #3 is basically a POLA launcher and the option is a powerbox.

Tentatively,
Pierre
-- 
pierre@nothos.net
OpenPGP 0xD9D50D8A

signature.asc
Description: Digital signature