From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56119) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YgD8i-00073N-Og for qemu-devel@nongnu.org; Thu, 09 Apr 2015 10:09:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YgD8e-0003UM-K0 for qemu-devel@nongnu.org; Thu, 09 Apr 2015 10:09:04 -0400 Received: from [86.35.2.13] (port=41718 helo=path.include.gr) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YgD8e-0003TG-96 for qemu-devel@nongnu.org; Thu, 09 Apr 2015 10:09:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Date: Thu, 09 Apr 2015 17:08:47 +0300 From: Chrysostomos Nanakos In-Reply-To: References: <1407519603-6635-1-git-send-email-kwolf@redhat.com> <1407519603-6635-23-git-send-email-kwolf@redhat.com> <5525F67E.2090609@suse.de> Message-ID: <882d339a871b5a198a5526630bb96def@mail.include.gr> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PULL 22/62] block: Support Archipelago as a QEMU block backend Reply-To: chris@include.gr List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Kevin Wolf , Peter Maydell , Jeff Cody , qemu-devel , Stefan Hajnoczi , =?UTF-8?Q?Andreas_F=C3=A4rber?= On 2015-04-09 17:05, Stefan Hajnoczi wrote: > On Thu, Apr 9, 2015 at 1:48 PM, Chrysostomos Nanakos=20 > wrote: >> On 2015-04-09 06:48, Andreas F=C3=A4rber wrote: >>> >>> Am 08.08.2014 um 19:39 schrieb Kevin Wolf: >>>> >>>> From: Chrysostomos Nanakos >>>> >>>> VM Image on Archipelago volume is specified like this: >>>> >>>> >>>> >>>>=20 >>>> file.driver=3Darchipelago,file.volume=3D[,file.mport=3D<= mapperd_port>[, >>>> file.vport=3D][,file.segment=3D]] >>>> >>>> 'archipelago' is the protocol. >>>> >>>> 'mport' is the port number on which mapperd is listening. This is >>>> optional >>>> and if not specified, QEMU will make Archipelago to use the=20 >>>> default port. >>>> >>>> 'vport' is the port number on which vlmcd is listening. This is=20 >>>> optional >>>> and if not specified, QEMU will make Archipelago to use the=20 >>>> default port. >>>> >>>> 'segment' is the name of the shared memory segment Archipelago=20 >>>> stack is >>>> using. >>>> This is optional and if not specified, QEMU will make Archipelago=20 >>>> to use >>>> the >>>> default value, 'archipelago'. >>>> >>>> Examples: >>>> >>>> file.driver=3Darchipelago,file.volume=3Dmy_vm_volume >>>> file.driver=3Darchipelago,file.volume=3Dmy_vm_volume,file.mport=3D12= 3 >>>> file.driver=3Darchipelago,file.volume=3Dmy_vm_volume,file.mport=3D12= 3, >>>> file.vport=3D1234 >>>> file.driver=3Darchipelago,file.volume=3Dmy_vm_volume,file.mport=3D12= 3, >>>> file.vport=3D1234,file.segment=3Dmy_segment >>>> >>>> Signed-off-by: Chrysostomos Nanakos >>>> Reviewed-by: Stefan Hajnoczi >>>> Signed-off-by: Kevin Wolf >>>> --- >>>> MAINTAINERS | 6 + >>>> block/Makefile.objs | 2 + >>>> block/archipelago.c | 787 >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> configure | 40 +++ >>>> 4 files changed, 835 insertions(+) >>>> create mode 100644 block/archipelago.c >>> >>> >>> Judging by configure output in v2.3.0-rc2, QEMU seems to rely on >>> libxseg, which is GPL-3.0+: https://github.com/grnet/libxseg >>> >>> How can anyone legally build this backend then? o.O >>> >>> Any chance libxseg can be relicensed to GPL-2.0+? >>> >> >> Hello Andreas, >> indeed the license has changed a few months after submitting the=20 >> patch for >> the block driver to QEMU. I have already contacted the=20 >> administration >> of GRNET which is responsible for this change asking them about the >> aforementioned problem. I am waiting for the reply and hopefully we=20 >> will >> resolve this license matter. > > In the meantime I've sent a patch to disable Archipelago by default=20 > in > ./configure ("[PATCH for-2.3] configure: disable by default and warn > about libxseg GPLv3 license"). You are CCed on the email. > > The intention is to reduce the chance of users accidentally compiling > binaries with license problems. Archipelago support is still > available but it must be explicitly enabled using ./configure > --enable-archipelago. > > Stefan For the moment I totally agree with the proposed patch. Regards, Chrysostomos.