On 2015-04-09 17:05, Stefan Hajnoczi wrote:
On Thu, Apr 9, 2015 at 1:48 PM, Chrysostomos Nanakos
wrote:
On 2015-04-09 06:48, Andreas Färber wrote:
Am 08.08.2014 um 19:39 schrieb Kevin Wolf:
From: Chrysostomos Nanakos
VM Image on Archipelago volume is specified like this:
file.driver=a
On Thu, Apr 9, 2015 at 1:48 PM, Chrysostomos Nanakos wrote:
> On 2015-04-09 06:48, Andreas Färber wrote:
>>
>> Am 08.08.2014 um 19:39 schrieb Kevin Wolf:
>>>
>>> From: Chrysostomos Nanakos
>>>
>>> VM Image on Archipelago volume is specified like this:
>>>
>>>
>>>
>>> file.driver=archipelago,file.
On 2015-04-09 06:48, Andreas Färber wrote:
Am 08.08.2014 um 19:39 schrieb Kevin Wolf:
From: Chrysostomos Nanakos
VM Image on Archipelago volume is specified like this:
file.driver=archipelago,file.volume=[,file.mport=[,
file.vport=][,file.segment=]]
'archipelago' is the protocol.
'mport' i
Am 08.08.2014 um 19:39 schrieb Kevin Wolf:
> From: Chrysostomos Nanakos
>
> VM Image on Archipelago volume is specified like this:
>
> file.driver=archipelago,file.volume=[,file.mport=[,
> file.vport=][,file.segment=]]
>
> 'archipelago' is the protocol.
>
> 'mport' is the port number on which
From: Chrysostomos Nanakos
VM Image on Archipelago volume is specified like this:
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
and if not specified, QE
