Re: [Qemu-devel] [PATCH v5 1/4] block: Support Archipelago as a QEMU block backend

2014-06-26 Thread Chrysostomos Nanakos
On Thu, Jun 26, 2014 at 09:06:03AM -0600, Eric Blake wrote: > On 06/23/2014 06:32 AM, Chrysostomos Nanakos wrote: > > VM Image on Archipelago volume is specified like this: > > > > file=archipelago:[/mport=[:vport=][: > > segment=]] > > > > or > > > > file.driver=archipelago,file.volume=[,file.m

Re: [Qemu-devel] [PATCH v5 1/4] block: Support Archipelago as a QEMU block backend

2014-06-26 Thread Eric Blake
On 06/23/2014 06:32 AM, Chrysostomos Nanakos wrote: > VM Image on Archipelago volume is specified like this: > > file=archipelago:[/mport=[:vport=][: > segment=]] > > or > > file.driver=archipelago,file.volume=[,file.mport=[, > file.vport=][,file.segment=]] > I still plan to review this series

[Qemu-devel] [PATCH v5 1/4] block: Support Archipelago as a QEMU block backend

2014-06-23 Thread Chrysostomos Nanakos
VM Image on Archipelago volume is specified like this: file=archipelago:[/mport=[:vport=][: segment=]] or file.driver=archipelago,file.volume=[,file.mport=[, file.vport=][,file.segment=]] 'archipelago' is the protocol. 'mport' is the port number on which mapperd is listening. This is optional