From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NA5nR-00035x-GD
	for qemu-devel@nongnu.org; Mon, 16 Nov 2009 12:55:25 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NA5nM-0002xf-93
	for qemu-devel@nongnu.org; Mon, 16 Nov 2009 12:55:24 -0500
Received: from [199.232.76.173] (port=40125 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NA5nM-0002xL-2T
	for qemu-devel@nongnu.org; Mon, 16 Nov 2009 12:55:20 -0500
Received: from mail-qy0-f194.google.com ([209.85.221.194]:33911)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NA5nL-00036j-P2
	for qemu-devel@nongnu.org; Mon, 16 Nov 2009 12:55:19 -0500
Received: by qyk32 with SMTP id 32so2492363qyk.4
	for <qemu-devel@nongnu.org>; Mon, 16 Nov 2009 09:55:18 -0800 (PST)
Message-ID: <4B019203.7030308@codemonkey.ws>
Date: Mon, 16 Nov 2009 11:55:15 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] QEMU redesigned for MPI (Message Passing Interface)
References: <747a56b80911130629q4046b4fbg400f7566997aa931@mail.gmail.com>
In-Reply-To: <747a56b80911130629q4046b4fbg400f7566997aa931@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Victor Vasilchenko <vvasilchenko@gmail.com>
Cc: qemu-devel@nongnu.org

Victor Vasilchenko wrote:
> Good day,
>
> I've got an idea in my head and can't get rid of it - neither can I 
> find any solution on web.
>
> The idea is to use the Virtualization Software with the purpose 
> OPPOSITE to it's natural way.
>
> The practical example below will explain it completely:
>
> 1) we take 4 common modern computers - CoreQuad + 8 GB Memory.
> 2) we assemble a standard Linux cluster with 16 cores and 32G memory.
> 3) and now - we run the only one virtual guest system, but give it ALL 
> available resources.

What you're describing is commonly referred to as a Single System 
Image.  It's been around for a while and can be found in software-only 
verses (pre-Xen VirtualIron, ScaleMP) and hardware-assisted (IBM, 3leaf).

Regards,

Anthony Liguori