public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with qemu from CU179
Date: Thu, 28 Sep 2023 12:41:07 +0200	[thread overview]
Message-ID: <aa49f38c-7de1-4ee5-8f52-09350550ced1@ipfire.org> (raw)
In-Reply-To: <BDC264A4-114F-4653-84A8-27EA984AEEB4@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]

Hi

On 28/09/2023 12:04, Michael Tremer wrote:
> Hello Adolf,
> 
> I am happy to bring back user-space networking for QEMU as long as it not been properly deprecated upstream.
Clear. Checking the history, this looks to be qemu deciding they did not want to have to maintain their own bundled version of libslirp when more and more OS's have a system version of libslirp available. Apparently all OS's have it now and hence qemu removed their own bundled version with qemu-7.2

Looking at libslirp, there is no mention of deprecation. The last version was released a year ago but it looks like a couple of commits are merged each month. The last commit was a month ago.

Regards,

Adolf.

> 
> -Michael
> 
>> On 28 Sep 2023, at 11:00, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 28/09/2023 10:39, Michael Tremer wrote:
>>> Hello Adolf,
>>>> On 27 Sep 2023, at 22:35, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> In qemu 7.2 they removed the bundled slirp library. This is used for the net user backend and is used by default if nothing else is specified.
>>> Hmm, it is not very common to use this kind of network access. I suppose most people use QEMU in connection with libvirt.
>> We can always discuss this in the next conf call on following Monday.
>> I will submit the patch set anyway and we can decide what to do in the conf call.
>>
>> Regards,
>> Adolf.
>>>> The example in the wiki uses the net user.
>>>>
>>>> Unfortunately it looks like nobody ran qemu in testing for CU179.
>>>>
>>>> A user on the forum has run into this problem and it stops his qemu system from running.
>>>>
>>>> I will do a new build of qemu/qemu-ga (updated to 8.1.1) which will include the libslirp package tomorrow (28th Sep).
>>>>
>>>> Hopefully the patch submission that I make for this will be able to be merged into CU180 Testing.
>>> No problem, we still have a few weeks before this gets released and we can add this as a quick fix.
>>> Best,
>>> -Michael
>>>>
>>>> Regards,
>>>>
>>>> Adolf.
>>>>
>>>>
>>>> -- 
>>>> Sent from my laptop
>>>>
> 

  reply	other threads:[~2023-09-28 10:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 21:35 Adolf Belka
2023-09-28  8:39 ` Michael Tremer
2023-09-28 10:00   ` Adolf Belka
2023-09-28 10:04     ` Michael Tremer
2023-09-28 10:41       ` Adolf Belka [this message]
2023-09-28 10:41         ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aa49f38c-7de1-4ee5-8f52-09350550ced1@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox