On 5/13/25 1:05 PM, Sergii Dmytruk wrote: > When running on an EFI-enabled system, Xen needs to have access to Boot > Services in order to initialize itself properly and reach a state in > which a dom0 kernel can operate without issues. > > This means that DRTM must be started in the middle of Xen's > initialization process. This effect is achieved via a callback into > bootloader (GRUB) which is responsible for initiating DRTM and > continuing Xen's initialization process. The latter is done by > branching in Slaunch entry point on a flag to switch back into long mode > before calling the same function which Xen would execute as the next > step without DRTM.
Depending on the bootloader for this unnecessarily ties DRTM to GRUB. Instead, it would be much better for Xen to be able to perform DRTM itself, which would allow DRTM to work without GRUB. Pop! OS already uses systemd-boot and the trend seems to be from GRUB to systemd-boot. Furthermore, this would allow DRTM with Xen launched directly from the UEFI firmware. -- Sincerely, Demi Marie Obenour (she/her/hers)
OpenPGP_0xB288B55FFF9C22C1.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
