Current supported VM types are: - ``SERVICE_VM`` Service VM - ``PRE_LAUNCHED_VM`` pre-launched VM - ``POST_LAUNCHED_VM`` post-launched VM Current supported VM types are: - ``Real-time`` for time-sensitive applications (not applicable to the service VM). - ``Standard`` for general-purpose applications, such as human-machine interface (HMI). ID of the pCPU that this VM's vCPU is allowed to pin to. Check "Real-time vCPU" for each vCPU used for real-time workloads. Then configure cache usage in the Hypervisor/Advanced/Cache Allocation Technology (CAT) configuration option. There you'll see Real-time vCPUs separated from vCPUs you allocate to other tasks. See :ref:`rdt_configuration` for more details. List of pCPU affinities. Specify the enclave page cache (EPC) section base for Intel Software Guard Extensions (SGX). Must be page aligned. Specify the enclave page cache (EPC) section size in bytes for Intel Software Guard Extensions (SGX). Must be page aligned. Specify the starting address for non-contiguous allocation. Specify the physical memory size for non-contiguous allocation in megabytes. The size is a subset of the VM's total memory size specified on the Basic tab. Specify the physical memory size allocated to this VM in megabytes. Integer value is not below zero. Specify Physical memory information for Prelaunched VM Select the kernel image type so that the hypervisor can load it correctly. Specify the tag for the kernel image that is used as a multiboot module. The tag's spelling must exactly match the module tag in the GRUB multiboot cmdline. Specify the tag for the RAMdisk image that is used as a multiboot module. The tag's spelling must exactly match the module tag in the GRUB multiboot cmdline. Specify the command-line parameters that will be used to boot the kernel for this VM. See `Linux documentation <https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html>`__ for a list of parameters. The loading address in host memory for the VM kernel. The entry address in host memory for the VM kernel. A string with either ``KERNEL_BZIMAGE`` or ``KERNEL_RAWIMAGE``. A string with either ``None``, ``COM Port 1``, ``COM Port 2``, ``COM Port 3``, or ``PCI``. A string with value: ``legacy`` or ``pci``. Specify the VM name of one end point for this vUART connection. Specify the COM base for each legacy virtual UART. Specify the virtual Bus:Device.Function (BDF) for each PCI virtual UART. Virtual BDF is automatically assigned when the configuration is saved and can be changed if needed. Specify the vUART name. Select the communication virtual UART (vUART) type. Enable passthrough of the trusted platform module (TPM2) device to this VM. Enable passthrough of the Primary-to-Sideband (P2SB) bridge register access BAR to this VM. Specify the hidden device vBDF Select the PCI devices you want to assign to this virtual machine. Select the USB physical bus and port number that will be emulated by the ACRN Device Model for this VM. USB 3.0, 2.0, and 1.0 are supported. A string with value: ``Kernel based (Virtual Host)`` or ``User space based (VBSU)``. Specify the virtio framework for specific virtio network device implemented in the Service VM. Specify the network interface name that will appear in the Service VM. Use the `ip a` command in the Service VM to display the network interface names. A string of letters, digits, ``_``, or ``-``. A string with value: ``Virtio console`` or ``Virtio serial port`` A string with value: ``pty``, ``stdio``, or ``file``. A string with value: ``Window`` and ``Full screen``. Values of display window resolutions. Monitor id specifies which physical monitor the virtual display locates in full screen mode. Windows resolution specifies the virtual window size of user vm. The abscissa (x-axis coordinate) of the left top point of the virtual window. The ordinate (x-axis coordinate) of the left top point of the virtual window. Display type provide virtual display for user vm with either full screen mode or virtual window mode. Specify device type in guest, ether HVC console when user config it as virtio console or /dev/vportXpY device file when user config it as virtio serial port, which can be read and written from the user space. Specify backend device type in service VM. The output file path for the file backend type. The sock file path for the sock server or client backend type. The device path for the tty backend type. Specifying backend device in service vm with device description. Specifying unique identifier to distinguish same devices in guest. A string with letters, digits, ``_``, or ``-``. A string with either ``Non-Windows OS`` or ``Windows OS``.