The H-extension is always enabled by default for latest QEMU so let
us update all README files.
Signed-off-by: Anup Patel <
apa...@ventanamicro.com>
---
docs/riscv/riscv32-nested-mmu-test-qemu.txt | 6 +++---
docs/riscv/riscv32-qemu.txt | 4 ++--
docs/riscv/riscv64-nested-mmu-test-qemu.txt | 6 +++---
docs/riscv/riscv64-qemu.txt | 4 ++--
tests/riscv/virt32/basic/README | 4 ++--
tests/riscv/virt32/linux/README | 4 ++--
tests/riscv/virt64/basic/README | 4 ++--
tests/riscv/virt64/linux/README | 4 ++--
8 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/docs/riscv/riscv32-nested-mmu-test-qemu.txt b/docs/riscv/riscv32-nested-mmu-test-qemu.txt
index 273d0ed2..425936f4 100644
--- a/docs/riscv/riscv32-nested-mmu-test-qemu.txt
+++ b/docs/riscv/riscv32-nested-mmu-test-qemu.txt
@@ -4,7 +4,7 @@ This section of readme explains how to build & run Xvisor RISC-V 32bit
nested MMU test-suite on Virt machine emulated by QEMU RISC-V.
Please follow the steps below for nested MMU test-suite on QEMU virt
-machine (v5.1 or higher):
+machine (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv64-unknown-linux-gnu-
@@ -32,9 +32,9 @@ machine (v5.1 or higher):
# cd <xvisor_source_directory>
[9. Run nested MMU test-suite]
- # qemu-system-riscv32 -cpu rv32,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -append 'vmm.bootcmd="wboxtest run_groups 1 nested_mmu"'
+ # qemu-system-riscv32 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -append 'vmm.bootcmd="wboxtest run_groups 1 nested_mmu"'
OR
- # qemu-system-riscv32 -cpu rv32,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin
+ # qemu-system-riscv32 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin
XVisor# wboxtest run_groups 1 nested_mmu
(Note: replace all <> brackets based on your workspace)
diff --git a/docs/riscv/riscv32-qemu.txt b/docs/riscv/riscv32-qemu.txt
index c9d4a14d..7156e0eb 100644
--- a/docs/riscv/riscv32-qemu.txt
+++ b/docs/riscv/riscv32-qemu.txt
@@ -5,7 +5,7 @@ Virt machine emulated by QEMU RISC-V.
Please follow the steps below to build & run Linux kernel with Busybox RootFS
on Virt32 (paravirtualized RISC-V 32bit) Guest with Xvisor RISC-V 32bit running
-on QEMU virt machine (v5.1 or higher):
+on QEMU virt machine (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv64-unknown-linux-gnu-
@@ -63,7 +63,7 @@ on QEMU virt machine (v5.1 or higher):
# genext2fs -B 1024 -b 32768 -d ./build/disk ./build/disk.img
[14. Launch QEMU]
- # qemu-system-riscv32 -cpu rv32,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
+ # qemu-system-riscv32 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
[15. Kick Guest0 to start Basic Firmware]
XVisor# guest kick guest0
diff --git a/docs/riscv/riscv64-nested-mmu-test-qemu.txt b/docs/riscv/riscv64-nested-mmu-test-qemu.txt
index 5541db42..6e8688a1 100644
--- a/docs/riscv/riscv64-nested-mmu-test-qemu.txt
+++ b/docs/riscv/riscv64-nested-mmu-test-qemu.txt
@@ -4,7 +4,7 @@ This section of readme explains how to build & run Xvisor RISC-V 64bit
nested MMU test-suite on Virt machine emulated by QEMU RISC-V.
Please follow the steps below for nested MMU test-suite on QEMU virt
-machine (v5.1 or higher):
+machine (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv64-unknown-linux-gnu-
@@ -32,9 +32,9 @@ machine (v5.1 or higher):
# cd <xvisor_source_directory>
[9. Run nested MMU test-suite]
- # qemu-system-riscv64 -cpu rv64,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -append 'vmm.bootcmd="wboxtest run_groups 1 nested_mmu"'
+ # qemu-system-riscv64 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -append 'vmm.bootcmd="wboxtest run_groups 1 nested_mmu"'
OR
- # qemu-system-riscv64 -cpu rv64,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin
+ # qemu-system-riscv64 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin
XVisor# wboxtest run_groups 1 nested_mmu
(Note: replace all <> brackets based on your workspace)
diff --git a/docs/riscv/riscv64-qemu.txt b/docs/riscv/riscv64-qemu.txt
index 0ceb5cc7..ad0b740b 100644
--- a/docs/riscv/riscv64-qemu.txt
+++ b/docs/riscv/riscv64-qemu.txt
@@ -5,7 +5,7 @@ Virt machine emulated by QEMU RISC-V.
Please follow the steps below to build & run Linux kernel with Busybox RootFS
on Virt64 (paravirtualized RISC-V 64bit) Guest with Xvisor RISC-V 64bit running
-on QEMU virt machine (v5.1 or higher):
+on QEMU virt machine (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv64-unknown-linux-gnu-
@@ -63,7 +63,7 @@ on QEMU virt machine (v5.1 or higher):
# genext2fs -B 1024 -b 32768 -d ./build/disk ./build/disk.img
[14. Launch QEMU]
- # qemu-system-riscv64 -cpu rv64,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
+ # qemu-system-riscv64 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/generic/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
[15. Kick Guest0 to start Basic Firmware]
XVisor# guest kick guest0
diff --git a/tests/riscv/virt32/basic/README b/tests/riscv/virt32/basic/README
index 44250a33..7c0b80c1 100644
--- a/tests/riscv/virt32/basic/README
+++ b/tests/riscv/virt32/basic/README
@@ -4,7 +4,7 @@ The basic firmware currently sets up PIC, Timer, and UART and emulates
a dummy terminal which reponds to various commands.
Please follow the steps below to build & run Basic Firmware on Virt32
-Guest with Xvisor running on QEMU (v3.1.50 or higher):
+Guest with Xvisor running on QEMU (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv32-unknown-linux-gnu-
@@ -34,7 +34,7 @@ Guest with Xvisor running on QEMU (v3.1.50 or higher):
# genext2fs -B 1024 -b 32768 -d ./build/disk ./build/disk.img
[7. Launch QEMU]
- # qemu-system-riscv32 -cpu rv32,x-h=true -M virt -m 512M -display none -serial stdio -bios <opensbi_build_directory>/platform/qemu/virt/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append "vmm.bootcmd=\"vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt\""
+ # qemu-system-riscv32 -M virt -m 512M -display none -serial stdio -bios <opensbi_build_directory>/platform/qemu/virt/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append "vmm.bootcmd=\"vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt\""
[8. Kick Guest0 for starting Basic Firmware]
XVisor# guest kick guest0
diff --git a/tests/riscv/virt32/linux/README b/tests/riscv/virt32/linux/README
index c02233b8..d8b08ddd 100644
--- a/tests/riscv/virt32/linux/README
+++ b/tests/riscv/virt32/linux/README
@@ -13,7 +13,7 @@ following url:
http://www.kernel.org
Please follow the steps below to build & run Linux kernel with Busybox
RootFS on Virt32 (paravirtualized RISC-V 32bit) Guest with Xvisor running
-on QEMU model (v5.1 or higher):
+on QEMU model (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv64-unknown-linux-gnu-
@@ -71,7 +71,7 @@ on QEMU model (v5.1 or higher):
# genext2fs -B 1024 -b 32768 -d ./build/disk ./build/disk.img
[14. Launch QEMU]
- # qemu-system-riscv32 -cpu rv32,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/qemu/virt32/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
+ # qemu-system-riscv32 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/qemu/virt32/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
[15. Kick Guest0 to start Basic Firmware]
XVisor# guest kick guest0
diff --git a/tests/riscv/virt64/basic/README b/tests/riscv/virt64/basic/README
index ad710751..e1b44494 100644
--- a/tests/riscv/virt64/basic/README
+++ b/tests/riscv/virt64/basic/README
@@ -4,7 +4,7 @@ The basic firmware currently sets up PIC, Timer, and UART and emulates
a dummy terminal which reponds to various commands.
Please follow the steps below to build & run Basic Firmware on Virt64
-Guest with Xvisor running on QEMU (v3.1.50 or higher):
+Guest with Xvisor running on QEMU (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv64-unknown-linux-gnu-
@@ -34,7 +34,7 @@ Guest with Xvisor running on QEMU (v3.1.50 or higher):
# genext2fs -B 1024 -b 32768 -d ./build/disk ./build/disk.img
[7. Launch QEMU]
- # qemu-system-riscv64 -cpu rv64,x-h=true -M virt -m 512M -display none -serial stdio -bios <opensbi_build_directory>/platform/qemu/virt/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append "vmm.bootcmd=\"vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt\""
+ # qemu-system-riscv64 -M virt -m 512M -display none -serial stdio -bios <opensbi_build_directory>/platform/qemu/virt/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append "vmm.bootcmd=\"vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt\""
[8. Kick Guest0 for starting Basic Firmware]
XVisor# guest kick guest0
diff --git a/tests/riscv/virt64/linux/README b/tests/riscv/virt64/linux/README
index ea3386b8..16466a4b 100644
--- a/tests/riscv/virt64/linux/README
+++ b/tests/riscv/virt64/linux/README
@@ -13,7 +13,7 @@ following url:
http://www.kernel.org
Please follow the steps below to build & run Linux kernel with Busybox
RootFS on Virt64 (paravirtualized RISC-V 64bit) Guest with Xvisor running
-on QEMU model (v5.1 or higher):
+on QEMU model (v8 or higher):
[1. Build environment for Xvisor]
# CROSS_COMPILE=riscv64-unknown-linux-gnu-
@@ -71,7 +71,7 @@ on QEMU model (v5.1 or higher):
# genext2fs -B 1024 -b 32768 -d ./build/disk ./build/disk.img
[14. Launch QEMU]
- # qemu-system-riscv64 -cpu rv64,x-h=true -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/qemu/virt64/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
+ # qemu-system-riscv64 -M virt -m 512M -nographic -bios <opensbi_source_directory>/build/platform/qemu/virt64/firmware/fw_jump.bin -kernel ./build/vmm.bin -initrd ./build/disk.img -append 'vmm.bootcmd="vfs mount initrd /;vfs run /boot.xscript;vfs cat /system/banner.txt"'
[15. Kick Guest0 to start Basic Firmware]
XVisor# guest kick guest0
--
2.34.1