From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [PATCH 2/10] Allow the monitor to be suspended during non-blocking op
Date: Wed, 10 Sep 2008 16:58:32 +0100
Message-ID: <20080910155831.GA30342@shareable.org>
References: <1220989802-13706-1-git-send-email-aliguori@us.ibm.com> <1220989802-13706-3-git-send-email-aliguori@us.ibm.com> <48C76EB1.6040906@qumranet.com> <20080910100520.GE2662@redhat.com> <48C7AB7C.30407@qumranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	Chris Wright <chrisw@redhat.com>,
	Uri Lublin <uri.lublin@qumranet.com>,
	Anthony Liguori <aliguori@us.ibm.com>, kvm@vger.kernel.org
To: qemu-devel@nongnu.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail2.shareable.org ([80.68.89.115]:47872 "EHLO
	mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752216AbYIJP6y (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 10 Sep 2008 11:58:54 -0400
Content-Disposition: inline
In-Reply-To: <48C7AB7C.30407@qumranet.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Avi Kivity wrote:
> (logically we would copy all of the data of all block devices, but 
> that's not very practical, so we assume shared storage).

Speaking of that, if the guest RAM were a memory-mapped file, couldn't
that use shared storage too?

You'd have to be careful: it would need a distributed filesystem with
coherent mappings (i.e. not NFS), but they do exist.

I'm guessing that the bulk of time spent in migration/checkpointing is
saving the RAM image.  Using a memory-mapped file on shared storage
for RAM might make that faster.  (Or slower!).

-- Jamie