Sam Vilain wrote: > On Fri, 2006-02-10 at 09:23 +0300, Vasily Averin wrote: >>>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. >From my point of view it is important to preserve only all the determinated state. Ok, lets we've checkpointed and saved current entropy pool. But we have not any guarantee that pool will be in the same state at the moment of first access to it after wakeuping. Because a new entropy can change it unpredictable. Am I right? Thank you, Vasily Averin Virtuozzo Linux kernel Team - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [RFC][PATCH 1/5] Virtualization/containers: startup
- From: Kirill Korotaev <[email protected]>
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: Linus Torvalds <[email protected]>
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: Kirill Korotaev <[email protected]>
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: Linus Torvalds <[email protected]>
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: [email protected] (Eric W. Biederman)
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: Kirill Korotaev <[email protected]>
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: [email protected] (Eric W. Biederman)
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: Dave Hansen <[email protected]>
- Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- From: [email protected] (Eric W. Biederman)
- swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- From: Pavel Machek <[email protected]>
- Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- From: [email protected] (Eric W. Biederman)
- Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- From: Kyle Moffett <[email protected]>
- Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- From: Sam Vilain <[email protected]>
- Re: [Devel] Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- From: Vasily Averin <[email protected]>
- Re: [Devel] Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- From: Sam Vilain <[email protected]>
- [RFC][PATCH 1/5] Virtualization/containers: startup
- Prev by Date: Re: [PATCH] IPv6: Cleanups for net/ipv6/addrconf.c (kzalloc, early exit) v2
- Next by Date: Re: [PATCH] percpu data: only iterate over possible CPUs
- Previous by thread: Re: [Devel] Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- Next by thread: Re: [Devel] Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup)
- Index(es):