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-API] [PATCH] [CP-1540] [CR-67] Remove P2V server components

To: 'Anil Madhavapeddy' <anil@xxxxxxxxxx>
Subject: RE: [Xen-API] [PATCH] [CP-1540] [CR-67] Remove P2V server components
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Mon, 18 Jan 2010 16:15:56 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: Andrew Peace <Andrew.Peace@xxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 18 Jan 2010 08:16:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <711071D6-021E-4836-81B0-B85FED9E2018@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <8a6800752019e0140664.1263759571@xxxxxxxxxxxxxxxxxxxxxx> <E234CBDE-2997-490A-BF9E-80D64843ABBB@xxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD2143B8C194B4@xxxxxxxxxxxxxxxxxxxxxxxxx> <711071D6-021E-4836-81B0-B85FED9E2018@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqYUE4Z+zXGZKu8SfebUoiWcB/ZIwACKaPg
Thread-topic: [Xen-API] [PATCH] [CP-1540] [CR-67] Remove P2V server components
Hi Anil,

> Machine->OVF->xapi works ok for Windows or Linux, but streaming disks
> across the API is just very convenient.  I only care about it in the
> context of some self-forking VMs work we're doing though, not for
> anything non-research.

Thanks for the explanation. So if I understand correctly it's not the guest 
installer network per-se (with all associated udhcp and IP addr munging) but 
the ability to get data into the VM via the XenAPI that you need.

One possibility we should investigate is "v2v". I believe there's code floating 
about somewhere which takes the shared memory transport common to both 
{net,block}{front,back} and sticks a simple socket interface on the front 
(similar to VMW's VMCI?). Potentially xapi could use that to talk to the guest 
instead of IP.


xen-api mailing list