github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-08-09 12:08:30 +00:00
Code Issues Projects Releases Wiki Activity

doc: update build ACRN doc

Browse Source 
Signed-off-by: guoqingxz <guoqingx.q.zhang@intel.com>
This commit is contained in:
guoqingxz 2020-05-10 16:22:33 +08:00 committed by deb-intel
parent 2db40c9956
commit fb65c42468
2 changed files with 4 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/getting-started/building-from-source.rst
View File

@ -267,8 +267,8 @@ The ``acrn.efi`` will be generated in the ``./hypervisor/build/acrn.efi`` direct
As mentioned in :ref:`ACRN Configuration Tool <vm_config_workflow>`, the As mentioned in :ref:`ACRN Configuration Tool <vm_config_workflow>`, the
Board configuration and VM configuration can be imported from XML files. Board configuration and VM configuration can be imported from XML files.
If you want to build the hypervisor with XML configuration files, If you want to build the hypervisor with XML configuration files,
specify the file location as follows (assuming you're current directory specify the file location as follows (assuming you're at the top level
is at the top level of the acrn-hypervisor directory): of the acrn-hypervisor directory):
.. code-block:: none .. code-block:: none
@ -281,7 +281,7 @@ is at the top level of the acrn-hypervisor directory):
information is retrieved from the corresponding ``BOARD_FILE`` and information is retrieved from the corresponding ``BOARD_FILE`` and
``SCENARIO_FILE`` XML configuration files. The ``TARGET_DIR`` parameter ``SCENARIO_FILE`` XML configuration files. The ``TARGET_DIR`` parameter
specifies what directory is used to store configuration files imported specifies what directory is used to store configuration files imported
from XML files. If the ``TARGED_DIR`` it is not specified, the original from XML files. If the ``TARGED_DIR`` is not specified, the original
configuration files of acrn-hypervisor would be overridden. configuration files of acrn-hypervisor would be overridden.
Follow the same instructions to boot and test the images you created from your build. Follow the same instructions to boot and test the images you created from your build.

9
doc/tutorials/building_acrn_in_docker.rst
View File

@ -49,14 +49,7 @@ Build the Docker Image from Dockerfile
Alternatively, you can build your own local Docker image using the Alternatively, you can build your own local Docker image using the
provided Dockerfile build instructions by following these steps. You'll provided Dockerfile build instructions by following these steps. You'll
need to this this if you're working behind a corporate proxy. need this if you're working behind a corporate proxy.
.. note::
A known `issue
<https://github.com/projectacrn/acrn-hypervisor/issues/4560>`_ exists
while building the ACRN hypervisor. Refer to `Get the Docker Image from
Docker Hub`_ as a temporary way to obtain the Docker Image for the v1.6
release.
#. Download `Dockerfile <https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/Dockerfile>`_ #. Download `Dockerfile <https://raw.githubusercontent.com/projectacrn/acrn-hypervisor/master/doc/getting-started/Dockerfile>`_
to your development machine. to your development machine.