From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id F15AAC433F5 for ; Wed, 20 Apr 2022 21:19:51 +0000 (UTC) Received: from localhost ([::1]:52872 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nhHjq-0007QT-EL for qemu-devel@archiver.kernel.org; Wed, 20 Apr 2022 17:19:50 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:34908) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhHio-0006lC-RA for qemu-devel@nongnu.org; Wed, 20 Apr 2022 17:18:46 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:42161) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhHim-00063Z-NF for qemu-devel@nongnu.org; Wed, 20 Apr 2022 17:18:46 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 475975C00D8 for ; Wed, 20 Apr 2022 17:18:43 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute4.internal (MEProxy); Wed, 20 Apr 2022 17:18:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apitman.com; h= cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1650489523; x=1650575923; bh=d1ADYTpiyC PICco+ukUmJZGTmZjUQ0M4y5zJvkl3fG8=; b=dAAE96fydF7lbQYZcTvVFj0dv7 eKGZT2Ikj4/SMN4nBEZFKyehnfI+8XS680Ty2VG2qflGFHJNCBORa6vvUO1tYhwZ V65As6NBgVtGsYg4SD/p6D1HWOl/3zIsMn63LQJE4FUHxHZErcgyv/M2cJaENSGz whWWbvnL1bsdOGFRhbWetAf+qPEqOhR8Kh9k3a7MsM4+XxP0lCPRGN6ul0gc9DHb l78Ly/iilSPomldYcJIcb0eeS/cbgDszx2kQV4vCwIvBnu6HRsDnt4DeDNKCAJOh MGeOAXHjW0taRbg8z4JdakcvO/E+CB1eMX5uTr39e8K6yBac6E8IA4xIPZmg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1650489523; x= 1650575923; bh=d1ADYTpiyCPICco+ukUmJZGTmZjUQ0M4y5zJvkl3fG8=; b=U LCscSN7ZfAM67Buc8/cg1RlR06EIrIlLEiEiLJ30t2OpF0PvLBO2kgOcG7DjAEtW 0JRRg123NRRyjT+9fbvuKzyCuqa9fOfapLxRS32ghfh7kfDSjTTnzbmyoGh89rBm C6FiqEH2Dl+BtjltoMw/gRLyDe3RIN8datI10nUCx5Ol4Gzh2uziNeCehSD9Q4oY MRAmIUORaA3A9KVCEkD1o7u2AXa2VveXnAYs59Nw4ZmGQqakLTTdiIhXUxH7PqZ1 EjdtAubMxkVBbXheFHpUGeodqBzKGNOIX3KqxnRqlpXIJVwlBfpu5/0MVSS8S4o9 b0UivU5uehcuSH8oXFTjg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrtddtgddufeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedftehnuggvrhhsucfrihhtmhgrnhdfuceorghnuggvrhhs segrphhithhmrghnrdgtohhmqeenucggtffrrghtthgvrhhnpeejueejtdetjeejhfeije dvffeuvedtjefhtdfghfeiffdvtdehffffhffhheeffeenucffohhmrghinhepghhnuhdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grnhguvghrshesrghpihhtmhgrnhdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 186701EE0083; Wed, 20 Apr 2022 17:18:43 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-568-g521196dd5d-fm-20220414.001-g521196dd Mime-Version: 1.0 Message-Id: In-Reply-To: References: <8f5cc095-e5e9-486d-8e52-d22cac6d2379@www.fastmail.com> Date: Wed, 20 Apr 2022 15:18:22 -0600 From: "Anders Pitman" To: qemu-devel@nongnu.org Subject: Re: Future of libslirp in QEMU Content-Type: multipart/alternative; boundary=b72d3146442f431d8e6ca8bb5161b4d4 Received-SPF: pass client-ip=66.111.4.26; envelope-from=anders@apitman.com; helo=out2-smtp.messagingengine.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" --b72d3146442f431d8e6ca8bb5161b4d4 Content-Type: text/plain Awesome, thanks. Apparently I'm not properly performing a date-sorted search on the list archives. I started here: https://lists.gnu.org/archive/html/qemu-devel/ Then entered "slirp" and searched with chronological order, but the latest entry is from 2020. What am I doing wrong? Thanks, //anders On Wed, Apr 20, 2022, at 2:21 PM, Daniel Henrique Barboza wrote: > > > On 4/20/22 16:08, Anders Pitman wrote: > > I noticed in the 7.0 changelog that libslirp might be removed as a submodule in the future. Since user networking is very important for my project, I'm wondering if this is simply an implementation detail, or if there are plans to eventually remove slirp support entirely from QEMU (which would be bad for me)? > > > > Is there somewhere I can read the discussion about this? I searched the mailing list archives but didn't see anything obvious. > > QEMU will still be supporting libslirp. The difference is that now QEMU will be > using libslirp from the distro instead of packaging it itself. > > The relevant thread is here: > > https://lists.gnu.org/archive/html/qemu-devel/2022-04/msg00974.html > > > Thanks, > > > Daniel > > --b72d3146442f431d8e6ca8bb5161b4d4 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Awesome, thanks= .

Apparently I'm not properly performing a = date-sorted search on the list archives. I started here:
<= br>

Then entered "slirp" and searched with chronological order, but= the latest entry is from 2020. What am I doing wrong?
Thanks,
//anders

= On Wed, Apr 20, 2022, at 2:21 PM, Daniel Henrique Barboza wrote:

On 4/20/22 16:08, Anders Pitman wrote:
> I = noticed in the 7.0 changelog that libslirp might be removed as a submodu= le in the future. Since user networking is very important for my project= , I'm wondering if this is simply an implementation detail, or if there = are plans to eventually remove slirp support entirely from QEMU (which w= ould be bad for me)?
> 
> Is ther= e somewhere I can read the discussion about this? I searched the mailing= list archives but didn't see anything obvious.

=
QEMU will still be supporting libslirp. The difference is that now = QEMU will be
using libslirp from the distro instead of pac= kaging it itself.

The relevant thread is he= re:


Thanks,


Daniel<= br>



--b72d3146442f431d8e6ca8bb5161b4d4--