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: veillard@xxxxxxxxxx
Subject: Re: [Xen-devel] A migration framework for external devices
From: "Mike D. Day" <ncmike@xxxxxxxxxx>
Date: Thu, 09 Feb 2006 11:10:17 -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 16:21:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060209150127.GQ30975@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: <OFAF40C2ED.9A049C9A-ON8525710F.007C18EC-8525710F.007C8530@xxxxxxxxxx> <43EB36DB.7080302@xxxxxxxxxx> <20060209150127.GQ30975@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Macintosh/20051201)
Daniel Veillard wrote:
  Another common XML related design error is to embbed XML along with
other data in a stream without markers, you end up having to precompute
the size of the XML instance which makes streaming impossible or force some unclean processing at the XML level (as an XML instance has no end
marker in itself, the end must be provided by the container or the code
driving the parser).

Yes, totally agree

  So how do you plan to glue the XML and the other parts together ?

One way is to have two channels (like ftp). Have an xml session channel and a tcp data channel. That gives the benefits of xml-rpc for triggering events and invoking plugins. You could use xml-rpc to negotiate the port for the migration data transfer, for example. Then use the data channel (scp/tcp) for the migration.

I'm not convinced this approach is better than starting from scratch tho.


LTC Open Hypervisor Project:
1) Ensure linux has a good GPL hypervisor
2) Ensure Xen exploits xSeries Platforms
3) Provide value-add Xen Extensions for IBM customers.

Xen-devel mailing list