From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36056) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cdEIt-0007Hb-FZ for qemu-devel@nongnu.org; Mon, 13 Feb 2017 05:56:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cdEIq-0000qp-9m for qemu-devel@nongnu.org; Mon, 13 Feb 2017 05:56:19 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47376) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cdEIq-0000qS-4c for qemu-devel@nongnu.org; Mon, 13 Feb 2017 05:56:16 -0500 References: <20170208221050.GP2955@var.home> <20170212073019.GA25566@cs.unibo.it> From: Thomas Huth Message-ID: Date: Mon, 13 Feb 2017 11:56:11 +0100 MIME-Version: 1.0 In-Reply-To: <20170212073019.GA25566@cs.unibo.it> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] libslirp and QEMU slirp List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Renzo Davoli , Samuel Thibault Cc: Stefan Hajnoczi , virtualsquare@cs.unibo.it, jasowang@redhat.com, Jan Kiszka , peter.maydell@linaro.org, qemu-devel On 12.02.2017 08:30, Renzo Davoli wrote: > Hi, >=20 > On Wed, Feb 08, 2017 at 11:10:50PM +0100, Samuel Thibault wrote: >> Hello, >> >> Stefan Hajnoczi, on Mon 06 Feb 2017 11:55:05 +0000, wrote: >>> I'm proposing this topic for discussion because there might be common >>> ground for Samuel from QEMU and the VDE folks to collaborate. >>> >>> Samuel: Should QEMU join forces with libslirp? >> >> Well, there are not that many forces from the QEMU side :) > Neither on VDE side ;-) but many ants can move mountains... >> >> - we are using timers for icmp announcements >> - qemu needs to be able to save/restore state, with compatibility with >> previous versions >=20 > libslirp is using qemu's slirp code. [...] > Timers have been reimplemented using the qemu's API. > save/restore are dummy stubs in libslirp. Qemu's code is still there bu= t it is not used > by libslirp. Well, sure, but if this libslirp is going to evolve into a QEMU-independent library, such timer and save/restore hacks likely should go away from the library and implemented on the side of the consuming application instead. > It would be a nice project to create a common codebase for libslirp. > The project sould be interesting for other VM projects (virtualbox-OSE?= ) and > maybe many others. We could collect several ants... FWIW, I know that WinUAE is using QEMU's slirp code, too. I've got a question: Is there already a project page and public repository for libslirp available somewhere? I did not find anything useful with Google yet... Thomas