[TESTING] GNR TDX machines - #4138
Conversation
There was a problem hiding this comment.
Pull request overview
Updates OpenVMM’s GitHub Actions runner selection for the Windows x64 Intel TDX VMM test jobs to target new “GNR” self-hosted baremetal machines.
Changes:
- Updated the Flowey-defined self-hosted runner label set for the Windows x64 Intel TDX baremetal pool to use
GNR. - Propagated the corresponding
runs-onlabel change into the generated GitHub Actions workflows (PR / PR release / CI).
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| flowey/flowey_hvlite/src/pipelines_shared/gh_pools.rs | Changes the canonical Flowey runner label set used to select the Windows x64 Intel TDX baremetal pool. |
| .github/workflows/openvmm-pr.yaml | Updates the workflow job’s runs-on labels to match the new pool label. |
| .github/workflows/openvmm-pr-release.yaml | Updates the release PR workflow job’s runs-on labels to match the new pool label. |
| .github/workflows/openvmm-ci.yaml | Updates the CI workflow job’s runs-on labels to match the new pool label. |
| "self-hosted".to_string(), | ||
| "Windows".to_string(), | ||
| "X64".to_string(), | ||
| "TDX".to_string(), | ||
| "GNR".to_string(), | ||
| "Baremetal".to_string(), |
| - self-hosted | ||
| - Windows | ||
| - X64 | ||
| - TDX | ||
| - GNR | ||
| - Baremetal |
| - self-hosted | ||
| - Windows | ||
| - X64 | ||
| - TDX | ||
| - GNR | ||
| - Baremetal |
| - self-hosted | ||
| - Windows | ||
| - X64 | ||
| - TDX | ||
| - GNR | ||
| - Baremetal |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.
Suppressed comments (1)
flowey/flowey_hvlite/src/pipelines_shared/gh_pools.rs:93
windows_tdx_self_hosted_baremetal()now returns a runner label set that includes "GNR" (and no longer includes a "TDX" label), but the function name and downstream usage still describe this pool as "tdx" (e.g., it’s used for the "x64-windows-intel-tdx" job). This mismatch makes it hard to reason about what hardware/capabilities the pool guarantees and risks future misrouting.
Consider either (a) keeping the "TDX" label and adding "GNR" as an additional label if you want “TDX-on-GNR” specificity, or (b) renaming the function/call sites/job labels to reflect that this is a GNR-specific pool (while keeping the CVM/TDX semantics in the test filter names).
"Windows".to_string(),
"X64".to_string(),
"GNR".to_string(),
"Baremetal".to_string(),
])
Test new GNR TDX blades