> -----Original Message-----
> From: Thanos Makatos <thanos.maka...@nutanix.com>
> Sent: 01 April 2021 13:42
> To: seabios@seabios.org
> Cc: John Levon <john.le...@nutanix.com>; Swapnil Ingle
> <swapnil.in...@nutanix.com>; Liu, Changpeng <changpeng....@intel.com>
> Subject: [SeaBIOS] SeaBIOS fails to boot from NVMe controller with lots of
> namespaces
>
> I'm using SeaBIOS (b0d61ec) to boot from a virtual NVMe controller that has
> relatively many namespaces (64). The exact error is :
>
> /3ff9f000\ Start thread
> |3ff9f000| Searching bootorder for: /pci@i0cf8/*@6
> ...
> |3ff9f000| WARNING - Unable to allocate resource at
> nvme_controller_enable:632!
>
> I changed the number of namespaces my controller reports to 1 and it
> worked fine. Is there an easy way to get around this or do I have to fix the
> code? I haven't looked at the code in detail, but I think we don't have to
> allocate the array of namespaces in nvme_controller_enable; instead, we
> can probe a namespace right before we attempt to boot from it (not sure
> where exactly this is done).
> _______________________________________________
> SeaBIOS mailing list -- seabios@seabios.org To unsubscribe send an email to
> seabios-le...@seabios.org
I figured out that by increasing BUILD_MIN_BIOSTABLE from 2K to 16K there's
enough memory to dynamically allocate. Is there any problem with this?
_______________________________________________
SeaBIOS mailing list -- seabios@seabios.org
To unsubscribe send an email to seabios-le...@seabios.org
