Repository navigation
Conversation
Signed-off-by: Leechael Yim <yanleech@gmail.com>
Leechael
force-pushed
the
fix/vmm-pci64-preflight
branch
from
October 30, 2026 08:33
7484d3c to
fb18c85
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
On usw5, eight B300 GPUs (10de:3182) expose 512 GiB + 64 MiB + 32 MiB of 64-bit MMIO BARs each: 4 TiB + 768 MiB in total. With
qemu_pci_hole64_size = "4T", firmware expands the PCI64 window beyond the fixed window modeled by dstack-mr. KMS then rejects the ACPI digest after several minutes of boot, and repeated boots can interrupt GPU initialization/cleanup.Fix
0uses Q35's 32 GiB default). Return an actionable error, append the existingboot.errorevent and updateboot_error, and clear the persisted started marker so automatic restart does not retry the same invalid configuration.This is intentionally a small capacity check, not a firmware allocation simulator: alignment gaps can still require a larger window. No guest/KMS/protobuf/Cloud API changes. Existing
CreateVmcleanup on synchronous start failure is unchanged; retained VMs started throughStartVmexpose the error throughVmInfo.eventsas before.Verification
anyhow/fs-errversions: 1 test passed. Production helper Clippy checks passed in that harness. Surrounding GPU config types were represented by minimal matching structs; this is not a full VMM build.git diff --checkpassed.dcap-qvl-webpki 0.103.15+dcap.1. Linux integration/build checks are left to CI.