WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] Blktap: Userspace file-based image support.(RFC)

To: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Blktap: Userspace file-based image support.(RFC)
From: Dan Smith <danms@xxxxxxxxxx>
Date: Fri, 30 Jun 2006 07:17:26 -0700
Cc: Julian Chesterfield <julian.chesterfield@xxxxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, NAHieu <nahieu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andrew Warfield <andrew.warfield@xxxxxxxxxxxx>
Delivery-date: Fri, 30 Jun 2006 07:18:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1151674861.7893.5.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> (Stephen C. Tweedie's message of "Fri, 30 Jun 2006 14:41:01 +0100")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D4BAB1A@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <m3psh3pm7t.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1151674861.7893.5.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
SCT> It depends on the environment.  To support cold/live migration,
SCT> having network-attached storage will be required; and file images
SCT> on NFS would be an extremely simple-to-setup way to achieve that.

Ah, but block devices can play too.  With dm-userspace, we could
migrate a domain from one machine to another, faulting the needed
blocks from its block devices on-demand, and copying the rest in the
background.  This would give us a peer-to-peer setup where block
devices could slowly move from machine to machine, following its
owner.  Once your block was accessed (or copied in the background),
it's local and fast.  A peer-to-peer NAS setup.

What do you think?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx

Attachment: pgpMLE17HttGI.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel