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

On 18 Jan 2010, at 16:15, Dave Scott wrote:

> 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.

That's exactly it; any mechanism is just fine to get the data to the guest.  IP 
is nice from the guest's perspective since most of them have a stack already 
(whereas the VMCI-like socket interface would require it be ported to, for 
example, MiniOS separately).  That would be very straightforward though, 
compared to all the messing around with private IPs and DHCP that is currently 


xen-api mailing list