Hello Simon,
these are the EFI configuration tables that EDK II is publishing:
Configuration tables: ee4e5898-3914-4259-9d6e-dc7bd79403cf 05ad34ba-6f02-4214-952e-4da0398e2bb9 7739f24c-93d7-11d4-9a3a-0090273fc14d 4c19049f-4137-4dd3-9c10-8b97a83ffdfa 49152e77-1ada-4764-b7a2-7afefed95e8b 060cc026-4c0d-4dda-8f41-595fef00a502 SMBIOS eb9d2d30-2d88-11d3-9a16-0090273fc14d ACPI 2.0 dcfa911d-26eb-469f-a220-38b7dc461220 d719b2cb-3d3a-4596-a3bc-dad00e67656f
Here is the translation for the GUIDs:
Configuration tables: EFI_LZMA_COMPRESSED (not standardized) EFI_DXE_SERVICES (not standardized) EFI_HOB_LIST (PI specification) EFI_MEMORY_TYPE (not standardized) EfiDebugImageInfoTable (UEFI specification) EFI_MEM_STATUS_CODE_REC (not standardized) SMBIOS (UEFI specification) EFI_GUID_EFI_ACPI1 (UEFI specification, deprecated) ACPI 2.0 (UEFI specification) EfiMemoryAttributesTable (UEFI specification) EFI_IMAGE_SECURITY_DATABASE (not defined as table in UEFI spec)
At least the Memory Attributes Table is used with some security profiles of Windows. The lack of one of the tables might be stopping the installation progress.
The EFI_DEBUG_IMAGE_INFO_TABLE points to SMM images and I needed smm=on to run the Windows installer on EDK II.
The Windows 11 installer does not comprise a virtio block device driver. Some Fedora people have packages a driver that you could load into the installer but I guess it is easier to supply an emulated NVMe or SCSI driver as installation target.
Best regards
Heinrich