diff --git a/misc/config_tools/configurator/README.md b/misc/config_tools/configurator/README.md index fcdc20618..0ef4bf8bd 100644 --- a/misc/config_tools/configurator/README.md +++ b/misc/config_tools/configurator/README.md @@ -19,20 +19,37 @@ to install system dependencies **(including yarn)**. #### Linux -In Linux, +In Linux, make sure your already install `git`, `python3`(version>=3.6) and `python3-venv` library, + +```bash +$ sudo apt install git python3 python3-venv +# check python3 version +$ python3 --version +Python 3.8.10 +``` #### Windows -In Windows, [chocolatey](https://chocolatey.org/) is a Windows package manager, +[Chocolatey](https://chocolatey.org/) is a package manager tool for windows, you can use `choco install xsltproc` to install `xsltproc` package, which provide `xmllint` command. +Make sure your system have python which version>3.6, +you can check it by following command line: + +```bash +$ python --version +Python 3.8.10 +``` + +If your system doesn't have git and python, you can install it by +`choco install git python3`. + ### 2. Clone Project And Install Project Dependencies. #### Linux ```bash -sudo apt install git git clone https://github.com/projectacrn/acrn-hypervisor cd acrn-hypervisor/misc/config_tools python3 -m pip install -r requirements.txt @@ -43,10 +60,8 @@ yarn #### Windows -Similar to Linux. - -In the Windows environment maybe you need to install git and python3 via chocolatey or manually, -and replace the command line `python3` with `py -3`. +Similar to Linux, in the Windows environment, +you need replace the command line `python3` with `python`. ### 3. How To Build @@ -65,7 +80,7 @@ Run following command in the 'acrn-hypervisor' directory. ```shell cd misc/config_tools python scenario_config/schema_slicer.py -python scenario_config/xs2js.py +python scenario_config/jsnoschema/convert.py xmllint --xinclude schema/datachecks.xsd > schema/allchecks.xsd python -m build @@ -88,6 +103,6 @@ acrn-configurator #### Windows -You can find msi(Windows)/dmg(macOS) folder under the -`misc/config_tools/configurator/src-tauri/target/release/bundle` +You can find installer under the +`misc/config_tools/configurator/src-tauri/target/release/bundle/msi` directory, the installer in the folder. diff --git a/misc/config_tools/configurator/index.html b/misc/config_tools/configurator/index.html index 01767a158..8d14a14aa 100644 --- a/misc/config_tools/configurator/index.html +++ b/misc/config_tools/configurator/index.html @@ -9,10 +9,13 @@
Name of the VM that uses this shared memory region.
" + "description": "\n Name of the VM that uses this shared memory region.\n
\nVirtual BDF (Bus Device Function) is automatically assigned and can be changed if needed. Set in Hex.
" + "description": "\n Virtual BDF (Bus Device Function) is automatically assigned and can be changed if needed. Set in Hex.\n
\nSelect all VMs that use the shared memory region.
" + "description": "\n Select all VMs that use the shared memory region.\n
\nName of the shared memory region.
" + "title": "Region Name", + "description": "\n Name of the shared memory region.\n
\nWhether the shared memory region is emulated by the hypervisor or Device Model.
" + "description": "\n Whether the shared memory region is emulated by the hypervisor or Device Model.\n
\nSelect the size of the shared memory region\nin megabytes. The value should be a power of 2\nand no more than 512.
" + "title": "Region Size (MB)", + "description": "\n Select the size of the shared memory region\nin megabytes. The value should be a power of 2\nand no more than 512.\n
\nSelect all VMs that use the shared memory region.
" + "description": "\n Select all VMs that use the shared memory region.\n
\nCreate a memory region for VMs to share: specify its name, size, and associated VMs.
" + "description": "\n Create a memory region for VMs to share: specify its name, size, and associated VMs.\n
\nEnable Intel Resource Director Technology (RDT). If\nthe board hardware does not support\nRDT, setting this option to y is ignored.
" + "description": "\n Enable Intel Resource Director Technology (RDT). If\nthe board hardware does not support\nRDT, setting this option to\n \n y\n \n is ignored.\n
\nEnable Code and Data Prioritization (CDP). CDP provides control over code and data placement in cache to improve an application's real-time performance.
" + "description": "\n Enable Code and Data Prioritization (CDP). CDP provides control over code and data placement in cache to improve an application's real-time performance.\n
\nEnable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.
" + "description": "\n Enable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.\n
\nEnable Software SRAM. This feature reserves memory buffers as always-cached memory to improve an application's real-time performance.
" + "description": "\n Enable Software SRAM. This feature reserves memory buffers as always-cached memory to improve an application's real-time performance.\n
\nID of the pCPU that this VM's vCPU is allowed to pin to.
", + "description": "\n ID of the pCPU that this VM's vCPU is allowed to pin to.\n
\nWhether this vCPU is used for real-time-critical workloads.
" + "description": "\n Whether this vCPU is used for real-time-critical workloads.\n
\nA pCPU that this VM's vCPU is allowed to pin to.
" + "description": "\n A pCPU that this VM's vCPU is allowed to pin to.\n
\nBy default (virtual_cat_support is not specified):\nvcpu_clos is per-CPU and it configures each CPU in VMs to a desired CLOS ID in the VM section of the\nscenario file. Follow RDT Detection and Resource Capabilities to identify the maximum supported CLOS ID that can be used.
\n\n\nIf virtual_cat_support is specified:\nvcpu_clos is not per-CPU anymore, just a list of physical CLOSIDs (minimum 2) that are assigned to VMs\nfor vCAT use. Each vcpu_clos will be mapped to a virtual CLOSID, the first vcpu_clos is mapped to virtual\nCLOSID 0 and the second is mapped to virtual CLOSID 1, etc.
" + "description": "\n By default (\n \n virtual_cat_support\n \n is not specified):\nvcpu_clos is per-CPU and it configures each CPU in VMs to a desired CLOS ID in the\n \n VM\n \n section of the\nscenario file. Follow\n \n RDT Detection and Resource Capabilities\n \n to identify the maximum supported CLOS ID that can be used.\n
\n\n If\n \n virtual_cat_support\n \n is specified:\nvcpu_clos is not per-CPU anymore, just a list of physical CLOSIDs (minimum 2) that are assigned to VMs\nfor vCAT use. Each vcpu_clos will be mapped to a virtual CLOSID, the first vcpu_clos is mapped to virtual\nCLOSID 0 and the second is mapped to virtual CLOSID 1, etc.\n
\nSpecify the enclave page cache (EPC) section base for Intel Software Guard Extensions (SGX). Must be page aligned.
" + "description": "\n Specify the enclave page cache (EPC) section base for Intel Software Guard Extensions (SGX). Must be page aligned.\n
\nSpecify the enclave page cache (EPC) section size in bytes for Intel Software Guard Extensions (SGX). Must be page aligned.
" + "description": "\n Specify the enclave page cache (EPC) section size in bytes for Intel Software Guard Extensions (SGX). Must be page aligned.\n
\nSpecify the starting address for non-contiguous allocation.
" + "description": "\n Specify the starting address for non-contiguous allocation.\n
\nSpecify the physical memory size for non-contiguous allocation in megabytes.\nThe size is a subset of the VM's total memory size specified on the Basic tab.
" + "description": "\n Specify the physical memory size for non-contiguous allocation in megabytes.\nThe size is a subset of the VM's total memory size specified on the Basic tab.\n
\nSpecify the physical memory size allocated to this VM in megabytes.
" + "description": "\n Specify the physical memory size allocated to this VM in megabytes.\n
\nSpecify Physical memory information for Prelaunched VM
" + "description": "\n Specify Physical memory information for Prelaunched VM\n
\nSelect the kernel image type so that the hypervisor can load it correctly.
" + "description": "\n Select the kernel image type so that the hypervisor can load it correctly.\n
\nSpecify 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.
" + "description": "\n 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.\n
\nSpecify 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.
" + "description": "\n 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.\n
\nSpecify the command-line parameters that will be used to boot the kernel for this VM. See Linux documentation for a list of parameters.
" + "description": "\n Specify the command-line parameters that will be used to boot the kernel for this VM. See\n \n Linux documentation\n \n for a list of parameters.\n
\nThe loading address in host memory for the VM kernel.
" + "description": "\n The loading address in host memory for the VM kernel.\n
\nThe entry address in host memory for the VM kernel.
" + "description": "\n The entry address in host memory for the VM kernel.\n
\nVirtual UART port
" + "description": "\n Virtual UART port\n
\nSpecify the COM base for each legacy virtual UART.
" + "description": "\n Specify the COM base for each legacy virtual UART.\n
\nSpecify 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.
" + "title": "Virtual UART BDF", + "description": "\n 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.\n
\nSpecify the vUART name.
" + "title": "vUART name", + "description": "\n Specify the vUART name.\n
\nSelect the communication virtual UART (vUART) type.
" + "title": "vUART Type", + "description": "\n Select the communication virtual UART (vUART) type.\n
\nEnable passthrough of the trusted platform module (TPM2) device to this VM.
" + "description": "\n Enable passthrough of the trusted platform module (TPM2) device to this VM.\n
\nEnable passthrough of the Primary-to-Sideband (P2SB) bridge register access BAR to this VM.
" + "description": "\n Enable passthrough of the Primary-to-Sideband (P2SB) bridge register access BAR to this VM.\n
\nSelect the PCI devices you want to assign to this virtual machine.
", + "description": "\n Select the PCI devices you want to assign to this virtual machine.\n
\nSpecify the virtio framework for specific virtio network device implemented in the Service VM.
" + "description": "\n Specify the virtio framework for specific virtio network device implemented in the Service VM.\n
\nSpecify 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.
" + "description": "\n Specify the network interface name that will appear in the Service VM. Use the\n \n ip a\n \n command in the Service VM to display the network interface names.\n
\nSpecify device type in guest, ether HVC console when user config it as virtio console or /dev/vportXpY\ndevice file when user config it as virtio serial port, which can be read and written from the user space.
" + "description": "\n Specify device type in guest, ether HVC console when user config it as virtio console or /dev/vportXpY\ndevice file when user config it as virtio serial port, which can be read and written from the user space.\n
\nSpecify backend device type in service VM.
" + "description": "\n Specify backend device type in service VM.\n
\nThe output file path for the file backend type.
" + "description": "\n The output file path for the file backend type.\n
\nThe sock file path for the sock server or client backend type.
" + "description": "\n The sock file path for the sock server or client backend type.\n
\nThe device path for the tty backend type.
" + "description": "\n The device path for the tty backend type.\n
\nSpecifying backend device in service vm with device description.
" + "description": "\n Specifying backend device in service vm with device description.\n
\nSpecifying unique identifier to distinguish same devices in guest.
" + "description": "\n Specifying unique identifier to distinguish same devices in guest.\n
\nSelect the build type:
\n\n\nDebug enables the debug shell, prints, and logs.
Release optimizes the ACRN binary for deployment and turns off all debug infrastructure.
These settings can only be changed at build time.
" + "description": "\n Select the build type:\n
\n\n \n Debug\n \n enables the debug shell, prints, and logs.\n
\n\n \n Release\n \n optimizes the ACRN binary for deployment and turns off all debug infrastructure.\n
\n\n These settings can only be changed at build time.\n
\nSelect the host serial device used for hypervisor debugging.
", + "description": "\n Select the host serial device used for hypervisor debugging.\n
\nSelect the default log level for log messages stored in memory. Value can be changed at runtime. Log messages with the selected value or lower are displayed.
" + "description": "\n Select the default log level for log messages stored in memory. Value can be changed at runtime. Log messages with the selected value or lower are displayed.\n
\nSelect the default log level for the hypervisor via Intel Trace Hub log. Use the Intel Trace Hub's memory to record log messages. Value can be changed at runtime. Log messages with the selected value or lower are displayed.
" + "description": "\n Select the default log level for the hypervisor via Intel Trace Hub log. Use the Intel Trace Hub's memory to record log messages. Value can be changed at runtime. Log messages with the selected value or lower are displayed.\n
\nSelect the default log level for log messages written to the serial console. Log messages with the selected value or lower are displayed.
" + "description": "\n Select the default log level for log messages written to the serial console. Log messages with the selected value or lower are displayed.\n
\nEnable hypervisor relocation in memory. The bootloader may need to change the location of the hypervisor because of other firmware.
" + "description": "\n Enable hypervisor relocation in memory. The bootloader may need to change the location of the hypervisor because of other firmware.\n
\nSelect the scheduling algorithm for determining the priority of User VMs running on a shared virtual CPU.
" + "description": "\n Select the scheduling algorithm for determining the priority of User VMs running on a shared virtual CPU.\n
\nEnable multiboot2 protocol support (with multiboot1 downward compatibility). If multiboot1 meets your requirements, disable this feature to reduce hypervisor code size.
" + "description": "\n Enable multiboot2 protocol support (with multiboot1 downward compatibility). If multiboot1 meets your requirements, disable this feature to reduce hypervisor code size.\n
\nEnable detection of split locks. A split lock can negatively affect an application's real-time performance. If a lock is detected, an alignment check exception #AC occurs.
" + "description": "\n Enable detection of split locks. A split lock can negatively affect an application's real-time performance. If a lock is detected, an alignment check exception #AC occurs.\n
\nEnable detection of uncacheable-memory (UC) locks. A UC lock can negatively affect an application's real-time performance. If a lock is detected, a general-protection exception #GP occurs.
" + "description": "\n Enable detection of uncacheable-memory (UC) locks. A UC lock can negatively affect an application's real-time performance. If a lock is detected, a general-protection exception #GP occurs.\n
\nEnable to do fixup for TPM2 and SMBIOS for Security VM. If no Security VM, setting this option to n
" + "description": "\n Enable to do fixup for TPM2 and SMBIOS for Security VM. If no Security VM, setting this option to\n \n n\n \n
\nIf y, permanently disables all interrupts in HV root mode.
" + "description": "\n If\n \n y\n \n , permanently disables all interrupts in HV root mode.\n
\nIntel Resource Director Technology (RDT) provides cache and memory bandwidth allocation features. The features can be used to improve an application's real-time performance.
" + "description": "\n Intel Resource Director Technology (RDT) provides cache and memory bandwidth allocation features. The features can be used to improve an application's real-time performance.\n
\nEnable Microsoft Hyper-V Hypervisor Top-Level Functional Specification (TFLS) for User VMs running Windows.
" + "description": "\n Enable Microsoft Hyper-V Hypervisor Top-Level Functional Specification (TFLS) for User VMs running Windows.\n
\nSpecify if the IOMMU enforces snoop behavior of DMA operations.
" + "description": "\n Specify if the IOMMU enforces snoop behavior of DMA operations.\n
\nEnable ACPI runtime parsing to get DMAR (DMA remapping) configuration data from the APCI tables. Otherwise, use existing, static information from the associated board configuration file.
" + "description": "\n Enable ACPI runtime parsing to get DMAR (DMA remapping) configuration data from the APCI tables. Otherwise, use existing, static information from the associated board configuration file.\n
\nEnable L1 cache flush before VM entry to prevent L1 terminal fault. L1 terminal fault is a hardware vulnerability that could allow unauthorized disclosure of information residing in the L1 data cache.
" + "description": "\n Enable L1 cache flush before VM entry to prevent L1 terminal fault. L1 terminal fault is a hardware vulnerability that could allow unauthorized disclosure of information residing in the L1 data cache.\n
\nEnable the software workaround for Machine Check Error on Page Size Change (erratum in some processor families).
" + "description": "\n Enable the software workaround for Machine Check Error on Page Size Change (erratum in some processor families).\n
\nConfigure shared memory regions for inter-VM communication.
" + "description": "\n Configure shared memory regions for inter-VM communication.\n
\nConfigure Software SRAM. This feature reserves memory buffers as always-cached memory to improve an application's real-time performance.
" + "description": "\n Configure Software SRAM. This feature reserves memory buffers as always-cached memory to improve an application's real-time performance.\n
\nSpecify the size of the memory stack in bytes for each physical CPU. For example, if you specify 8 kilobytes, each CPU will get its own 8-kilobyte stack.
" + "description": "\n Specify the size of the memory stack in bytes for each physical CPU. For example, if you specify 8 kilobytes, each CPU will get its own 8-kilobyte stack.\n
\nThe 2MB-aligned starting physical address of the RAM region used by the hypervisor.
" + "description": "\n The 2MB-aligned starting physical address of the RAM region used by the hypervisor.\n
\nMaximum number of User VMs allowed.
" + "description": "\n Maximum number of User VMs allowed.\n
\nMaximum number of IOAPICs.
" + "description": "\n Maximum number of IOAPICs.\n
\nSpecify the maximum number of PCI devices. This impacts the amount of memory used to maintain information about these PCI devices. The default value is calculated from the board configuration file. If you have PCI devices that were not detected by the Board Inspector, you may need to change this maximum value.
" + "description": "\n Specify the maximum number of PCI devices. This impacts the amount of memory used to maintain information about these PCI devices. The default value is calculated from the board configuration file. If you have PCI devices that were not detected by the Board Inspector, you may need to change this maximum value.\n
\nMaximum number of interrupt lines per IOAPIC.
" + "description": "\n Maximum number of interrupt lines per IOAPIC.\n
\nSpecify the maximum number of interrupt request (IRQ) entries from all passthrough devices.
" + "description": "\n Specify the maximum number of interrupt request (IRQ) entries from all passthrough devices.\n
\nSpecify the maximum number of Message Signaled Interrupt MSI-X tables per device. The default value is calculated from the board configuration file.
" + "description": "\n Specify the maximum number of Message Signaled Interrupt MSI-X tables per device. The default value is calculated from the board configuration file.\n
\nSpecify the maximum number of emulated MMIO regions for device virtualization. The default value is calculated from the board configuration file.
" + "description": "\n Specify the maximum number of emulated MMIO regions for device virtualization. The default value is calculated from the board configuration file.\n
\nSegment, Bus, Device, and function of the GPU.
" + "description": "\n Segment, Bus, Device, and function of the GPU.\n
\nConfigure the debug facilities.
" + "description": "\n Configure the debug facilities.\n
\nEnable hypervisor features.
" + "description": "\n Enable hypervisor features.\n
\nConfigure memory used by the hypervisor.
" + "description": "\n Configure memory used by the hypervisor.\n
\nConfigure the capacities of the hypervisor.
" + "description": "\n Configure the capacities of the hypervisor.\n
\nMiscellaneous options for workarounds.
" + "description": "\n Miscellaneous options for workarounds.\n
\nSpecify the vUART connection settings.\nRefer to Enable vUART Configurations for detailed vUART settings.
" + "description": "\n Specify the vUART connection settings.\nRefer to\n \n Enable vUART Configurations\n \n for detailed vUART settings.\n
\nSpecify the cache setting.
" + "description": "\n Specify the cache setting.\n
\nSpecify the load_order.
" + "description": "\n Specify the VM load order.\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nEnable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable nested virtualization for KVM.
" + "description": "\n Enable nested virtualization for KVM.\n
\nEnable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.
" + "title": "VM Virtual Cache Allocation Tech", + "description": "\n Enable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.\n
\nSpecify secure world support for trusty OS.
" + "description": "\n Specify secure world support for trusty OS.\n
\nSpecify MTRR capability to hide for VM.
" + "description": "\n Specify MTRR capability to hide for VM.\n
\nSpecify TPM2 FIXUP for VM.
" + "description": "\n Specify TPM2 FIXUP for VM.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nSpecify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.
" + "description": "\n Specify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nSpecify the VM vCPU priority for scheduling.
" + "description": "\n Specify the VM vCPU priority for scheduling.\n
\nSpecify the companion VM id of this VM.
" + "description": "\n Specify the companion VM id of this VM.\n
\nGeneral information for host kernel, boot\nargument and memory.
" + "description": "\n General information for host kernel, boot\nargument and memory.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nMMIO resources to passthrough.
" + "description": "\n MMIO resources to passthrough.\n
\nSpecify the pre-launched VM owned IOAPIC pins and the corresponding mapping between physical GSI and virtual GSI.
" + "description": "\n Specify the pre-launched VM owned IOAPIC pins and the corresponding mapping between physical GSI and virtual GSI.\n
\nEnable virtualization of PCIe Precision Time Measurement (PTM) mechanism for devices with PTM capability and for real-time application. The hypervisor provides PCIe root port emulation instead of host bridge emulation for the VM. PTM coordinates timing between the device and root port with the device's local timebases without relying on software.
" + "description": "\n Enable virtualization of PCIe Precision Time Measurement (PTM) mechanism for devices with PTM capability and for real-time application. The hypervisor provides PCIe root port emulation instead of host bridge emulation for the VM. PTM coordinates timing between the device and root port with the device's local timebases without relying on software.\n
\nSelect the OS type for this VM. This is required to run Windows in a User VM. See Device Model Parameters for how to include this in the Device Model arguments.
" + "description": "\n Select the OS type for this VM. This is required to run Windows in a User VM. See\n \n Device Model Parameters\n \n for how to include this in the Device Model arguments.\n
\nUse virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.
" + "description": "\n Use virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.\n
\nEnable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.
" + "description": "\n Enable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.\n
\nSelect 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.
" + "description": "\n 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.\n
\nVirtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see Virtio-Console.
" + "description": "\n Virtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see\n \n Virtio-Console\n \n .\n
\nThe virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be: tap device /dev/net/tun,\nMacVTap device /dev/tapx, or vhost device /dev/vhost-net
" + "description": "\n The virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be:\n \n tap\n \n device /dev/net/tun,\n \n MacVTap\n \n device /dev/tapx, or\n \n vhost\n \n device /dev/vhost-net\n
\nThe virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.
" + "description": "\n The virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.\n
\nThe virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.
" + "description": "\n The virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.\n
\nThis feature enables you to view the VM's GPU output in the Service VM.
\n\n This feature enables you to view the VM's GPU output in the Service VM.\n
\nEnable virt-IO devices in post-launched VMs.
" + "description": "\n Enable virt-IO devices in post-launched VMs.\n
\nThe hypervisor configuration defines a working scenario and target\nboard by configuring the hypervisor image features and capabilities such as\nsetting up the log and the serial port.
" + "description": "\n The hypervisor configuration defines a working scenario and target\nboard by configuring the hypervisor image features and capabilities such as\nsetting up the log and the serial port.\n
\nVM configuration includes scenario-based VM configuration\ninformation that is used to describe the characteristics and attributes for\nall VMs in a user scenario. It also includes launch script-based VM\nconfiguration information, where parameters are passed to the device model\nto launch post-launched User VMs.
" + "description": "\n VM configuration includes\n \n scenario-based\n \n VM configuration\ninformation that is used to describe the characteristics and attributes for\nall VMs in a user scenario. It also includes\n \n launch script-based\n \n VM\nconfiguration information, where parameters are passed to the device model\nto launch post-launched User VMs.\n
\nSpecify the load_order.
" + "description": "\n Specify the VM load order.\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nEnable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.
" + "title": "VM Virtual Cache Allocation Tech", + "description": "\n Enable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.\n
\nSpecify secure world support for trusty OS.
" + "description": "\n Specify secure world support for trusty OS.\n
\nSpecify MTRR capability to hide for VM.
" + "description": "\n Specify MTRR capability to hide for VM.\n
\nSpecify TPM2 FIXUP for VM.
" + "description": "\n Specify TPM2 FIXUP for VM.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nSpecify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.
" + "description": "\n Specify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nSpecify the VM vCPU priority for scheduling.
" + "description": "\n Specify the VM vCPU priority for scheduling.\n
\nSpecify the companion VM id of this VM.
" + "description": "\n Specify the companion VM id of this VM.\n
\nGeneral information for host kernel, boot\nargument and memory.
" + "description": "\n General information for host kernel, boot\nargument and memory.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nMMIO resources to passthrough.
" + "description": "\n MMIO resources to passthrough.\n
\nSpecify the pre-launched VM owned IOAPIC pins and the corresponding mapping between physical GSI and virtual GSI.
" + "description": "\n Specify the pre-launched VM owned IOAPIC pins and the corresponding mapping between physical GSI and virtual GSI.\n
\nEnable virtualization of PCIe Precision Time Measurement (PTM) mechanism for devices with PTM capability and for real-time application. The hypervisor provides PCIe root port emulation instead of host bridge emulation for the VM. PTM coordinates timing between the device and root port with the device's local timebases without relying on software.
" + "description": "\n Enable virtualization of PCIe Precision Time Measurement (PTM) mechanism for devices with PTM capability and for real-time application. The hypervisor provides PCIe root port emulation instead of host bridge emulation for the VM. PTM coordinates timing between the device and root port with the device's local timebases without relying on software.\n
\nSpecify the load_order.
" + "description": "\n Specify the VM load order.\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nEnable nested virtualization for KVM.
" + "description": "\n Enable nested virtualization for KVM.\n
\nSpecify secure world support for trusty OS.
" + "description": "\n Specify secure world support for trusty OS.\n
\nSpecify MTRR capability to hide for VM.
" + "description": "\n Specify MTRR capability to hide for VM.\n
\nSpecify TPM2 FIXUP for VM.
" + "description": "\n Specify TPM2 FIXUP for VM.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nSpecify the VM vCPU priority for scheduling.
" + "description": "\n Specify the VM vCPU priority for scheduling.\n
\nSpecify the companion VM id of this VM.
" + "description": "\n Specify the companion VM id of this VM.\n
\nGeneral information for host kernel, boot\nargument and memory.
" + "description": "\n General information for host kernel, boot\nargument and memory.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nSpecify the physical memory size allocated to this VM in megabytes.
" + "description": "\n Specify the physical memory size allocated to this VM in megabytes.\n
\nSpecify the load_order.
" + "description": "\n Specify the VM load order.\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nEnable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.
" + "title": "VM Virtual Cache Allocation Tech", + "description": "\n Enable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.\n
\nSpecify secure world support for trusty OS.
" + "description": "\n Specify secure world support for trusty OS.\n
\nSpecify MTRR capability to hide for VM.
" + "description": "\n Specify MTRR capability to hide for VM.\n
\nSpecify TPM2 FIXUP for VM.
" + "description": "\n Specify TPM2 FIXUP for VM.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nSpecify the VM vCPU priority for scheduling.
" + "description": "\n Specify the VM vCPU priority for scheduling.\n
\nSpecify the companion VM id of this VM.
" + "description": "\n Specify the companion VM id of this VM.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nEnable virtualization of PCIe Precision Time Measurement (PTM) mechanism for devices with PTM capability and for real-time application. The hypervisor provides PCIe root port emulation instead of host bridge emulation for the VM. PTM coordinates timing between the device and root port with the device's local timebases without relying on software.
" + "description": "\n Enable virtualization of PCIe Precision Time Measurement (PTM) mechanism for devices with PTM capability and for real-time application. The hypervisor provides PCIe root port emulation instead of host bridge emulation for the VM. PTM coordinates timing between the device and root port with the device's local timebases without relying on software.\n
\nSelect the OS type for this VM. This is required to run Windows in a User VM. See Device Model Parameters for how to include this in the Device Model arguments.
" + "description": "\n Select the OS type for this VM. This is required to run Windows in a User VM. See\n \n Device Model Parameters\n \n for how to include this in the Device Model arguments.\n
\nUse virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.
" + "description": "\n Use virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.\n
\nEnable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.
" + "description": "\n Enable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.\n
\nSelect 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.
" + "description": "\n 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.\n
\nVirtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see Virtio-Console.
" + "description": "\n Virtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see\n \n Virtio-Console\n \n .\n
\nThe virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be: tap device /dev/net/tun,\nMacVTap device /dev/tapx, or vhost device /dev/vhost-net
" + "description": "\n The virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be:\n \n tap\n \n device /dev/net/tun,\n \n MacVTap\n \n device /dev/tapx, or\n \n vhost\n \n device /dev/vhost-net\n
\nThe virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.
" + "description": "\n The virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.\n
\nThe virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.
" + "description": "\n The virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.\n
\nThis feature enables you to view the VM's GPU output in the Service VM.
\n\n This feature enables you to view the VM's GPU output in the Service VM.\n
\nEnable virt-IO devices in post-launched VMs.
" + "description": "\n Enable virt-IO devices in post-launched VMs.\n
\nSpecify the physical memory size allocated to this VM in megabytes.
" + "description": "\n Specify the physical memory size allocated to this VM in megabytes.\n
\nSelect the kernel image type so that the hypervisor can load it correctly.
" + "description": "\n Select the kernel image type so that the hypervisor can load it correctly.\n
\nSpecify 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.
" + "description": "\n 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.\n
\nSpecify 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.
" + "description": "\n 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.\n
\nSpecify the command-line parameters that will be used to boot the kernel for this VM. See Linux documentation for a list of parameters.
" + "description": "\n Specify the command-line parameters that will be used to boot the kernel for this VM. See\n \n Linux documentation\n \n for a list of parameters.\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nGeneral information for host kernel, boot\nargument and memory.
" + "description": "\n General information for host kernel, boot\nargument and memory.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nMMIO resources to passthrough.
" + "description": "\n MMIO resources to passthrough.\n
\nSelect the OS type for this VM. This is required to run Windows in a User VM. See Device Model Parameters for how to include this in the Device Model arguments.
" + "description": "\n Select the OS type for this VM. This is required to run Windows in a User VM. See\n \n Device Model Parameters\n \n for how to include this in the Device Model arguments.\n
\nUse virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.
" + "description": "\n Use virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.\n
\nEnable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.
" + "description": "\n Enable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.\n
\nSelect 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.
" + "description": "\n 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.\n
\nVirtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see Virtio-Console.
" + "description": "\n Virtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see\n \n Virtio-Console\n \n .\n
\nThe virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be: tap device /dev/net/tun,\nMacVTap device /dev/tapx, or vhost device /dev/vhost-net
" + "description": "\n The virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be:\n \n tap\n \n device /dev/net/tun,\n \n MacVTap\n \n device /dev/tapx, or\n \n vhost\n \n device /dev/vhost-net\n
\nThe virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.
" + "description": "\n The virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.\n
\nThe virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.
" + "description": "\n The virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.\n
\nThis feature enables you to view the VM's GPU output in the Service VM.
\n\n This feature enables you to view the VM's GPU output in the Service VM.\n
\nEnable virt-IO devices in post-launched VMs.
" + "description": "\n Enable virt-IO devices in post-launched VMs.\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nGeneral information for host kernel, boot\nargument and memory.
" + "description": "\n General information for host kernel, boot\nargument and memory.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nMMIO resources to passthrough.
" + "description": "\n MMIO resources to passthrough.\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nGeneral information for host kernel, boot\nargument and memory.
" + "description": "\n General information for host kernel, boot\nargument and memory.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nSelect the VM type. A standard VM (STANDARD_VM) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (RTVM) offers special features for time-sensitive applications.
" + "description": "\n Select the VM type. A standard VM (\n \n STANDARD_VM\n \n ) is for general-purpose applications, such as human-machine interface (HMI). A real-time VM (\n \n RTVM\n \n ) offers special features for time-sensitive applications.\n
\nSpecify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.
" + "description": "\n Specify the name used to identify this VM. The VM name will be shown in the hypervisor console vm_list command.\n
\nSelect a subset of physical CPUs that this VM can use. More than one can be selected.
" + "description": "\n Select a subset of physical CPUs that this VM can use. More than one can be selected.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nSelect the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example, console=ttyS0 for COM port 1).
" + "description": "\n Select the console virtual UART (vUART) type. Add the console settings to the kernel command line by typing them in the \"Linux kernel command-line parameters\" text box (for example,\n \n console=ttyS0\n \n for COM port 1).\n
\nSelect the OS type for this VM. This is required to run Windows in a User VM. See Device Model Parameters for how to include this in the Device Model arguments.
" + "description": "\n Select the OS type for this VM. This is required to run Windows in a User VM. See\n \n Device Model Parameters\n \n for how to include this in the Device Model arguments.\n
\nUse virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.
" + "description": "\n Use virtual bootloader OVMF (Open Virtual Machine Firmware) to boot this VM.\n
\nEnable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.
" + "description": "\n Enable the ACRN Device Model to emulate COM1 as a User VM stdio I/O. Hypervisor global emulation will take priority over this VM setting.\n
\nSelect 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.
" + "description": "\n 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.\n
\nVirtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see Virtio-Console.
" + "description": "\n Virtio console device for data input and output.\nThe virtio console BE driver copies data from the frontend's transmitting virtqueue when it receives a kick on virtqueue (implemented as a vmexit).\nThe BE driver then writes the data to backend, and can be implemented as PTY, TTY, STDIO, and regular file.\nFor details, see\n \n Virtio-Console\n \n .\n
\nThe virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be: tap device /dev/net/tun,\nMacVTap device /dev/tapx, or vhost device /dev/vhost-net
" + "description": "\n The virtio network device emulates a virtual network interface card (NIC) for the VM. The frontend\nis the virtio network driver, simulating the virtual NIC. The backend could be:\n \n tap\n \n device /dev/net/tun,\n \n MacVTap\n \n device /dev/tapx, or\n \n vhost\n \n device /dev/vhost-net\n
\nThe virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.
" + "description": "\n The virtio input device creates a virtual human interface device such as a keyboard,\nmouse, and tablet. It sends Linux input layer events over virtio.\n
\nThe virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.
" + "description": "\n The virtio-blk device presents a block device to the VM. Each virtio-blk device appears as a disk inside the VM.\n
\nThis feature enables you to view the VM's GPU output in the Service VM.
\n\n This feature enables you to view the VM's GPU output in the Service VM.\n
\nEnable virt-IO devices in post-launched VMs.
" + "description": "\n Enable virt-IO devices in post-launched VMs.\n
\nConfigure shared memory regions for inter-VM communication.
" + "description": "\n Configure shared memory regions for inter-VM communication.\n
\nConfigure the debug facilities.
" + "description": "\n Configure the debug facilities.\n
\nEnable hypervisor features.
" + "description": "\n Enable hypervisor features.\n
\nSpecify the vUART connection settings.\nRefer to Enable vUART Configurations for detailed vUART settings.
" + "description": "\n Specify the vUART connection settings.\nRefer to\n \n Enable vUART Configurations\n \n for detailed vUART settings.\n
\nSpecify the cache setting.
" + "description": "\n Specify the cache setting.\n
\nSpecify Physical memory information for Prelaunched VM
" + "description": "\n Specify Physical memory information for Prelaunched VM\n
\nEnable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable nested virtualization for KVM.
" + "description": "\n Enable nested virtualization for KVM.\n
\nEnable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.
" + "title": "VM Virtual Cache Allocation Tech", + "description": "\n Enable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nSpecify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.
" + "description": "\n Specify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nEnable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.
" + "title": "VM Virtual Cache Allocation Tech", + "description": "\n Enable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nSpecify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.
" + "description": "\n Specify the Intel Software Guard Extensions (SGX) enclave page cache (EPC) section settings.\n
\nSpecify memory information for User VMs.
" + "description": "\n Specify memory information for User VMs.\n
\nEnable nested virtualization for KVM.
" + "description": "\n Enable nested virtualization for KVM.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nEnable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable LAPIC passthrough for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.
" + "description": "\n Enable polling mode for I/O completion for this VM. This feature is required for VMs with stringent real-time performance needs.\n
\nEnable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.
" + "title": "VM Virtual Cache Allocation Tech", + "description": "\n Enable virtualization of the Cache Allocation Technology (CAT) feature in RDT. CAT enables you to allocate cache to VMs, providing isolation to avoid performance interference from other VMs.\n
\nClass of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.
" + "description": "\n Class of Service for Cache Allocation Technology.\nRefer SDM 17.19.2 for details, and use with caution.\n
\nEnable hypervisor relocation in memory. The bootloader may need to change the location of the hypervisor because of other firmware.
" + "description": "\n Enable hypervisor relocation in memory. The bootloader may need to change the location of the hypervisor because of other firmware.\n
\nSelect the scheduling algorithm for determining the priority of User VMs running on a shared virtual CPU.
" + "description": "\n Select the scheduling algorithm for determining the priority of User VMs running on a shared virtual CPU.\n
\nEnable multiboot2 protocol support (with multiboot1 downward compatibility). If multiboot1 meets your requirements, disable this feature to reduce hypervisor code size.
" + "description": "\n Enable multiboot2 protocol support (with multiboot1 downward compatibility). If multiboot1 meets your requirements, disable this feature to reduce hypervisor code size.\n
\nEnable detection of split locks. A split lock can negatively affect an application's real-time performance. If a lock is detected, an alignment check exception #AC occurs.
" + "description": "\n Enable detection of split locks. A split lock can negatively affect an application's real-time performance. If a lock is detected, an alignment check exception #AC occurs.\n
\nEnable detection of uncacheable-memory (UC) locks. A UC lock can negatively affect an application's real-time performance. If a lock is detected, a general-protection exception #GP occurs.
" + "description": "\n Enable detection of uncacheable-memory (UC) locks. A UC lock can negatively affect an application's real-time performance. If a lock is detected, a general-protection exception #GP occurs.\n
\nIntel Resource Director Technology (RDT) provides cache and memory bandwidth allocation features. The features can be used to improve an application's real-time performance.
" + "description": "\n Intel Resource Director Technology (RDT) provides cache and memory bandwidth allocation features. The features can be used to improve an application's real-time performance.\n
\nEnable Microsoft Hyper-V Hypervisor Top-Level Functional Specification (TFLS) for User VMs running Windows.
" + "description": "\n Enable Microsoft Hyper-V Hypervisor Top-Level Functional Specification (TFLS) for User VMs running Windows.\n
\nEnable ACPI runtime parsing to get DMAR (DMA remapping) configuration data from the APCI tables. Otherwise, use existing, static information from the associated board configuration file.
" + "description": "\n Enable ACPI runtime parsing to get DMAR (DMA remapping) configuration data from the APCI tables. Otherwise, use existing, static information from the associated board configuration file.\n
\nEnable L1 cache flush before VM entry to prevent L1 terminal fault. L1 terminal fault is a hardware vulnerability that could allow unauthorized disclosure of information residing in the L1 data cache.
" + "description": "\n Enable L1 cache flush before VM entry to prevent L1 terminal fault. L1 terminal fault is a hardware vulnerability that could allow unauthorized disclosure of information residing in the L1 data cache.\n
\nEnable the software workaround for Machine Check Error on Page Size Change (erratum in some processor families).
" + "description": "\n Enable the software workaround for Machine Check Error on Page Size Change (erratum in some processor families).\n
\nConfigure Software SRAM. This feature reserves memory buffers as always-cached memory to improve an application's real-time performance.
" + "description": "\n Configure Software SRAM. This feature reserves memory buffers as always-cached memory to improve an application's real-time performance.\n
\nSpecify the size of the memory stack in bytes for each physical CPU. For example, if you specify 8 kilobytes, each CPU will get its own 8-kilobyte stack.
" + "description": "\n Specify the size of the memory stack in bytes for each physical CPU. For example, if you specify 8 kilobytes, each CPU will get its own 8-kilobyte stack.\n
\nSpecify the maximum number of PCI devices. This impacts the amount of memory used to maintain information about these PCI devices. The default value is calculated from the board configuration file. If you have PCI devices that were not detected by the Board Inspector, you may need to change this maximum value.
" + "description": "\n Specify the maximum number of PCI devices. This impacts the amount of memory used to maintain information about these PCI devices. The default value is calculated from the board configuration file. If you have PCI devices that were not detected by the Board Inspector, you may need to change this maximum value.\n
\nSpecify the maximum number of interrupt request (IRQ) entries from all passthrough devices.
" + "description": "\n Specify the maximum number of interrupt request (IRQ) entries from all passthrough devices.\n
\nSpecify the maximum number of Message Signaled Interrupt MSI-X tables per device. The default value is calculated from the board configuration file.
" + "description": "\n Specify the maximum number of Message Signaled Interrupt MSI-X tables per device. The default value is calculated from the board configuration file.\n
\nSpecify the maximum number of emulated MMIO regions for device virtualization. The default value is calculated from the board configuration file.
" + "description": "\n Specify the maximum number of emulated MMIO regions for device virtualization. The default value is calculated from the board configuration file.\n
\nEnable hypervisor features.
" + "description": "\n Enable hypervisor features.\n
\nConfigure memory used by the hypervisor.
" + "description": "\n Configure memory used by the hypervisor.\n
\nConfigure the capacities of the hypervisor.
" + "description": "\n Configure the capacities of the hypervisor.\n
\nSpecify the cache setting.
" + "description": "\n Specify the cache setting.\n
\n