Re: [Devel] Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)

[Sam Vilain <sam@vilain.net>]

On Fri, 2006-02-10 at 09:23 +0300, Vasily Averin wrote:
> >> <wishful thinking>
> >> I can see another extension to this functionality.  With appropriate 
> >> changes it might also be possible to have a container exist across 
> >> multiple computers using some cluster code for synchronization and 
> >> fencing.  The outermost container would be the system boot container, 
> >> and multiple inner containers would use some sort of network-
> >> container-aware cluster filesystem to spread multiple vservers across 
> >> multiple servers, distributing CPU and network load appropriately.
> >> </wishful thinking>
> > Yeah.  If you fudged/virtualised /dev/random, the system clock, etc you
> > could even have Tandem-style transparent High Availability.
> > </more wishful thinking>
> Could you please explain, why you want to virtualize /dev/random?

When checkpointing it is important to preserve all state.  If you are
doing transparent highly available computing, you need to make sure all
system calls get the same answers in the clones.  So you would need to
virtualise the entropy pool.

There are likely to be dozens of other quite hard problems in the way
first.  Like I said, wishful thinking :-).  

Sam.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/