My test of the new functionality in OVMF 2024.02-2ubuntu0.4 also worked as expected on Noble on DGX H100, and I observed no regressions in my control tests:
Control test 1 (no custom X-PciMmio64Mb): 1. Started a VM with 4 GPUs passed-through without specifying a custom opt/ovmf/X-PciMmio64Mb or pci=realloc pci=nocrs. Boot time post-ram-alloc was ~1:30. Installed `nvidia-driver-550-server` in guest and ran `sudo nvidia-smi` - worked as expected Control test 2 (custom X-PciMmio64Mb > required GPU aperture size): 1. Started a VM with 4 GPUs passed-through with opt/ovmf/X-PciMmio64Mb = 1262144, without pci=realloc pci=nocrs. Boot time post-ram-alloc was ~1:30. Installed `nvidia-driver-550-server` in guest and ran `sudo nvidia-smi` - worked as expected New functionality test (custom X-PciMmio64Mb < required GPU aperture size): 1. Started a VM with 4 GPUs passed-through with opt/ovmf/X-PciMmio64Mb = 1024Mb and pci=realloc pci=nocrs set in guest. Boot time post-ram-alloc was 0:16 2. Installed `nvidia-driver-550-server` in guest and ran `sudo nvidia-smi` - worked as expected Therefore, I believe this should be safe to migrate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2101903 Title: Backport "OvmfPkg: Use user-specified opt/ovmf/X-PciMmio64Mb value unconditionally" to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/edk2/+bug/2101903/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
