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

Warner Losh imp at bsdimp.com
Tue Dec 15 16:39:39 UTC 2020


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.

Warner


>
> 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
> >>
> >>
> >> _______________________________________________
> >> freebsd-arch at freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> >> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
> >>
> > _______________________________________________
> > freebsd-arch at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> > To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
>


More information about the freebsd-arch mailing list