Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932340AbWBKRbP (ORCPT ); Sat, 11 Feb 2006 12:31:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932337AbWBKRbP (ORCPT ); Sat, 11 Feb 2006 12:31:15 -0500 Received: from mailhub.sw.ru ([195.214.233.200]:37640 "EHLO relay.sw.ru") by vger.kernel.org with ESMTP id S932340AbWBKRbP (ORCPT ); Sat, 11 Feb 2006 12:31:15 -0500 Message-ID: <43EE1EDE.6040809@sw.ru> Date: Sat, 11 Feb 2006 20:29:02 +0300 From: Vasily Averin Organization: SW-soft User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050921 X-Accept-Language: en-us, en, ru MIME-Version: 1.0 To: Sam Vilain CC: devel@openvz.org, Kyle Moffett , Andrew Morton , Kirill Korotaev , frankeh@watson.ibm.com, Andrey Savochkin , Rik van Riel , greg@kroah.com, Linux Kernel Mailing List , Linus Torvalds , "Eric W. Biederman" , Pavel Machek , Alexey Kuznetsov , serue@us.ibm.com, alan@lxorguk.ukuu.org.uk, arjan@infradead.org Subject: Re: [Devel] Re: swsusp done by migration (was Re: [RFC][PATCH 1/5] Virtualization/containers: startup) References: <43E38BD1.4070707@openvz.org> <43E3915A.2080000@sw.ru> <43E71018.8010104@sw.ru> <1139243874.6189.71.camel@localhost.localdomain> <20060208215412.GD2353@ucw.cz> <7CCC1159-BF55-4961-BC24-A759F893D43F@mac.com> <43EC170C.6090807@vilain.net> <43EC317C.9090101@sw.ru> <1139625499.12123.41.camel@localhost.localdomain> In-Reply-To: <1139625499.12123.41.camel@localhost.localdomain> X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1192 Lines: 29 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. >>> >>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 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/