doc: update docs and images to match scenario names
Update the docs and images referencing ``industry`` and ``logical_partition`` scenarios to ``shared`` and ``partioned``. Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
@@ -152,7 +152,7 @@ The default scheduler is **SCHED_BVT**.
|
||||
Example
|
||||
*******
|
||||
|
||||
Use the following settings to support this configuration in the industry scenario:
|
||||
Use the following settings to support this configuration in the shared scenario:
|
||||
|
||||
+---------+--------+-------+-------+
|
||||
|pCPU0 |pCPU1 |pCPU2 |pCPU3 |
|
||||
|
@@ -205,7 +205,7 @@ How to Test
|
||||
#. Refer to the :ref:`enable_s5` section to set up the S5 environment for the User VMs.
|
||||
|
||||
.. note:: RT-Linux's UUID must use ``495ae2e5-2603-4d64-af76-d4bc5a8ec0e5``. Also, the
|
||||
industry EFI image is required for launching the RT-Linux VM.
|
||||
shared EFI image is required for launching the RT-Linux VM.
|
||||
|
||||
.. note:: Use the ``systemctl status life_mngr.service`` command to ensure the service is working on the LaaG or RT-Linux:
|
||||
|
||||
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 64 KiB |
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 64 KiB |
Before Width: | Height: | Size: 65 KiB After Width: | Height: | Size: 65 KiB |
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 28 KiB |
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 47 KiB |
@@ -1,13 +1,13 @@
|
||||
.. _using_partition_mode_on_nuc:
|
||||
|
||||
Getting Started Guide for ACRN Logical Partition Mode
|
||||
#####################################################
|
||||
Getting Started Guide for ACRN Partitioned Mode
|
||||
###############################################
|
||||
|
||||
The ACRN hypervisor supports a logical partition scenario in which the User
|
||||
The ACRN hypervisor supports a partitioned scenario in which the User
|
||||
OS, running in a pre-launched VM, can bypass the ACRN
|
||||
hypervisor and directly access isolated PCI devices. The following
|
||||
guidelines provide step-by-step instructions on how to set up the ACRN
|
||||
hypervisor logical partition scenario on Intel NUC while running two
|
||||
hypervisor partitioned scenario on Intel NUC while running two
|
||||
pre-launched VMs.
|
||||
|
||||
.. contents::
|
||||
@@ -20,6 +20,10 @@ Validated Versions
|
||||
- Ubuntu version: **18.04**
|
||||
- ACRN hypervisor tag: **v2.6**
|
||||
|
||||
.. note:: After the v2.6 release, the ``logical_partition`` scenario
|
||||
was renamed to ``partitioned``, affecting the file names used in this
|
||||
guide (validated with v2.6).
|
||||
|
||||
Prerequisites
|
||||
*************
|
||||
|
||||
|
@@ -104,6 +104,6 @@ then add it to the grub menu:
|
||||
|
||||
``uart=bdf@0x101`` for port 2
|
||||
|
||||
``uart=bdf@0x101`` is preferred for the industry scenario; otherwise, it can't
|
||||
``uart=bdf@0x101`` is preferred for the shared scenario; otherwise, it can't
|
||||
input in the Hypervisor console after the Service VM boots up.
|
||||
There is no such limitation for the hybrid or hybrid_rt scenarios.
|
||||
|