1'virt' Generic Virtual Platform (``virt``) 2========================================== 3 4The ``virt`` board is a platform which does not correspond to any real hardware; 5it is designed for use in virtual machines. It is the recommended board type 6if you simply want to run a guest such as Linux and do not care about 7reproducing the idiosyncrasies and limitations of a particular bit of 8real-world hardware. 9 10Supported devices 11----------------- 12 13The ``virt`` machine supports the following devices: 14 15* Up to 512 generic RV32GC/RV64GC cores, with optional extensions 16* Core Local Interruptor (CLINT) 17* Platform-Level Interrupt Controller (PLIC) 18* CFI parallel NOR flash memory 19* 1 NS16550 compatible UART 20* 1 Google Goldfish RTC 21* 1 SiFive Test device 22* 8 virtio-mmio transport devices 23* 1 generic PCIe host bridge 24* The fw_cfg device that allows a guest to obtain data from QEMU 25 26The hypervisor extension has been enabled for the default CPU, so virtual 27machines with hypervisor extension can simply be used without explicitly 28declaring. 29 30Hardware configuration information 31---------------------------------- 32 33The ``virt`` machine automatically generates a device tree blob ("dtb") 34which it passes to the guest, if there is no ``-dtb`` option. This provides 35information about the addresses, interrupt lines and other configuration of 36the various devices in the system. Guest software should discover the devices 37that are present in the generated DTB. 38 39If users want to provide their own DTB, they can use the ``-dtb`` option. 40These DTBs should have the following requirements: 41 42* The number of subnodes of the /cpus node should match QEMU's ``-smp`` option 43* The /memory reg size should match QEMU’s selected ram_size via ``-m`` 44* Should contain a node for the CLINT device with a compatible string 45 "riscv,clint0" if using with OpenSBI BIOS images 46 47Boot options 48------------ 49 50The ``virt`` machine can start using the standard -kernel functionality 51for loading a Linux kernel, a VxWorks kernel, an S-mode U-Boot bootloader 52with the default OpenSBI firmware image as the -bios. It also supports 53the recommended RISC-V bootflow: U-Boot SPL (M-mode) loads OpenSBI fw_dynamic 54firmware and U-Boot proper (S-mode), using the standard -bios functionality. 55 56Using flash devices 57------------------- 58 59By default, the first flash device (pflash0) is expected to contain 60S-mode firmware code. It can be configured as read-only, with the 61second flash device (pflash1) available to store configuration data. 62 63For example, booting edk2 looks like 64 65.. code-block:: bash 66 67 $ qemu-system-riscv64 \ 68 -blockdev node-name=pflash0,driver=file,read-only=on,filename=<edk2_code> \ 69 -blockdev node-name=pflash1,driver=file,filename=<edk2_vars> \ 70 -M virt,pflash0=pflash0,pflash1=pflash1 \ 71 ... other args .... 72 73For TCG guests only, it is also possible to boot M-mode firmware from 74the first flash device (pflash0) by additionally passing ``-bios 75none``, as in 76 77.. code-block:: bash 78 79 $ qemu-system-riscv64 \ 80 -bios none \ 81 -blockdev node-name=pflash0,driver=file,read-only=on,filename=<m_mode_code> \ 82 -M virt,pflash0=pflash0 \ 83 ... other args .... 84 85Firmware images used for pflash must be exactly 32 MiB in size. 86 87riscv-iommu support 88------------------- 89 90The board has support for the riscv-iommu-pci device by using the following 91command line: 92 93.. code-block:: bash 94 95 $ qemu-system-riscv64 -M virt -device riscv-iommu-pci (...) 96 97It also has support for the riscv-iommu-sys platform device: 98 99.. code-block:: bash 100 101 $ qemu-system-riscv64 -M virt,iommu-sys=on (...) 102 103Refer to :ref:`riscv-iommu` for more information on how the RISC-V IOMMU support 104works. 105 106Machine-specific options 107------------------------ 108 109The following machine-specific options are supported: 110 111- aclint=[on|off] 112 113 When this option is "on", ACLINT devices will be emulated instead of 114 SiFive CLINT. When not specified, this option is assumed to be "off". 115 This option is restricted to the TCG accelerator. 116 117- acpi=[on|off|auto] 118 119 When this option is "on" (which is the default), ACPI tables are generated and 120 exposed as firmware tables etc/acpi/rsdp and etc/acpi/tables. 121 122- aia=[none|aplic|aplic-imsic] 123 124 This option allows selecting interrupt controller defined by the AIA 125 (advanced interrupt architecture) specification. The "aia=aplic" selects 126 APLIC (advanced platform level interrupt controller) to handle wired 127 interrupts whereas the "aia=aplic-imsic" selects APLIC and IMSIC (incoming 128 message signaled interrupt controller) to handle both wired interrupts and 129 MSIs. When not specified, this option is assumed to be "none" which selects 130 SiFive PLIC to handle wired interrupts. 131 132- aia-guests=nnn 133 134 The number of per-HART VS-level AIA IMSIC pages to be emulated for a guest 135 having AIA IMSIC (i.e. "aia=aplic-imsic" selected). When not specified, 136 the default number of per-HART VS-level AIA IMSIC pages is 0. 137 138- iommu-sys=[on|off] 139 140 Enables the riscv-iommu-sys platform device. Defaults to 'off'. 141 142Running Linux kernel 143-------------------- 144 145Linux mainline v5.12 release is tested at the time of writing. To build a 146Linux mainline kernel that can be booted by the ``virt`` machine in 14764-bit mode, simply configure the kernel using the defconfig configuration: 148 149.. code-block:: bash 150 151 $ export ARCH=riscv 152 $ export CROSS_COMPILE=riscv64-linux- 153 $ make defconfig 154 $ make 155 156To boot the newly built Linux kernel in QEMU with the ``virt`` machine: 157 158.. code-block:: bash 159 160 $ qemu-system-riscv64 -M virt -smp 4 -m 2G \ 161 -display none -serial stdio \ 162 -kernel arch/riscv/boot/Image \ 163 -initrd /path/to/rootfs.cpio \ 164 -append "root=/dev/ram" 165 166To build a Linux mainline kernel that can be booted by the ``virt`` machine 167in 32-bit mode, use the rv32_defconfig configuration. A patch is required to 168fix the 32-bit boot issue for Linux kernel v5.12. 169 170.. code-block:: bash 171 172 $ export ARCH=riscv 173 $ export CROSS_COMPILE=riscv64-linux- 174 $ curl https://patchwork.kernel.org/project/linux-riscv/patch/20210627135117.28641-1-bmeng.cn@gmail.com/mbox/ > riscv.patch 175 $ git am riscv.patch 176 $ make rv32_defconfig 177 $ make 178 179Replace ``qemu-system-riscv64`` with ``qemu-system-riscv32`` in the command 180line above to boot the 32-bit Linux kernel. A rootfs image containing 32-bit 181applications shall be used in order for kernel to boot to user space. 182 183Running U-Boot 184-------------- 185 186U-Boot mainline v2021.04 release is tested at the time of writing. To build an 187S-mode U-Boot bootloader that can be booted by the ``virt`` machine, use 188the qemu-riscv64_smode_defconfig with similar commands as described above for Linux: 189 190.. code-block:: bash 191 192 $ export CROSS_COMPILE=riscv64-linux- 193 $ make qemu-riscv64_smode_defconfig 194 195Boot the 64-bit U-Boot S-mode image directly: 196 197.. code-block:: bash 198 199 $ qemu-system-riscv64 -M virt -smp 4 -m 2G \ 200 -display none -serial stdio \ 201 -kernel /path/to/u-boot.bin 202 203To test booting U-Boot SPL which in M-mode, which in turn loads a FIT image 204that bundles OpenSBI fw_dynamic firmware and U-Boot proper (S-mode) together, 205build the U-Boot images using riscv64_spl_defconfig: 206 207.. code-block:: bash 208 209 $ export CROSS_COMPILE=riscv64-linux- 210 $ export OPENSBI=/path/to/opensbi-riscv64-generic-fw_dynamic.bin 211 $ make qemu-riscv64_spl_defconfig 212 213The minimal QEMU commands to run U-Boot SPL are: 214 215.. code-block:: bash 216 217 $ qemu-system-riscv64 -M virt -smp 4 -m 2G \ 218 -display none -serial stdio \ 219 -bios /path/to/u-boot-spl \ 220 -device loader,file=/path/to/u-boot.itb,addr=0x80200000 221 222To test 32-bit U-Boot images, switch to use qemu-riscv32_smode_defconfig and 223riscv32_spl_defconfig builds, and replace ``qemu-system-riscv64`` with 224``qemu-system-riscv32`` in the command lines above to boot the 32-bit U-Boot. 225 226Enabling TPM 227------------ 228 229A TPM device can be connected to the virt board by following the steps below. 230 231First launch the TPM emulator: 232 233.. code-block:: bash 234 235 $ swtpm socket --tpm2 -t -d --tpmstate dir=/tmp/tpm \ 236 --ctrl type=unixio,path=swtpm-sock 237 238Then launch QEMU with some additional arguments to link a TPM device to the backend: 239 240.. code-block:: bash 241 242 $ qemu-system-riscv64 \ 243 ... other args .... \ 244 -chardev socket,id=chrtpm,path=swtpm-sock \ 245 -tpmdev emulator,id=tpm0,chardev=chrtpm \ 246 -device tpm-tis-device,tpmdev=tpm0 247 248The TPM device can be seen in the memory tree and the generated device 249tree and should be accessible from the guest software. 250