diff --git a/src/gapbs/README.md b/src/gapbs/README.md
index 5307102..030a8df 100644
--- a/src/gapbs/README.md
+++ b/src/gapbs/README.md
@@ -12,7 +12,7 @@
 
 This document provides instructions to create a GAP Benchmark Suite (GAPBS) disk image, which, along with an example script, may be used to run GAPBS within gem5 simulations. The example script uses a pre-built disk-image.
 
-A pre-built disk image, for X86, can be found, gzipped, here: <http://dist.gem5.org/dist/v22-0/images/x86/ubuntu-18-04/gapbs.img.gz>.
+A pre-built disk image, for X86, can be found, gzipped, here: <http://dist.gem5.org/dist/v22-1/images/x86/ubuntu-18-04/gapbs.img.gz>.
 
 ## Building the Disk Image
 
diff --git a/src/gpu/DNNMark/README.md b/src/gpu/DNNMark/README.md
index e07b8a7..7b10474 100644
--- a/src/gpu/DNNMark/README.md
+++ b/src/gpu/DNNMark/README.md
@@ -27,8 +27,8 @@
 `-v ${PWD}:${PWD}` in the docker run commands
 ```
 cd src/gpu/DNNMark
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 ./setup.sh HIP
-docker run --rm -v ${PWD}:${PWD} -w ${PWD}/build -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 make
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 ./setup.sh HIP
+docker run --rm -v ${PWD}:${PWD} -w ${PWD}/build -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 make
 ```
 
 DNNMark uses MIOpen kernels, which are unable to be compiled on-the-fly in gem5.
@@ -38,7 +38,7 @@
 To generate the MIOpen kernels:
 ```
 cd src/gpu/DNNMark
-docker run --rm -v ${PWD}:${PWD} -v${PWD}/cachefiles:/root/.cache/miopen/2.9.0 -w ${PWD} gcr.io/gem5-test/gcn-gpu:v22-0 python3 generate_cachefiles.py cachefiles.csv [--gfx-version={gfx801,gfx803}] [--num-cus=N]
+docker run --rm -v ${PWD}:${PWD} -v${PWD}/cachefiles:/root/.cache/miopen/2.9.0 -w ${PWD} gcr.io/gem5-test/gcn-gpu:v22-1 python3 generate_cachefiles.py cachefiles.csv [--gfx-version={gfx801,gfx803}] [--num-cus=N]
 ```
 
 Due to the large amounts of memory that need to be set up for DNNMark, we have
@@ -56,13 +56,13 @@
 To build GCN3_X86:
 ```
 # Working directory is your gem5 directory
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 scons -sQ -j$(nproc) build/GCN3_X86/gem5.opt
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 scons -sQ -j$(nproc) build/GCN3_X86/gem5.opt
 ```
 
 To run one of the benchmarks (fwd softmax) in gem5:
 ```
 # Assuming gem5 and gem5-resources are sub-directories of the current directory
-docker run --rm -v ${PWD}:${PWD} -v ${PWD}/gem5-resources/src/gpu/DNNMark/cachefiles:/root/.cache/miopen/2.9.0 -w ${PWD} gcr.io/gem5-test/gcn-gpu:v22-0 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n3 --benchmark-root=gem5-resources/src/gpu/DNNMark/build/benchmarks/test_fwd_softmax -cdnnmark_test_fwd_softmax --options="-config gem5-resources/src/gpu/DNNMark/config_example/softmax_config.dnnmark -mmap gem5-resources/src/gpu/DNNMark/mmap.bin"
+docker run --rm -v ${PWD}:${PWD} -v ${PWD}/gem5-resources/src/gpu/DNNMark/cachefiles:/root/.cache/miopen/2.9.0 -w ${PWD} gcr.io/gem5-test/gcn-gpu:v22-1 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n3 --benchmark-root=gem5-resources/src/gpu/DNNMark/build/benchmarks/test_fwd_softmax -cdnnmark_test_fwd_softmax --options="-config gem5-resources/src/gpu/DNNMark/config_example/softmax_config.dnnmark -mmap gem5-resources/src/gpu/DNNMark/mmap.bin"
 ```
 
 Information from the original DNNMark README included below.
diff --git a/src/gpu/halo-finder/README.md b/src/gpu/halo-finder/README.md
index e9b144a..bb8266d 100644
--- a/src/gpu/halo-finder/README.md
+++ b/src/gpu/halo-finder/README.md
@@ -59,4 +59,4 @@
 
 ## Pre-built binary
 
