From: Laszlo Ersek <lersek@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: Too slow edk2 bios boot?
Date: Wed, 23 Jun 2021 17:23:19 +0200 [thread overview]
Message-ID: <df47fd61-a04b-8739-b80f-bf9f4ad5e618@redhat.com> (raw)
In-Reply-To: <CAEUhbmWP3Wi-vL-ACyMtwTbukdHNQArXAE0gHFaHYHAW4ONuKg@mail.gmail.com>
On 06/23/21 07:47, Bin Meng wrote:
> Hi Laszlo,
>
> On Wed, Jun 23, 2021 at 12:13 AM Laszlo Ersek <lersek@redhat.com> wrote:
>
>> On 06/18/21 15:06, Bin Meng wrote:
>>> On Fri, Jun 18, 2021 at 7:46 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
>>>
>>>> On Fri, Jun 18, 2021 at 06:46:57PM +0800, Bin Meng wrote:
>>>>> Hi Laszlo,
>>>>>
>>>>> Using the QEMU shipped edk2 bios, for i386, it boots very quickly to
>>>>> the EFI shell.
>>>>>
>>>>> $ qemu-system-i386 -nographic -pflash edk2-i386-code.fd
>>
>> Ouch. Don't do this. If you use just one pflash chip, then a unified FD
>> file is expected in that chip, containing both varstore and firmware
>> executable.
>>
>> Upstream QEMU does not bundle / install unified FD files however. What it
>> provides are separate executables and varstore *templates*.
>>
>> If you don't want to create a permanent variable store file for your VM,
>> from the template called "edk2-i386-vars.fd", then the minimum command line
>> is something like this:
>>
>> qemu-system-i386 \
>> -drive if=pflash,unit=0,format=raw,readonly=on,file=edk2-i386-code.fd \
>> -drive if=pflash,unit=1,format=raw,snapshot=on,file=edk2-i386-vars.fd \
>>
>> (Nowadays I should use the "blockdev" syntax instead of "-drive", but I've
>> not updated my scripts thus far ;))
>>
>
> Thank you. I suggest we document this in the QEMU documentation [1]
Already documented in "docs/interop/firmware.json".
>>>> qemu -nic none ?
>>>>
>>>
>>> Yep this works. Thanks a lot!
>>
>> If you need neither NICs nor disks in your guest at all, then "-nic none"
>> is indeed the simplest solution.
>>
>
> If using NICs in the guest, then we have to adjust the order in the BIOS
> boot menu?
No; assuming you have a device (NIC or disk) you'd like to boot off of,
and a NIC you wouldn't, specify the "bootindex" device property for the
devices in the first category (with the desired decimal indices), and
omit the "bootindex" device property for the devices in the second category.
Thanks
Laszlo
prev parent reply other threads:[~2021-06-23 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 10:46 Too slow edk2 bios boot? Bin Meng
2021-06-18 11:46 ` Gerd Hoffmann
2021-06-18 13:06 ` Bin Meng
2021-06-22 16:13 ` Laszlo Ersek
2021-06-23 5:47 ` Bin Meng
2021-06-23 15:23 ` Laszlo Ersek [this message]
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=df47fd61-a04b-8739-b80f-bf9f4ad5e618@redhat.com \
--to=lersek@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=kraxel@redhat.com \
--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).