From dc5c5be42a5d6d004a95a4088046c36e627374b7 Mon Sep 17 00:00:00 2001 From: gomico Date: Wed, 25 Dec 2024 14:47:56 +0800 Subject: [PATCH] update English docs to remove " based on 920\ --- .../Installation/installation-preparations.md | 96 ++++++++----------- docs/en/docs/Virtualization/Skylark.md | 2 +- .../docs/Virtualization/managing-devices.md | 4 +- 3 files changed, 41 insertions(+), 61 deletions(-) diff --git a/docs/en/docs/Installation/installation-preparations.md b/docs/en/docs/Installation/installation-preparations.md index b10776515..2d549a7a5 100644 --- a/docs/en/docs/Installation/installation-preparations.md +++ b/docs/en/docs/Installation/installation-preparations.md @@ -5,17 +5,17 @@ This section describes the compatibility of the hardware and software and the re - [Installation Preparations](#installation-preparations) - - [Obtaining the Installation Source](#obtaining-the-installation-source) - - [Release Package Integrity Check](#release-package-integrity-check) - - [Introduction](#introduction) - - [Prerequisites](#prerequisites) - - [Procedures](#procedures) - - [Installation Requirements for PMs](#installation-requirements-for-pms) - - [Hardware Compatibility](#hardware-compatibility) - - [Minimum Hardware Specifications](#minimum-hardware-specifications) - - [Installation Requirements for VMs](#installation-requirements-for-vms) - - [Virtualization Platform Compatibility](#virtualization-platform-compatibility) - - [Minimum Virtualization Platform Specifications](#minimum-virtualization-platform-specifications) + - [Obtaining the Installation Source](#obtaining-the-installation-source) + - [Release Package Integrity Check](#release-package-integrity-check) + - [Introduction](#introduction) + - [Prerequisites](#prerequisites) + - [Procedures](#procedures) + - [Installation Requirements for PMs](#installation-requirements-for-pms) + - [Hardware Compatibility](#hardware-compatibility) + - [Minimum Hardware Specifications](#minimum-hardware-specifications) + - [Installation Requirements for VMs](#installation-requirements-for-vms) + - [Virtualization Platform Compatibility](#virtualization-platform-compatibility) + - [Minimum Virtualization Platform Specifications](#minimum-virtualization-platform-specifications) @@ -25,22 +25,22 @@ Obtain the openEuler release package and verification file before the installati Perform the following operations to obtain the openEuler release package: -1. Visit the [openEuler](https://www.openeuler.org/en/) website. -2. Click **Download > Software Packages**. -3. Click **Server Image** below **openEuler 22.03 LTS SP1**. The ISO list is displayed. - - **aarch64**: ISO image files of the AArch64 architecture - - **x86_64**: ISO image files of the x86_64 architecture - - **source**: ISO image files of the openEuler source code -4. Select the target openEuler release package and verification file based on the actual environment. - - AArch64 architecture: - 1. Click **aarch64**. - 2. If you install openEuler from a local source, download the release package **openEuler-22.03-LTS-SP1-aarch64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-aarch64-dvd.iso.sha256sum** to the local host. - 3. If you install openEuler through the network, download the release package **openEuler-22.03-LTS-SP1-netinst-aarch64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-netinst-aarch64-dvd.iso.sha256sum** to the local host. - - - x86_64 architecture: - 1. Click **x86_64**. - 1. If you install openEuler from a local source, download the release package **openEuler-22.03-LTS-SP1-x86_64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-x86_64-dvd.iso.sha256sum** to the local host. - 1. If you install openEuler through the network, download the release package **openEuler-22.03-LTS-SP1-netinst-x86_64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-netinst-x86_64-dvd.iso.sha256sum** to the local host. +1. Visit the [openEuler](https://www.openeuler.org/en/) website. +2. Click **Download > Software Packages**. +3. Click **Server Image** below **openEuler 22.03 LTS SP1**. The ISO list is displayed. + - **aarch64**: ISO image files of the AArch64 architecture + - **x86_64**: ISO image files of the x86_64 architecture + - **source**: ISO image files of the openEuler source code +4. Select the target openEuler release package and verification file based on the actual environment. + - AArch64 architecture: + 1. Click **aarch64**. + 2. If you install openEuler from a local source, download the release package **openEuler-22.03-LTS-SP1-aarch64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-aarch64-dvd.iso.sha256sum** to the local host. + 3. If you install openEuler through the network, download the release package **openEuler-22.03-LTS-SP1-netinst-aarch64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-netinst-aarch64-dvd.iso.sha256sum** to the local host. + + - x86_64 architecture: + 1. Click **x86_64**. + 2. If you install openEuler from a local source, download the release package **openEuler-22.03-LTS-SP1-x86_64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-x86_64-dvd.iso.sha256sum** to the local host. + 3. If you install openEuler through the network, download the release package **openEuler-22.03-LTS-SP1-netinst-x86_64-dvd.iso** and the verification file **openEuler-22.03-LTS-SP1-netinst-x86_64-dvd.iso.sha256sum** to the local host. >![](./public_sys-resources/icon-note.gif) **Note** > When the network is available, install openEuler through the network because the ISO release package is small. @@ -69,21 +69,21 @@ Verification file: **openEuler-22.03-LTS-SP1-aarch64-dvd.iso.sha256sum** To verify the file integrity, perform the following operations: -1. Obtain the verification value in the verification file. Run the following command: +1. Obtain the verification value in the verification file. Run the following command: - ``` - $ cat openEuler-22.03-LTS-SP1-aarch64-dvd.iso.sha256sum + ```shell + cat openEuler-22.03-LTS-SP1-aarch64-dvd.iso.sha256sum ``` -2. Calculate the SHA256 verification value of the file. Run the following command: +2. Calculate the SHA256 verification value of the file. Run the following command: - ``` - $ sha256sum openEuler-22.03-LTS-SP1-aarch64-dvd.iso + ```shell + sha256sum openEuler-22.03-LTS-SP1-aarch64-dvd.iso ``` After the command is run, the verification value is displayed. -3. Check whether the values obtained from the step 1 and step 2 are consistent. +3. Check whether the values obtained from the step 1 and step 2 are consistent. If the values are consistent, the ISO file is not damaged. Otherwise, the file is damaged and you need to obtain it again. @@ -97,8 +97,8 @@ You need to take hardware compatibility into account before installing openEuler >![](./public_sys-resources/icon-note.gif) **NOTE:** > ->- TaiShan 200 servers are based on Huawei Kunpeng 920 processors. ->- Currently, only Huawei TaiShan and FusionServer Pro servers are supported. More servers from other vendors will be supported in the future. +>- TaiShan 200 servers are powered by Huawei Kunpeng 920 processors. +>- Currently, only Huawei TaiShan and FusionServer Pro servers are supported. More servers from other vendors will be supported in the future. **Table 1** Supported servers @@ -128,8 +128,8 @@ To install the openEuler OS on a VM, the VM must meet the following requirements You need to take the compatibility of the virtualization platform into account before installing openEuler. Currently, the following virtualization platforms are supported: -- A virtualization platform created by the virtualization components of openEuler (QEMU and KVM provided in the release package) with openEuler as the host OS -- An x86 virtualization platform of Huawei public cloud +- A virtualization platform created by the virtualization components of openEuler (QEMU and KVM provided in the release package) with openEuler as the host OS +- An x86 virtualization platform of Huawei public cloud ### Minimum Virtualization Platform Specifications @@ -143,23 +143,3 @@ You need to take the compatibility of the virtualization platform into account b | CPU | Two CPUs| | Memory | ≥ 4 GB (8 GB or higher recommended for better user experience) | | Hard drive | ≥ 32 GB (120 GB or higher recommended for better user experience) | - - - - - - - - - - - - - - - - - - - - diff --git a/docs/en/docs/Virtualization/Skylark.md b/docs/en/docs/Virtualization/Skylark.md index acce23b5b..5b259e99c 100644 --- a/docs/en/docs/Virtualization/Skylark.md +++ b/docs/en/docs/Virtualization/Skylark.md @@ -128,7 +128,7 @@ After the Skylark component is installed, you can modify the configuration file ### LLC/MB Interference Control -Skylark's interference control on LLC/MB depends on the RDT/MPAM function provided by hardware. For Intel x86_64 processors, **rdt=cmt,mbmtotal,mbmlocal,l3cat,mba** needs to be added to kernel command line parameters. For Kunpeng920 processors, **mpam=acpi** needs to be added to kernel command line parameters. +Skylark's interference control on LLC/MB depends on the RDT/MPAM function provided by hardware. For Intel x86_64 processors, **rdt=cmt,mbmtotal,mbmlocal,l3cat,mba** needs to be added to kernel command line parameters. For Kunpeng 920 processors, **mpam=acpi** needs to be added to kernel command line parameters. - **MIN_LLC_WAYS_LOW_VMS** is an integer used to control the number of LLC ways that can be accessed by low-priority VMs. The value ranges from 1 to 3, with the default value being 2. During initialization, Skylark limits the numfer of accessible LLC ways for low-priority VMs to this value. diff --git a/docs/en/docs/Virtualization/managing-devices.md b/docs/en/docs/Virtualization/managing-devices.md index 1e9998ace..2b6cf356c 100644 --- a/docs/en/docs/Virtualization/managing-devices.md +++ b/docs/en/docs/Virtualization/managing-devices.md @@ -447,14 +447,14 @@ To configure SR-IOV passthrough for a NIC, perform the following steps: >Disabling the SR-IOV function: >To disable the SR-IOV function after the VM is stopped and no VF is in use, run the following command: >The following uses the Hi1822 NIC (corresponding network interface name: eth0) as an example: -> + > >```shell >echo 0 > /sys/class/net/eth0/device/sriov_numvfs >``` #### SR-IOV Passthrough for the HPRE Accelerator -The accelerator engine is a hardware acceleration solution provided by TaiShan 200 server based on the Kunpeng 920 processor. The HPRE accelerator is used to accelerate SSL/TLS applications. It significantly reduces processor consumption and improves processor efficiency. +The accelerator engine is a hardware acceleration solution provided by TaiShan 200 servers. The HPRE accelerator is used to accelerate SSL/TLS applications. It significantly reduces processor consumption and improves processor efficiency. On the Kunpeng server, the VF of the HPRE accelerator on the host needs to be passed through to the VM for internal services of the VM. **Table 3** HPRE accelerator description -- Gitee