-<http://dist.gem5.org/dist/v22-0/test-progs/halo-finder/ForceTreeTest>
+<http://dist.gem5.org/dist/v22-1/test-progs/halo-finder/ForceTreeTest>
diff --git a/src/gpu/heterosync/README.md b/src/gpu/heterosync/README.md
index 30a03a7..7b7f1f3 100644
--- a/src/gpu/heterosync/README.md
+++ b/src/gpu/heterosync/README.md
@@ -21,7 +21,7 @@
 ## Compilation
 ```
 cd src/gpu/heterosync
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 make release-gfx8
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 make release-gfx8
 ```
 
 The release-gfx8 target builds for gfx801, a GCN3-based APU, and gfx803, a
@@ -33,12 +33,12 @@
 HeteroSync has multiple applications that can be run (see below).  For example, to run sleepMutex with 10 ld/st per thread, 16 WGs, and 4 iterations of the critical section:
 
 ```
-docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/gcn-gpu:v22-0 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n 3 -c bin/allSyncPrims-1kernel --options="sleepMutex 10 16 4"
+docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/gcn-gpu:v22-1 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n 3 -c bin/allSyncPrims-1kernel --options="sleepMutex 10 16 4"
 ```
 
 ## Pre-built binary
 
-<http://dist.gem5.org/dist/v22-0/test-progs/heterosync/gcn3/allSyncPrims-1kernel>
+<http://dist.gem5.org/dist/v22-1/test-progs/heterosync/gcn3/allSyncPrims-1kernel>
 
 Information from original HeteroSync README included below:
 
diff --git a/src/gpu/hip-samples/README.md b/src/gpu/hip-samples/README.md
index 6f0eeb4..84a0935 100644
--- a/src/gpu/hip-samples/README.md
+++ b/src/gpu/hip-samples/README.md
@@ -28,7 +28,7 @@
 
 ```
 cd src/gpu/hip-samples
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 make
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 make
 ```
 
 Individual programs can be made by specifying the name of the program
@@ -38,18 +38,18 @@
 
 ## Pre-built binary
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/2dshfl>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/2dshfl>
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/dynamic_shared>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/dynamic_shared>
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/inline_asm>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/inline_asm>
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/MatrixTranspose>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/MatrixTranspose>
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/sharedMemory>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/sharedMemory>
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/shfl>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/shfl>
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/stream>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/stream>
 
-<http://dist.gem5.org/dist/v22-0/test-progs/hip-samples/unroll>
+<http://dist.gem5.org/dist/v22-1/test-progs/hip-samples/unroll>
diff --git a/src/gpu/hsa-agent-pkt/README.md b/src/gpu/hsa-agent-pkt/README.md
index 404d352..5aa1130 100644
--- a/src/gpu/hsa-agent-pkt/README.md
+++ b/src/gpu/hsa-agent-pkt/README.md
@@ -29,7 +29,7 @@
 
 ```
 cd src/gpu/hsa-agent-pkt
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 make gfx8-apu
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 make gfx8-apu
 ```
 
 The compiled binary can be found in `src/gpu/hsa-agent-pkt/bin`
diff --git a/src/gpu/lulesh/README.md b/src/gpu/lulesh/README.md
index 1ecc137..5cda401 100644
--- a/src/gpu/lulesh/README.md
+++ b/src/gpu/lulesh/README.md
@@ -20,7 +20,7 @@
 ## Compilation and Running
 ```
 cd src/gpu/lulesh
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 make
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 make
 ```
 
 By default, the makefile builds for gfx801, and is placed in the `src/gpu/lulesh/bin` folder.
@@ -30,7 +30,7 @@
 
 ```
 # Working directory is your gem5 directory
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 scons -sQ -j$(nproc) build/GCN3_X86/gem5.opt
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 scons -sQ -j$(nproc) build/GCN3_X86/gem5.opt
 ```
 
 The following command shows how to run lulesh
@@ -42,7 +42,7 @@
 
 ```
 # Assuming gem5 and gem5-resources are in your working directory
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n3 --mem-size=8GB --benchmark-root=gem5-resources/src/gpu/lulesh/bin -clulesh
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n3 --mem-size=8GB --benchmark-root=gem5-resources/src/gpu/lulesh/bin -clulesh
 ```
 
 ## Pre-built binary
