public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, fred.lotter@canonical.com
Subject: Re: [edk2-devel] QEMU / OVMF ESP corruption
Date: Tue, 5 Nov 2024 13:28:39 +0100	[thread overview]
Message-ID: <semrqgf6jxoqr5qjoaqwi3qjidre7n4iw73l2wujy3ah57t4rk@wwsd7jim3yax> (raw)
In-Reply-To: <CA+yndwj1O+fq5Ypfqiqa6NXymZocOpj3CTWxd9UKrgqbxDYRbg@mail.gmail.com>

  Hi,

> This pattern seen during the EFI stub preamble is also seen during OVMF
> startup, so it seems this is some common EFI VAR ? related code. At OVMF
> startup this seems to repeat a number of times before Grub starts.
> 
> ===> If I move OVMF to pflash disks for code + vars, this issue does not
> happen.

Most likely this is OVMF reading/writing NvVars file (EFI variable
storage).  When using pflash OVMF doesn't do that.

It's a very fundamental design bug in grub.  Grub uses its own code for
alot of stuff instead of calling EFI services.  Which includes the FAT
filesystem driver.  Result is that there are *two* FAT filesystem
drivers active in the system (both edk2 and grub driver), stomping on
each others feed, especially if both are used for write access to the
file system.

take care,
  Gerd



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120725): https://edk2.groups.io/g/devel/message/120725
Mute This Topic: https://groups.io/mt/108674692/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2024-11-05 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 16:23 [edk2-devel] QEMU / OVMF ESP corruption Fred Lotter
2024-11-05 12:28 ` Gerd Hoffmann [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-list 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=semrqgf6jxoqr5qjoaqwi3qjidre7n4iw73l2wujy3ah57t4rk@wwsd7jim3yax \
    --to=devel@edk2.groups.io \
    /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