From: "Michael Paesold" Subject: Re: [PATCH] External device migration support Date: Mon, 27 Mar 2006 15:31:08 +0200 Message-ID: <036701c651a2$b5123920$e101a8c0@zaphod> References: <1143149234.6648.19.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan Berger , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Stefan Berger wrote: > This patch enables external devices, such as for example a mounted hard > drive image or a TPM, to be migrated to a remote machine. The patch > hooks into the checkpointing (XendCheckpoint.py) code and performs > migration in 4 different steps: ... > Please let me know what you think about this idea. I really like the idea because it seems to work for any external device that can be migrated but does not allow concurrent access from both migration source and destination. I have not looked at the patch in detail, but I saw the specific inclusion of +# The tool used for initiating virtual TPM migration +#(vtpm-migration-tool '') Could this migration tool specification be more generalized so that any device migration can be configured, not just vtpm devices? Best Regards, Michael Paesold