Re: [edk2-devel] [PATCH v2 2/4] OvmfPkg/PlatformInitLib: detect physical address space

["Fiona Ebner" <f.ebner@proxmox.com>]

Am 16.03.23 um 15:37 schrieb Gerd Hoffmann:
> On Thu, Mar 16, 2023 at 02:58:07PM +0100, Fiona Ebner wrote:
>> Hi,
>> after upgrading to edk2-stable202211 recently, we got user reports[0]
>> about QEMU virtual machines with '-cpu host' on AMD Ryzen hosts not
>> booting correctly anymore. A workaround seems to be assigning more
>> memory to the VM.
> 
> Most likely this one:
>   https://bugzilla.tianocore.org/show_bug.cgi?id=4251
> 
> Either upgrade to 202302 or backport a107ad0f6236..015a001b03db
> to fix that.
> 

Thank you for the suggestion! Unfortunately, the behavior is the same
with 202302 (and with current master, i.e. 410ca0ff94). The bug report
talks about TCG, but this is with KVM.

Is there anything like page tables or the MMIO window which simply
requires more memory when PhysMemAddressWidth is larger? Please note
that the issue here occurs with and without ecb778d0ac
("OvmfPkg/PlatformInitLib: dynamic mmio window size"), the first bad
commit is one earlier.

P.S. I would've tested 202302 already yesterday, but we base the edk2
package off Debian and building the 202302 release didn't work. The QEMU
instance spawned by debian/edk2-vars-generator.py script would hang. I
had to find and cherry-pick QEMU commit dab30fbef3 ("acpi: cpuhp: fix
guest-visible maximum access size to the legacy reg block") first to
make it work.

Best Regards,
Fiona