doc: Update images
- Update images to align better with ACRN branding Signed-off-by: Reyes, Amy <amy.reyes@intel.com>
@ -12,8 +12,7 @@ configuration is based on the ACRN predefined **shared** scenario and consists
|
||||
of an ACRN hypervisor, Service VM, and six User VMs, but we'll launch only one
|
||||
User VM, as illustrated in this figure:
|
||||
|
||||
.. image:: ./images/gsg_scenario.png
|
||||
:scale: 80%
|
||||
.. image:: ./images/gsg_scenario-1-0.75x.png
|
||||
|
||||
Throughout this guide, you will be exposed to some of the tools, processes, and
|
||||
components of the ACRN project. Let's get started.
|
||||
@ -26,7 +25,6 @@ development computer is where you configure and build ACRN and your application.
|
||||
The target system is where you deploy and run ACRN and your application.
|
||||
|
||||
.. image:: ./images/gsg_host_target.png
|
||||
:scale: 60%
|
||||
|
||||
Before you begin, make sure your machines have the following prerequisites:
|
||||
|
||||
|
BIN
doc/getting-started/images/ACRN_terms-1-0.75x.png
Normal file
After Width: | Height: | Size: 97 KiB |
Before Width: | Height: | Size: 25 KiB |
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 16 KiB |
BIN
doc/getting-started/images/gsg_scenario-1-0.75x.png
Normal file
After Width: | Height: | Size: 54 KiB |
Before Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 1.3 KiB After Width: | Height: | Size: 3.0 KiB |
Before Width: | Height: | Size: 2.9 KiB After Width: | Height: | Size: 3.7 KiB |
Before Width: | Height: | Size: 2.1 KiB After Width: | Height: | Size: 3.4 KiB |
BIN
doc/getting-started/images/overview_flow-1-0.6x.png
Normal file
After Width: | Height: | Size: 96 KiB |
Before Width: | Height: | Size: 109 KiB |
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 18 KiB |
@ -32,7 +32,6 @@ The recommended development environment for ACRN consists of two machines:
|
||||
* **Target system** where you install and run ACRN images
|
||||
|
||||
.. image:: ./images/overview_host_target.png
|
||||
:scale: 60%
|
||||
|
||||
ACRN requires a serial output from the target system to the development computer
|
||||
for :ref:`debugging and system messaging <acrn-debug>`. If your target doesn't
|
||||
@ -49,7 +48,7 @@ General Process for Building an ACRN Hypervisor
|
||||
The general process for configuring and building an ACRN hypervisor is
|
||||
illustrated in the following figure. Additional details follow.
|
||||
|
||||
.. image:: ./images/overview_flow.png
|
||||
.. image:: ./images/overview_flow-1-0.6x.png
|
||||
|
||||
.. _overview_dev_hw_scenario:
|
||||
|
||||
@ -57,7 +56,6 @@ illustrated in the following figure. Additional details follow.
|
||||
*************************************************
|
||||
|
||||
.. |icon_light| image:: ./images/icon_light.png
|
||||
:scale: 75%
|
||||
|
||||
ACRN configuration is hardware and scenario specific. You will need to learn
|
||||
about supported ACRN hardware and scenarios, and select the right ones for your
|
||||
@ -80,8 +78,7 @@ VMs that can be run, their attributes, and the resources they have access to.
|
||||
This image shows an example of an ACRN scenario to illustrate the types of VMs
|
||||
that ACRN offers:
|
||||
|
||||
.. image:: ./images/acrn_terms.png
|
||||
:scale: 75%
|
||||
.. image:: ./images/ACRN_terms-1-0.75x.png
|
||||
|
||||
ACRN offers three types of VMs:
|
||||
|
||||
@ -147,7 +144,6 @@ later in :ref:`overview_dev_config_editor`.
|
||||
****************************************************
|
||||
|
||||
.. |icon_host| image:: ./images/icon_host.png
|
||||
:scale: 75%
|
||||
|
||||
Your development computer requires certain dependencies to configure and build
|
||||
ACRN:
|
||||
@ -163,7 +159,6 @@ ACRN:
|
||||
*********************************************************
|
||||
|
||||
.. |icon_target| image:: ./images/icon_target.png
|
||||
:scale: 75%
|
||||
|
||||
The :ref:`board_inspector_tool` ``board_inspector.py``, found in the ACRN
|
||||
hypervisor source code, enables you to generate a board configuration file on
|
||||
|
Before Width: | Height: | Size: 113 KiB |
BIN
doc/introduction/images/ACRN-V2-high-level-arch-1-0.75x.png
Normal file
After Width: | Height: | Size: 112 KiB |
Before Width: | Height: | Size: 175 KiB |
BIN
doc/introduction/images/ACRN-hybrid-rt-example-1-0.75x.png
Normal file
After Width: | Height: | Size: 97 KiB |
Before Width: | Height: | Size: 153 KiB |
BIN
doc/introduction/images/ACRN-industry-example-1-0.75x.png
Normal file
After Width: | Height: | Size: 106 KiB |
Before Width: | Height: | Size: 165 KiB |
BIN
doc/introduction/images/ACRN-partitioned-example-1-0.75x.png
Normal file
After Width: | Height: | Size: 58 KiB |
Before Width: | Height: | Size: 104 KiB |
@ -126,8 +126,7 @@ software (or mediator) in the Service VM inherits the User VM priority.
|
||||
As mentioned earlier, hardware resources used by VMs can be configured into
|
||||
two parts, as shown in this hybrid VM sample configuration:
|
||||
|
||||
.. figure:: images/ACRN-V2-high-level-arch.png
|
||||
:width: 700px
|
||||
.. figure:: images/ACRN-V2-high-level-arch-1-0.75x.png
|
||||
:align: center
|
||||
:name: V2-hl-arch
|
||||
|
||||
@ -327,8 +326,7 @@ can define your own configuration scenarios.
|
||||
device drivers to access the hardware and provides I/O mediation to the User
|
||||
VMs.
|
||||
|
||||
.. figure:: images/ACRN-industry-example.png
|
||||
:width: 700px
|
||||
.. figure:: images/ACRN-industry-example-1-0.75x.png
|
||||
:align: center
|
||||
:name: arch-shared-example
|
||||
|
||||
@ -346,15 +344,15 @@ can define your own configuration scenarios.
|
||||
|
||||
In this example, one post-launched User VM provides Human Machine Interface
|
||||
(HMI) capability, another provides Artificial Intelligence (AI) capability,
|
||||
some compute function is run the Kata Container, and the RTVM runs the soft
|
||||
some compute function is run in the Kata Container, and the RTVM runs the soft
|
||||
Programmable Logic Controller (PLC) that requires hard real-time
|
||||
characteristics.
|
||||
|
||||
- The Service VM, provides device sharing functionalities, such as disk and
|
||||
- The Service VM provides device sharing functionalities, such as disk and
|
||||
network mediation, to other virtual machines. It can also run an
|
||||
orchestration agent allowing User VM orchestration with tools such as
|
||||
Kubernetes.
|
||||
- The HMI Application OS can be Windows* or Linux*. Windows is dominant in
|
||||
- The HMI Application OS can be Windows or Linux. Windows is dominant in
|
||||
Industrial HMI environments.
|
||||
- ACRN can support a soft real-time OS such as preempt-rt Linux for soft-PLC
|
||||
control, or a hard real-time OS that offers less jitter.
|
||||
@ -367,8 +365,7 @@ can define your own configuration scenarios.
|
||||
since all partitioned VMs run native device drivers and directly access their
|
||||
configured resources.
|
||||
|
||||
.. figure:: images/ACRN-partitioned-example.png
|
||||
:width: 700px
|
||||
.. figure:: images/ACRN-partitioned-example-1-0.75x.png
|
||||
:align: center
|
||||
:name: arch-partitioned-example
|
||||
|
||||
@ -386,8 +383,7 @@ can define your own configuration scenarios.
|
||||
VMs are started by the Device Model in the Service VM and share the remaining
|
||||
resources.
|
||||
|
||||
.. figure:: images/ACRN-hybrid-rt-example.png
|
||||
:width: 700px
|
||||
.. figure:: images/ACRN-hybrid-rt-example-1-0.75x.png
|
||||
:align: center
|
||||
:name: arch-hybrid-rt-example
|
||||
|
||||
|
@ -70,8 +70,7 @@ May 2019. The new hybrid mode architecture has the flexibility to
|
||||
support both partition mode and sharing mode simultaneously, as shown in
|
||||
this architecture diagram:
|
||||
|
||||
.. figure:: ../introduction/images/ACRN-V2-high-level-arch.png
|
||||
:width: 700px
|
||||
.. figure:: ../introduction/images/ACRN-V2-high-level-arch-1-0.75x.png
|
||||
:align: center
|
||||
|
||||
ACRN V2 high-level architecture
|
||||
|
@ -128,7 +128,7 @@ As introduced in :ref:`overview_dev`, configuration takes place at
|
||||
:ref:`overview_dev_board_config` and :ref:`overview_dev_config_editor` in
|
||||
the overall development process:
|
||||
|
||||
.. image:: ../getting-started/images/overview_flow.png
|
||||
.. image:: ../getting-started/images/overview_flow-1-0.6x.png
|
||||
|
||||
ACRN source also includes makefile targets to aid customization. See
|
||||
:ref:`hypervisor-make-options`.
|
||||
|