You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dstack-mr: support edk2-stable202505 OVMF event layout
OVMF was upgraded from an untagged 2024-09 snapshot to edk2-stable202505
in commit f9f11f3 on meta-dstack. The newer firmware emits four extra
RTMR[0] events (QEMU fw_cfg BootMenu/bootorder, EV_EFI_VARIABLE_AUTHORITY,
and a second BootXXXX) and re-formats BootOrder/Boot0000 as full
UEFI_VARIABLE_DATA structs. dstack-mr was still computing the legacy
13-event log, so quote replay on 0.5.10 CVMs produced wrong RTMR[0].
Add an OvmfVariant enum in dstack-types and dispatch rtmr0_log on it.
The new variant's digests come from a 0.5.10 CVM's actual event log;
they're firmware constants for this OVMF build under the standard -kernel
boot config.
Plumbing:
- VmConfig.ovmf_variant: Option<OvmfVariant>: explicit source of truth
for verifiers, set by VMM from image.info.ovmf_variant.
- ImageInfo.ovmf_variant: ditto in metadata.json.
- Verifier prefers vm_config.ovmf_variant; falls back to parsing the
version suffix out of vm_config.image (e.g. "dstack-0.5.10") so
pre-existing deployments without the field keep working.
- dstack-mr CLI adds --dstack-os-version for explicit override.
Verified end-to-end against a 0.5.10 CVM: all four measurements (MRTD,
RTMR[0-2]) match the quote exactly.
0 commit comments