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

Hi, On 06/02/2014 06:31 PM, Kevin Wolf wrote: Am 02.06.2014 um 17:04 hat Chrysostomos Nanakos geschrieben: Hi, On 06/02/2014 05:30 PM, Eric Blake wrote: On 06/02/2014 08:15 AM, Chrysostomos Nanakos wrote: VM Image on Archipelago volume is specified like this: file=archipelago:[/mport=[:vpor

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

On 06/02/2014 06:31 PM, Kevin Wolf wrote: Am 02.06.2014 um 17:04 hat Chrysostomos Nanakos geschrieben: Hi, On 06/02/2014 05:30 PM, Eric Blake wrote: On 06/02/2014 08:15 AM, Chrysostomos Nanakos wrote: VM Image on Archipelago volume is specified like this: file=archipelago:[/mport=[:vport=]]

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

On 06/02/2014 09:49 AM, Chrysostomos Nanakos wrote: I still think that there is no need to burden the code with this shorthand... >>> If everyone agrees I can totally remove that part. >> I don't think it's a bad idea to provide a shortcut for human users. The >> important point is just

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

Eric Blake writes: > On 06/02/2014 08:15 AM, Chrysostomos Nanakos wrote: >> VM Image on Archipelago volume is specified like this: >> >> file=archipelago:[/mport=[:vport=]] >> or > > I still think that there is no need to burden the code with this > shorthand... > >> >> file.driver=archipelago,

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

Am 02.06.2014 um 17:04 hat Chrysostomos Nanakos geschrieben: > Hi, > > On 06/02/2014 05:30 PM, Eric Blake wrote: > >On 06/02/2014 08:15 AM, Chrysostomos Nanakos wrote: > >>VM Image on Archipelago volume is specified like this: > >> > >>file=archipelago:[/mport=[:vport=]] > >>or > >I still think th

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

Hi, On 06/02/2014 05:30 PM, Eric Blake wrote: On 06/02/2014 08:15 AM, Chrysostomos Nanakos wrote: VM Image on Archipelago volume is specified like this: file=archipelago:[/mport=[:vport=]] or I still think that there is no need to burden the code with this shorthand... If everyone agrees I

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

On 06/02/2014 08:15 AM, Chrysostomos Nanakos wrote: > VM Image on Archipelago volume is specified like this: > > file=archipelago:[/mport=[:vport=]] > or I still think that there is no need to burden the code with this shorthand... > > file.driver=archipelago,file.volume=[,file.mport=[, > file.

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

VM Image on Archipelago volume is specified like this: file=archipelago:[/mport=[:vport=]] or file.driver=archipelago,file.volume=[,file.mport=[, file.vport=]] 'archipelago' is the protocol. 'mport' is the port number on which mapperd is listening. This is optional and if not specified, QEMU wi