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

[Yuri Pankov]

Warner Losh wrote:
> On Tue, Dec 15, 2020 at 9:34 AM YUAN RUI via freebsd-arch <
> freebsd-arch at freebsd.org> wrote:
> 
>> yes, all
>>
>> It cannot be the problem of too small memory. I allocated 32g of memory
>> for vmware and this problem still occurs. After debugging, I found that
>> if the memory allocation is greater than 64M, it will trigger a crash.
>>
> 
> OK. That's good to know. I'll have to think about the best way forward.
> There was, at the time this was done (by others), the thought it was 'free'
> and had no consequences.

I can confirm reducing EFI_STAGING_SIZE back to 64 and building "cdrom" 
image successfully boots on ESXi 7, it does not with latest snapshot. 
More so, looks like 
https://svnweb.freebsd.org/base?view=revision&revision=355132 should 
take care, in a dynamic way, of the original problem increasing 
EFI_STAGING_SIZE was supposed to fix?

>> On 12/16/2020 12:09 AM, Warner Losh wrote:
>>> Is this at all? Or only on memory sizes that are small?
>>>
>>> Warner
>>>
>>> On Tue, Dec 15, 2020 at 3:45 AM YUAN RUI via freebsd-arch <
>>> freebsd-arch at freebsd.org> wrote:
>>>
>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866

Thanks a lot!