diff --git a/src/gpu/pennant/README.md b/src/gpu/pennant/README.md
index d326687..4771f88 100644
--- a/src/gpu/pennant/README.md
+++ b/src/gpu/pennant/README.md
@@ -20,7 +20,7 @@
 
 ```
 cd src/gpu/pennant
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 make
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 make
 ```
 
 By default, the binary is built for gfx801 and is placed in `src/gpu/pennant/build`
@@ -31,7 +31,7 @@
 
 ```
 # Assuming gem5 and gem5-resources are in your working directory
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n3 --benchmark-root=gem5-resources/src/gpu/pennant/build -cpennant --options="gem5-resources/src/gpu/pennant/test/noh/noh.pnt"
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n3 --benchmark-root=gem5-resources/src/gpu/pennant/build -cpennant --options="gem5-resources/src/gpu/pennant/test/noh/noh.pnt"
 ```
 
 The output gets placed in `src/gpu/pennant/test/noh/`, and the file `noh.xy`
@@ -40,7 +40,7 @@
 
 ## Pre-built binary
 
-<http://dist.gem5.org/dist/v22-0/test-progs/pennant/pennant>
+<http://dist.gem5.org/dist/v22-1/test-progs/pennant/pennant>
 
 The information from the original PENNANT README is included below.
 
diff --git a/src/gpu/square/README.md b/src/gpu/square/README.md
index 02e7d61..1e16d76 100644
--- a/src/gpu/square/README.md
+++ b/src/gpu/square/README.md
@@ -18,14 +18,14 @@
 By default, square will build for all supported GPU types (gfx801, gfx803)
 ```
 cd src/gpu/square
-docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-0 make
+docker run --rm -v ${PWD}:${PWD} -w ${PWD} -u $UID:$GID gcr.io/gem5-test/gcn-gpu:v22-1 make
 ```
 
 The compiled binary can be found in the `bin` directory.
 
 ## Pre-built binary
 
-A pre-built binary can be found at <http://dist.gem5.org/dist/v22-0/test-progs/square/square>.
+A pre-built binary can be found at <http://dist.gem5.org/dist/v22-1/test-progs/square/square>.
 
 ## Compiling GCN3_X86/gem5.opt
 
@@ -34,11 +34,11 @@
 ```
 git clone https://gem5.googlesource.com/public/gem5
 cd gem5
-docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/gcn-gpu:v22-0 scons build/GCN3_X86/gem5.opt -j <num cores>
+docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/gcn-gpu:v22-1 scons build/GCN3_X86/gem5.opt -j <num cores>
 ```
 
 ## Running Square on GCN3_X86/gem5.opt
 
 ```
-docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/gcn-gpu:v22-0 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n 3 -c bin/square
+docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/gcn-gpu:v22-1 gem5/build/GCN3_X86/gem5.opt gem5/configs/example/apu_se.py -n 3 -c bin/square
 ```
diff --git a/src/linux-kernel/README.md b/src/linux-kernel/README.md
index 9614287..5d83de6 100644
--- a/src/linux-kernel/README.md
+++ b/src/linux-kernel/README.md
@@ -80,11 +80,11 @@
 The pre-build compiled x86 Linux binaries can be downloaded from the following
 links:
 
