Background
PR #3408 (issue #3153) adopted dstack v0.5.11 only for key-provider-build/ (reproducible mr_enclave via build-args), and deliberately kept dstack-vmm and the guest OS image at v0.5.8. Bumping the VMM was deferred because it has real costs and no immediate benefit:
- Measurements:
MRTD/RTMR0-2 are pinned on-chain (allowed_os_measurements) and were generated by the v0.5.8 launcher. v0.5.11 changed the QEMU launch path (vmm/src/app/qemu.rs) and the dstack-mr calculator, so a bump needs measurement re-verification (and possibly a vote_add_os_measurement).
- Config schema: v0.5.11's
vmm.toml differs substantially from v0.5.8 (top-level address/port/image_path → unix socket + [image]; no max_disk_size; host_api 9300→10000; new [key_provider]; changed port_mapping defaults), so the guide's MPC vmm.toml won't drop in.
- Build dep: v0.5.11's
dstack-vmm build requires Node.js + npm (it builds the vmm/ui console).
User Story
As an operator, I want the whole dstack host toolchain (vmm + key-provider) on one pinned version — a single clone that also picks up host-side fixes — without breaking on-chain attestation.
Acceptance Criteria
Resources & Additional Notes
Background
PR #3408 (issue #3153) adopted dstack v0.5.11 only for
key-provider-build/(reproduciblemr_enclavevia build-args), and deliberately keptdstack-vmmand the guest OS image at v0.5.8. Bumping the VMM was deferred because it has real costs and no immediate benefit:MRTD/RTMR0-2are pinned on-chain (allowed_os_measurements) and were generated by the v0.5.8 launcher. v0.5.11 changed the QEMU launch path (vmm/src/app/qemu.rs) and thedstack-mrcalculator, so a bump needs measurement re-verification (and possibly avote_add_os_measurement).vmm.tomldiffers substantially from v0.5.8 (top-leveladdress/port/image_path→ unix socket +[image]; nomax_disk_size;host_api9300→10000; new[key_provider]; changedport_mappingdefaults), so the guide's MPCvmm.tomlwon't drop in.dstack-vmmbuild requires Node.js + npm (it builds thevmm/uiconsole).User Story
As an operator, I want the whole dstack host toolchain (vmm + key-provider) on one pinned version — a single clone that also picks up host-side fixes — without breaking on-chain attestation.
Acceptance Criteria
dstack-vmmlaunching the chosen OS image reproduces measurements already inallowed_os_measurements(or coordinate avote_add_os_measurementfor the new set).vmm.toml(port mapping incl. 24567, disk size,host_api,[key_provider]).nodejs/npmto the VMM build prerequisites.Resources & Additional Notes