Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751071AbWBJEbV (ORCPT ); Thu, 9 Feb 2006 23:31:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751077AbWBJEbV (ORCPT ); Thu, 9 Feb 2006 23:31:21 -0500 Received: from watts.utsl.gen.nz ([202.78.240.73]:23966 "EHLO mail.utsl.gen.nz") by vger.kernel.org with ESMTP id S1751071AbWBJEbU (ORCPT ); Thu, 9 Feb 2006 23:31:20 -0500 Message-ID: <43EC170C.6090807@vilain.net> Date: Fri, 10 Feb 2006 17:31:08 +1300 From: Sam Vilain User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kyle Moffett Cc: "Eric W. Biederman" , Pavel Machek , Dave Hansen , Kirill Korotaev , Linus Torvalds , Kirill Korotaev , Andrew Morton , Linux Kernel Mailing List , frankeh@watson.ibm.com, clg@fr.ibm.com, greg@kroah.com, alan@lxorguk.ukuu.org.uk, serue@us.ibm.com, arjan@infradead.org, Rik van Riel , Alexey Kuznetsov , Andrey Savochkin , devel@openvz.org, Pavel Emelianov Subject: 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> In-Reply-To: <7CCC1159-BF55-4961-BC24-A759F893D43F@mac.com> X-Enigmail-Version: 0.92.1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1055 Lines: 24 Kyle Moffett wrote: > > 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. > Yeah. If you fudged/virtualised /dev/random, the system clock, etc you could even have Tandem-style transparent High Availability. Actually there is relatively little difference between a NUMA system and a cluster... 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/