[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 18 Sep 2023 03:51:26 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866

Graham Perrin <grahamperrin@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|Normal                      |---
           See Also|                            |https://bugs.freebsd.org/bu
                   |                            |gzilla/show_bug.cgi?id=2478
                   |                            |45
              Flags|mfc-stable12?               |
                 CC|grahamperrin@freebsd.org    |doc@FreeBSD.org
           Keywords|                            |loader, needs-patch, uefi
                URL|                            |https://github.com/freebsd/
                   |                            |freebsd-doc/blob/main/websi
                   |                            |te/content/en/releases/12.2
                   |                            |R/errata.adoc#open-issues

--- Comment #38 from Graham Perrin <grahamperrin@gmail.com> ---
<https://www.freebsd.org/releases/12.2R/errata/#open-issues> will benefit from
a belated link to this bug 251866, or, at least, an outline of the loader.efi
issue. Keyword: 

* needs patch


(In reply to Warner Losh from comment #36)

I hesitate before closing this report only because of the regression keyword.

Given: 

a) 13.0-RELEASE <https://www.freebsd.org/releases/13.0R/> announced 
   more than two years ago

b) 12.4-RELEASE no longer recommended for new deployments

c) stable/12 reaching end of life in less than three months

d) the available resolution for users of supported versions of FreeBSD 12.⋯
   (upgrade to VMware vSphere ESXi 8.0 or greater)

– I do think that documentation and then closure will be reasonable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.