Run AGFHC, TransferBench, and RVS health burn-in tests

Run AGFHC, TransferBench, and RVS health burn-in tests#

2026-09-24

4 min read time

Applies to Linux

Health burn-in tests run AMD GPU Field Health Check (AGFHC), TransferBench, and ROCm Validation Suite (RVS) on every node in the cluster. Use these tests to validate GPU hardware, memory bandwidth, and compute throughput before production workloads.

Set up config#

  1. Copy the health configuration file:

    cvs config copy health/mi300_health_config.json --output ~/cvs_workspace/health/mi300_health_config.json

  2. Edit paths and any remaining <changeme> placeholders:

    • Under agfhc: path, package_tar_ball, install_dir

    • Under transferbench: git_install_path, rocm_path (or leave <changeme> to auto-detect)

    • Under rvs: git_install_path, path, rocm_path

For the complete field reference including install paths and threshold values, see Health test configuration file reference for Cluster Validation Suite (CVS).

Run tests#

Use these tests to validate single-node diagnostics for GPU cluster health. For the performance validation, use the reference bandwidth or latency numbers provided as part of the input config_file for the relevant test.

Use these scripts to run each health test. These CVS test scripts have two parts: installing the functionality and running the tests.

AGFHC#

See the AGFHC (AMD GPU Field Health Check) docs for more information.

You can list all available AGFHC test cases using the CLI:

cvs list agfhc_cvs

Available tests in agfhc_cvs:
  - test_agfhc_hbm
  - test_agfhc_hbm1_lvl5
  - test_agfhc_hbm2_lvl5
  - test_agfhc_hbm3_lvl3
  - test_agfhc_dma_all_lvl1
  - test_agfhc_dma_lvl1
  - test_agfhc_gfx_lvl1
  - test_agfhc_pcie_lvl1
  - test_agfhc_pcie_lvl3
  - test_agfhc_xgmi_lvl1
  - test_agfhc_all_perf
  - test_agfhc_all_lvl5

Run the AGFHC test:

  1. Run the installation:

    cvs run install_agfhc \
  --cluster_file ~/cvs_workspace/cluster.json \
  --config_file ~/cvs_workspace/health/mi300_health_config.json \
  --html=/var/www/html/cvs/agfhc.html --capture=tee-sys --self-contained-html \
  --log-file=/tmp/agfhc.log -vvv -s

  2. Run the AGFHC test:

    cvs run agfhc_cvs \
  --cluster_file ~/cvs_workspace/cluster.json \
  --config_file ~/cvs_workspace/health/mi300_health_config.json \
  --html=/var/www/html/cvs/agfhc.html --capture=tee-sys --self-contained-html \
  --log-file=/tmp/agfhc.log -vvv -s

  3. Run the CSP qualification test:

    cvs run csp_qual_agfhc \
  --cluster_file ~/cvs_workspace/cluster.json \
  --config_file ~/cvs_workspace/health/mi300_health_config.json \
  --html=/var/www/html/cvs/agfhc.html --capture=tee-sys --self-contained-html \
  --log-file=/tmp/agfhc.log -vvv -s

TransferBench#

See the TransferBench docs for more information.

You can list all available TransferBench test cases using the CLI:

cvs list transferbench_cvs

Available tests in transferbench_cvs:
  - test_transfer_bench_a2a
  - test_transfer_bench_p2p
  - test_transfer_bench_healthcheck
  - test_transfer_bench_a2asweep
  - test_transfer_bench_scaling
  - test_transfer_bench_schmoo

Run the TransferBench test:

  1. Run the installation:

    cvs run install_transferbench \
  --cluster_file ~/cvs_workspace/cluster.json \
  --config_file ~/cvs_workspace/health/mi300_health_config.json \
  --html=/var/www/html/cvs/transferbench.html --capture=tee-sys --self-contained-html \
  --log-file=/tmp/transferbench.log -vvv -s

  2. Start the TransferBench test:

    cvs run transferbench_cvs \
  --cluster_file ~/cvs_workspace/cluster.json \
  --config_file ~/cvs_workspace/health/mi300_health_config.json \
  --html=/var/www/html/cvs/transferbench.html --capture=tee-sys --self-contained-html \
  --log-file=/tmp/transferbench.log -vvv -s

RVS#

See the ROCm Validation Suite (RVS) docs for more information.

You can list all available RVS test cases using the CLI:

cvs list rvs_cvs

Available tests in rvs_cvs:
  - test_rvs_level_config
  - test_rvs_gpu_enumeration
  - test_rvs_gpup_single
  - test_rvs_mem_test
  - test_rvs_gst_single
  - test_rvs_iet_single
  - test_rvs_pebb_single
  - test_rvs_pbqt_single
  - test_rvs_peqt_single
  - test_rvs_rcqt_single
  - test_rvs_tst_single
  - test_rvs_babel_stream

Run the RVS test:

  1. Run the installation:

    cvs run install_rvs \
  --cluster_file ~/cvs_workspace/cluster.json \
  --config_file ~/cvs_workspace/health/mi300_health_config.json \
  --html=/var/www/html/cvs/rvs.html --capture=tee-sys --self-contained-html \
  --log-file=/tmp/rvs.log -vvv -s

  2. Start the RVS test:

    cvs run rvs_cvs \
  --cluster_file ~/cvs_workspace/cluster.json \
  --config_file ~/cvs_workspace/health/mi300_health_config.json \
  --html=/var/www/html/cvs/rvs.html --capture=tee-sys --self-contained-html \
  --log-file=/tmp/rvs.log -vvv -s

Note

Both cvs run install_rvs and cvs run rvs_cvs support running inside a per-host container instead of on the host filesystem. Pass a cluster_container.json cluster file with orchestrator: container to route invocations through the container backend. See Run Cluster Validation Suite (CVS) test suites with a per-host Docker container backend.

Contents