From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Liviu Ionescu <ilg@livius.net>,
QEMU Developers <qemu-devel@nongnu.org>,
Alistair Francis <alistair23@gmail.com>
Subject: Re: /usr/shared/qemu binaries
Date: Tue, 18 Jan 2022 13:30:35 +0100 [thread overview]
Message-ID: <d9c9de5c-7b33-ea60-4a14-634cdd8f66a2@redhat.com> (raw)
In-Reply-To: <CAFEAcA_qkUPjSz2PQTxtkTFuho=HusONxN56e9z89B8jHrOJag@mail.gmail.com>
On 1/13/22 18:23, Peter Maydell wrote:
> On Thu, 13 Jan 2022 at 17:13, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 1/12/22 14:56, Peter Maydell wrote:
>>> Those are UEFI firmware images which are suitable for using with
>>> the arm/aarch64 "virt" board. They're only used if the user specifically
>>> asks to use them on the command line (eg with
>>> "-drive if=pflash,format=raw,file=pc-bios/edk2-aarch64-code.fd" or
>>> similar).
>>
>> There must be lots of zeros in there. Maybe we should tell QEMU to
>> unpack firmware .gz or .lzo files?
>
> Not hugely keen on adding more "do what I mean" behaviour...
Certainly no autodetection (with writable pflash there's the possibility
of the guest causing real problems), but we already distribute firmware
as compressed files so the zeroes _are_ causing problems for us as well.
We are just telling the users to deal with it.
Paolo
next prev parent reply other threads:[~2022-01-18 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 10:12 /usr/shared/qemu binaries Liviu Ionescu
2022-01-10 12:10 ` Alistair Francis
2022-01-10 13:02 ` Liviu Ionescu
2022-01-10 22:55 ` Alistair Francis
2022-01-10 23:03 ` Liviu Ionescu
2022-01-12 12:24 ` Liviu Ionescu
2022-01-12 13:56 ` Peter Maydell
2022-01-12 14:14 ` Liviu Ionescu
2022-01-13 17:13 ` Paolo Bonzini
2022-01-13 17:23 ` Peter Maydell
2022-01-18 12:30 ` Paolo Bonzini [this message]
2022-01-18 13:24 ` Daniel P. Berrangé
2022-01-13 17:58 ` Liviu Ionescu
2022-01-13 17:59 ` BALATON Zoltan
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=d9c9de5c-7b33-ea60-4a14-634cdd8f66a2@redhat.com \
--to=pbonzini@redhat.com \
--cc=alistair23@gmail.com \
--cc=ilg@livius.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).