public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Richard Lyu via groups.io" <richard.lyu=suse.com@groups.io>
To: devel@edk2.groups.io
Subject: Re: [edk2-devel] [OvmfPkg] Build fails due to insufficient FV size in edk2-stable202502
Date: Tue, 11 Mar 2025 15:47:52 +0800	[thread overview]
Message-ID: <Z8_qqOJzw7RuMOgr@localhost.localdomain> (raw)
In-Reply-To: <j5Y4DJtgqIC4kqpho_e_qyHnLxSBWTypc1OWHlIandY9Dy4HrwvXVud5Iqnu95qsMyYHIVkQgviNKty0BADt8DGjEjacN9IA2L6_leoMdlA=@proton.me>

Thanks! It's good for me, and I will try it.

On 2025/03/11 07:30, memristor2 via groups.io wrote:
> Yes you could do this manually. one way is to extend the size of the FD that is small and reduce the size of other FDs if they have unused space so the overall size wouldn't change. Look into the FDF specification for a better understanding and it's not that complicated you'd resolve this quickly.
> 
> 
> 
> 
> Sent with Proton Mail secure email.
> 
> On Tuesday, March 11th, 2025 at 10:46 AM, Richard Lyu via groups.io <richard.lyu=suse.com@groups.io> wrote:
> 
> > Hi memristor2, ardb,
> > 
> > Thank you for your suggestions, but since there is a requirement to use a 2MB size, I need to maintain the size at FD_SIZE_2MB. So, is there any other way to reduce the size, such as by modifying the fdf file?
> > Would this method be worth trying?
> > 
> > Best Regards,
> > Richard Lyu
> > 
> > On 2025/03/11 08:03, Ard Biesheuvel wrote:
> > 
> > > On Tue, 11 Mar 2025 at 07:46, Richard Lyu via groups.io
> > > richard.lyu=suse.com@groups.io wrote:
> > > 
> > > > I built OVMF with the following options
> > > > 
> > > > build -D TPM2_ENABLE -D TPM2_CONFIG_ENABLE -D NETWORK_IP6_ENABLE -D NETWORK_HTTP_BOOT_ENABLE -D BUILD_SHELL=FALSE -a X64 -b DEBUG -t GCC5 -p OvmfPkg/OvmfPkgX64.dsc -D FD_SIZE_2MB -D SECURE_BOOT_ENABLE
> > > > 
> > > > However, I encountered an insufficient FV size issue. This issue did not occur in edk2-stable202411, but it appears in edk2-stable202502.
> > > > 
> > > > GenFv: ERROR 3000: Invalid
> > > > the required fv image size 0x1affc8 exceeds the set fv image size 0x1ac000
> > > > 
> > > > Is there any way to resolve this?
> > > 
> > > Using FD_SIZE_4MB instead of FD_SIZE_2MB should help.
> > 
> > 
> > 
> > 
> 
> 
> 
> 
> 


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



  reply	other threads:[~2025-03-11  7:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  6:45 [edk2-devel] [OvmfPkg] Build fails due to insufficient FV size in edk2-stable202502 Richard Lyu via groups.io
2025-03-11  6:54 ` memristor2 via groups.io
2025-03-11  7:03 ` Ard Biesheuvel via groups.io
2025-03-11  7:16   ` Richard Lyu via groups.io
2025-03-11  7:30     ` memristor2 via groups.io
2025-03-11  7:47       ` Richard Lyu via groups.io [this message]
2025-03-11 12:14     ` Gerd Hoffmann via groups.io
2025-03-12  5:44       ` Richard Lyu via groups.io

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=Z8_qqOJzw7RuMOgr@localhost.localdomain \
    --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