system/arm/virt.rst

7 real hardware; it is designed for use in virtual machines.
17 that VM migration will work between QEMU versions. For instance the
21 is not guaranteed to work between different QEMU releases for
35 - Either one or two PL011 UARTs for the NonSecure World
52   - A second PL061 GPIO controller, with GPIO lines for triggering
77 - ``max`` (same as ``host`` for KVM and HVF; best possible emulation with TCG)
79 Note that the default is ``cortex-a15``, so for an AArch64 guest you must
83 enable all the CPU features for a given ``virt`` machine. Where a CPU
88 For example, MTE support must be enabled with ``-machine virt,mte=on``,
92 See the machine-specific options below, or check them for a given machine
100 with support for this; see below.
121   address space above 32 bits. The default is ``on`` for machine types
131   Set ``on``/``off`` to enable/disable the compact layout for high memory regions.
132   The default is ``on`` for machine types later than ``virt-7.2``.
135   Set ``on``/``off`` to enable/disable the high memory region for GICv3 or
140   Set ``on``/``off`` to enable/disable the high memory region for PCI ECAM.
141   The default is ``on`` for machine types later than ``virt-3.0``.
144   Set ``on``/``off`` to enable/disable the high memory region for PCI MMIO.
148   Set the high memory region size for PCI MMIO. Must be a power of 2 and
170   for machine types later than ``virt-2.7``.
173   Set the IOMMU type to create for the guest. Valid values are:
183   for default root bus.
195   "/secure-chosen") to use for features like the random number
203   A deprecated synonym for dtb-randomness.
216 The 'defconfig' for Linux arm and arm64 kernels should include the
217 right device drivers for virtio and the PCI controller; however some older
218 kernel versions, especially for 32-bit Arm, did not have everything
232 Hardware configuration information for bare-metal programming
248 QEMU supports two types of guest image boot for ``virt``, and
249 the way for the guest code to locate the dtb binary differs:
251 - For guests using the Linux kernel boot protocol (this means any
253   of the DTB is passed in a register (``r2`` for 32-bit guests,
254   or ``x0`` for 64-bit guests)
256 - For guests booting as "bare-metal" (any other kind of boot),