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/
Home Products Support Community News


Re: [Xen-devel] A migration framework for external devices

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] A migration framework for external devices
From: "Mike D. Day" <ncmike@xxxxxxxxxx>
Date: Thu, 09 Feb 2006 13:35:53 -0500
Cc: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Stefan Berger <stefanb@xxxxxxxxxx>, "Scarlata, Vincent R" <vincent.r.scarlata@xxxxxxxxx>, Ronald Perez <ronpz@xxxxxxxxxx>
Delivery-date: Thu, 09 Feb 2006 18:47:05 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43EB766A.30701@xxxxxxxxxx>
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: <OF8A30427C.48305C4F-ON85257110.005AFDA3-85257110.005CA9EB@xxxxxxxxxx> <43EB766A.30701@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Macintosh/20051201)
Anthony Liguori wrote:
all). It also allows you to do clever things like vary the port which should add to the security of migration.

Allowing the target to choose the port is good practice but not added security.

Why do plugins have to exist? The only reason to have a plugin mechanism is to be able to maintain plugins outside of the Xend tree which would require a stable plugin interface. I don't think we're at a point where we can do that.

No, you are missing an important point. The plugin mechanism is necessary to isolate specialized device migration code from general-purpose migration code. I don't think it has anything to do with where the plugins are maintained.

This all sounds like it's going to add complexity. The tools are already far too complex.

I think the complexity is already there in the usage scenarios. So this is not adding complexity. Rather it is dealing with complexity that exists. Right now the tools ignore most of the complex scenarios.


Xen-devel mailing list