Version matrix
This page is the single source of truth for versions and images. Every record distinguishes a recorded value, a minimum version and the way to verify it: recorded values reproduce a run, minimum versions decide compatibility, and the verification method tells you how to check the working tree.
Component versions
Component |
Version or value |
Type |
Evidence |
|---|---|---|---|
QEMU (recorded submodule) |
v11.1.2, commit |
recorded |
|
QEMU (system fallback, legacy launcher) |
10.1 or newer with |
minimum |
preflight check in |
gem5 (submodule) |
|
recorded |
|
gem5 build target |
|
fixed |
|
GPU model |
MI300X, gfx942, PCI |
fixed |
|
Coherence protocol |
|
fixed |
|
Rust |
1.95 or newer |
minimum |
|
Guest operating system |
Ubuntu 24.04.2 LTS |
recorded |
image |
Guest kernel |
|
recorded |
image |
ROCm |
7.0 (apt repositories |
recorded |
|
amdgpu DKMS |
matches ROCm 7.0 |
recorded |
|
PyTorch wheel channel |
|
recorded |
|
Guest ROM and discovery firmware |
|
recorded |
|
Packer |
1.16.1 |
recorded |
image |
Packer plugins |
qemu 1.1.7, ansible 1.1.6 |
recorded |
image |
The QEMU submodule record is the v11.1.2 release commit. The qemu checkout in a working tree may sit on another branch, so use git -C qemu describe --tags --always before building; the QEMU version in release notes refers to the recorded gitlink.
Images and containers
Name |
Role |
Source |
|---|---|---|
|
development container image; also the default gem5 container image of the legacy shell launcher |
|
|
build image for guest GPU test programs; default of |
external image; override with |
Guest kernel and disk |
|
|
ghcr.io/third_party/gem5/gpu-fs only builds guest GPU programs and is not the runtime image of a cosim session; the gem5 container started by the legacy shell launcher is cosim-dev:local.
Guest image recipe
The repository contains exactly one guest image recipe, with the following identity and artifacts:
Item |
Value |
|---|---|
Recipe identifier |
|
Role and architecture |
|
Directory |
|
Build entry points |
|
Artifacts |
|
Guest disk |
about 55 GB; the build needs about 60 GB of free space |
Build and check recipes |
|
Provenance and verification
Use these commands to record and check build provenance:
git submodule status gem5 qemu ext/libvfio-user
cat third_party/qemu/VERSION
git -C gem5 describe --tags --always
just ci-gem5-key
just ci-rocm-assets key
The gem5 cache key combines the project commit, gem5 commit, development image, build recipe and build arguments; see
scripts/ci/runtime_artifact.py.The guest image
manifest.jsonrecords the recipe identifier, kernel release, image format and SHA-256 of kernel and disk; seescripts/host/cosim-image.CI artifacts are named after the workflow run and retained for a fixed number of days; reuse across runs verifies the original provenance, see
scripts/ci/image_artifact.pyandscripts/ci/runtime_artifact.py.
Sources and maintenance
Version information comes from these files; update this page when upgrading:
third_party/qemu/VERSIONand the repository gitlink: QEMU version.git submodule status gem5andjustfile: gem5 checkout and build target.Cargo.toml: minimum Rust version.resources/images/recipes/ubuntu/24.04/x86_64/rocm/7.0/recipe.toml: guest OS and kernel.resources/images/recipes/ubuntu/24.04/x86_64/rocm/7.0/provision.yml,build.shandimage.pkr.hcl: ROCm, PyTorch channel, ROM and build-tool versions.