github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-06-03 04:39:50 +00:00
Code Issues Projects Releases Wiki Activity

doc: Update Config Overview

Browse Source 
- Regarding post-launched VMs, update the messaging about static vs. dynamic. Dynamic is more about creating a VM at runtime per PR 7802, not changing the configuration of an existing VM at runtime.

Signed-off-by: Reyes, Amy <amy.reyes@intel.com>
This commit is contained in:
Reyes, Amy 2022-06-23 09:50:16 -07:00 committed by David Kinder
parent 5a2d4ac6c1
commit bcb82c0c4d
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/getting-started/overview_dev.rst
View File

@ -101,20 +101,21 @@ ACRN offers three types of VMs:
* **Post-launched User VMs**: These VMs typically share hardware resources via * **Post-launched User VMs**: These VMs typically share hardware resources via
the Service VM and Device Model. They can also access hardware devices the Service VM and Device Model. They can also access hardware devices
directly if they've been configured as passthrough devices. Unlike directly if they've been configured as passthrough devices. The configuration
pre-launched VMs, you can change the configuration at runtime. They are of a post-launched VM can be static (defined at build time) or dynamic
well-suited for non-safety applications, including human machine interface (defined at runtime without rebuilding ACRN). They are well-suited for
(HMI), artificial intelligence (AI), computer vision, real-time, and others. non-safety applications, including human machine interface (HMI), artificial
intelligence (AI), computer vision, real-time, and others.
The names "pre-launched" and "post-launched" refer to the boot order of these The names "pre-launched" and "post-launched" refer to the boot order of these
VMs. The ACRN hypervisor launches the pre-launched VMs first, then launches the VMs. The ACRN hypervisor launches the pre-launched VMs first, then launches the
Service VM. The Service VM launches the post-launched VMs. Service VM. The Service VM launches the post-launched VMs.
Due to the static configuration of pre-launched VMs, they are recommended only Pre-launched VMs are recommended only if you need complete isolation from the
if you need complete isolation from the rest of the system. Most use cases can rest of the system. Most use cases can meet their requirements without
meet their requirements without pre-launched VMs. Even if your application has pre-launched VMs. Even if your application has stringent real-time requirements,
stringent real-time requirements, start by testing the application on a start by testing the application on a post-launched VM before considering a
post-launched VM before considering a pre-launched VM. pre-launched VM.
Scenario Types Scenario Types
--------------- ---------------