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:00:47 +0200 [thread overview]
Message-ID: <57751fcd-574b-429f-92bb-c1086ca2b737@ipfire.org> (raw)
In-Reply-To: <28A7F68A-5077-432E-B3D3-C15B1C513C62@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
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
>>
>
next prev parent reply other threads:[~2023-09-28 10:00 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 [this message]
2023-09-28 10:04 ` Michael Tremer
2023-09-28 10:41 ` Adolf Belka
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=57751fcd-574b-429f-92bb-c1086ca2b737@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