-- [vmlinux-4.4.186](http://dist.gem5.org/dist/v22-0/kernels/x86/static/vmlinux-4.4.186)
-- [vmlinux-4.9.186](http://dist.gem5.org/dist/v22-0/kernels/x86/static/vmlinux-4.9.186)
-- [vmlinux-4.14.134](http://dist.gem5.org/dist/v22-0/kernels/x86/static/vmlinux-4.14.134)
-- [vmlinux-4.19.83](http://dist.gem5.org/dist/v22-0/kernels/x86/static/vmlinux-4.19.83)
-- [vmlinux-5.4.49](http://dist.gem5.org/dist/v22-0/kernels/x86/static/vmlinux-5.4.49)
+- [vmlinux-4.4.186](http://dist.gem5.org/dist/v22-1/kernels/x86/static/vmlinux-4.4.186)
+- [vmlinux-4.9.186](http://dist.gem5.org/dist/v22-1/kernels/x86/static/vmlinux-4.9.186)
+- [vmlinux-4.14.134](http://dist.gem5.org/dist/v22-1/kernels/x86/static/vmlinux-4.14.134)
+- [vmlinux-4.19.83](http://dist.gem5.org/dist/v22-1/kernels/x86/static/vmlinux-4.19.83)
+- [vmlinux-5.4.49](http://dist.gem5.org/dist/v22-1/kernels/x86/static/vmlinux-5.4.49)
 
 **Note on ARM Kernel Binaries:** A cross-compiler is needed to compile ARM
 kernel binaries on a x86 machine. We used `gcc 10.3.0
@@ -93,13 +93,13 @@
 
 The pre-build compiled ARM Linux binaries can be downloaded from the following links:
 
-- [arm64-vmlinux-4.4.186](http://dist.gem5.org/dist/v22-0/kernels/arm/static/arm64-vmlinux-4.4.186)
-- [arm64-vmlinux-4.9.186](http://dist.gem5.org/dist/v22-0/kernels/arm/static/arm64-vmlinux-4.9.186)
-- [arm64-vmlinux-4.14.134](http://dist.gem5.org/dist/v22-0/kernels/arm/static/arm64-vmlinux-4.14.134)
-- [arm64-vmlinux-4.19.83](http://dist.gem5.org/dist/v22-0/kernels/arm/static/arm64-vmlinux-4.19.83)
-- [arm64-vmlinux-5.10.110](http://dist.gem5.org/dist/v22-0/kernels/arm/static/arm64-vmlinux-5.10.110)
-- [arm64-vmlinux-5.15.36](http://dist.gem5.org/dist/v22-0/kernels/arm/static/arm64-vmlinux-5.15.36)
-- [arm64-vmlinux-5.4.49](http://dist.gem5.org/dist/v22-0/kernels/arm/static/arm64-vmlinux-5.4.49)
+- [arm64-vmlinux-4.4.186](http://dist.gem5.org/dist/v22-1/kernels/arm/static/arm64-vmlinux-4.4.186)
+- [arm64-vmlinux-4.9.186](http://dist.gem5.org/dist/v22-1/kernels/arm/static/arm64-vmlinux-4.9.186)
+- [arm64-vmlinux-4.14.134](http://dist.gem5.org/dist/v22-1/kernels/arm/static/arm64-vmlinux-4.14.134)
+- [arm64-vmlinux-4.19.83](http://dist.gem5.org/dist/v22-1/kernels/arm/static/arm64-vmlinux-4.19.83)
+- [arm64-vmlinux-5.10.110](http://dist.gem5.org/dist/v22-1/kernels/arm/static/arm64-vmlinux-5.10.110)
+- [arm64-vmlinux-5.15.36](http://dist.gem5.org/dist/v22-1/kernels/arm/static/arm64-vmlinux-5.15.36)
+- [arm64-vmlinux-5.4.49](http://dist.gem5.org/dist/v22-1/kernels/arm/static/arm64-vmlinux-5.4.49)
 
 Alternatively to the vanilla kernel + linux-configs described above, it is also
 possible to compile a gem5 port of the Linux Kernel 4.14.0 for ARM. The
diff --git a/src/lupv/README.md b/src/lupv/README.md
index 648b5b5..040a374 100644
--- a/src/lupv/README.md
+++ b/src/lupv/README.md
@@ -68,7 +68,7 @@
 A pre-built bootloader/kernel binary can be obtained from
 [here](http://dist.gem5.org/dist/v21-2/kernels/riscv/static/lupio-linux).
 =======
-A pre-built bootloader/kernel binary can be obtained from [here](http://dist.gem5.org/dist/v22-0/kernels/riscv/static/lupio-linux).
+A pre-built bootloader/kernel binary can be obtained from [here](http://dist.gem5.org/dist/v22-1/kernels/riscv/static/lupio-linux).
 >>>>>>> stable
 
 ## Root filesystem
@@ -142,5 +142,5 @@
 A pre-built, gzipped, image can be obtained
 [here](http://dist.gem5.org/dist/v21-2/images/riscv/busybox/riscv-lupio-busybox.img.gz).
 =======
-A pre-built, gzipped, image can be obtained [here](http://dist.gem5.org/dist/v22-0/images/riscv/busybox/riscv-lupio-busybox.img.gz).
+A pre-built, gzipped, image can be obtained [here](http://dist.gem5.org/dist/v22-1/images/riscv/busybox/riscv-lupio-busybox.img.gz).
 >>>>>>> stable
diff --git a/src/npb/README.md b/src/npb/README.md
index 0f59edc..f485c94 100644
--- a/src/npb/README.md
+++ b/src/npb/README.md
@@ -72,7 +72,7 @@
 ```
 
 Once this process succeeds, the created disk image can be found on `npb/npb-image/npb`.
-A disk image already created following the above instructions can be found, gzipped, [here](http://dist.gem5.org/dist/v22-0/images/x86/ubuntu-18-04/npb.img.gz).
+A disk image already created following the above instructions can be found, gzipped, [here](http://dist.gem5.org/dist/v22-1/images/x86/ubuntu-18-04/npb.img.gz).
 
 ## Simulating NPB using an example script
 
diff --git a/src/riscv-fs/README.md b/src/riscv-fs/README.md
index 90a3fa9..b165252 100644
--- a/src/riscv-fs/README.md
+++ b/src/riscv-fs/README.md
@@ -106,7 +106,7 @@
 ```
 
 This should generate a `vmlinux` image in the `linux` directory.
-A pre-built RISC-V 5.10 linux kernel can be downloaded [here](http://dist.gem5.org/dist/v22-0/kernels/riscv/static/vmlinux-5.10).
+A pre-built RISC-V 5.10 linux kernel can be downloaded [here](http://dist.gem5.org/dist/v22-1/kernels/riscv/static/vmlinux-5.10).
 
 ## Bootloader (bbl)
 
@@ -136,7 +136,7 @@
 ```
 
 This will produce a `bbl` bootloader binary with linux kernel in `riscv-pk/build` directory.
-A pre-built copy of this bootloard binary, with the linux kernel can be downloaded [here](http://dist.gem5.org/dist/v22-0/kernels/riscv/static/bootloader-vmlinux-5.10).
+A pre-built copy of this bootloard binary, with the linux kernel can be downloaded [here](http://dist.gem5.org/dist/v22-1/kernels/riscv/static/bootloader-vmlinux-5.10).
 
 ## Busy Box
 
@@ -220,7 +220,7 @@
 ```
 
 The disk image `riscv_disk` is ready to use.
-A pre-built, gzipped, disk image can be downloaded [here](http://dist.gem5.org/dist/v22-0/images/riscv/busybox/riscv-disk.img.gz).
+A pre-built, gzipped, disk image can be downloaded [here](http://dist.gem5.org/dist/v22-1/images/riscv/busybox/riscv-disk.img.gz).
 
 **Note:** If you need to resize the disk image once it is created, you can do the following:
 
diff --git a/src/riscv-ubuntu/README.md b/src/riscv-ubuntu/README.md
index e00918d..66915a6 100644
--- a/src/riscv-ubuntu/README.md
+++ b/src/riscv-ubuntu/README.md
@@ -212,7 +212,7 @@
 
 # Pre-built disk image
 
-A pre-build, gzipped, disk image is available at <http://dist.gem5.org/dist/v22-0/images/riscv/ubuntu-20-04/riscv-ubuntu-20220318.img.gz>. **Note**: The password set for the `ubuntu` user is `helloworld`.
+A pre-build, gzipped, disk image is available at <http://dist.gem5.org/dist/v22-1/images/riscv/ubuntu-20-04/riscv-ubuntu-20220318.img.gz>. **Note**: The password set for the `ubuntu` user is `helloworld`.
 
 # Using the Disk Image
 This disk image is used in the following gem5 example RISCV config files, found within the gem5 repository:
diff --git a/src/x86-ubuntu/README.md b/src/x86-ubuntu/README.md
index 114db6b..021525a 100644
--- a/src/x86-ubuntu/README.md
+++ b/src/x86-ubuntu/README.md
@@ -76,7 +76,7 @@
 ```
 
 Once this process succeeds, the disk image can be found on `x86-ubuntu/x86-ubuntu-image/x86-ubuntu`.
-A disk image already created following the above instructions can be found, gzipped, [here](http://dist.gem5.org/dist/v22-0/images/x86/ubuntu-18-04/x86-ubuntu.img.gz).
+A disk image already created following the above instructions can be found, gzipped, [here](http://dist.gem5.org/dist/v22-1/images/x86/ubuntu-18-04/x86-ubuntu.img.gz).
 
 
 ## Example Run Scripts