Thanks Gerd,

 

> When hotplugging devices you might need the 'pref64-reserve=<size>' property for '-device pcie-root-port' to make the bridge window larger.

 

Double thanks for this - it was exactly what I needed, and I am now able to get hotplug working on a VM where the GPUs weren't attached at boot. (and I can confirm that there is no PCI initialization slowdown when I do it that way, as opposed to attaching at boot time.)

 

> I think it would be better to just give the PciMmio64Mb config hints higher priority, i.e. if they are present (and don't conflict with installed memory) simply use them as-is

 

Seems reasonable. Since I was able to get the hotplug approach working as I'd hoped, this may not end up being needed for me (if hotplug is appropriate for my colleague's use case), but I'll keep this in mind.

 

> But I'd also like to figure what the exact problem is.  Ideally OVMF should just work without requiring manual configuration.  One of the reasons to add the dynamic mmio window was to allow pci devices with large bars to work fine without manual tuning ...

 

Agreed - I'm hoping to get closer to that answer in this thread that I started in the kvm/pci lists. As far as I can tell, PlatformDynamicMMIOWindow isn't doing anything wrong here - it gives me a valid sized window - it just so happens that we were benefiting from the old improperly sized window in a roundabout way as long as our `pci=realloc` workaround was in place in older OVMF versions.

 

> Can you try to change the manual configuration to be more like the dynamic mmio window configuration, one change at a time (first size, next base, possibly multiple base addresses) and see where exactly it breaks? Does it make a difference if you add a iommu to the virtual machine? 

 

_._,_._,_

_._,_._,_