Installation Preparations

This section describes the compatibility of the hardware and software and the related configurations and preparations required for the installation.

Obtaining the Installation Source

Obtain the openEuler release package and verification file before the installation.

Perform the following operations to obtain the openEuler release package:

  1. Visit the openEuler 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.

Note
When the network is available, install openEuler through the network because the ISO release package is small. The release package of AArch64 architecture supports UEFI mode, while the release package of x86_64 architecture supports UEFI mode and Legacy mode.

Release Package Integrity Check

NOTE
This section describes how to verify the integrity of the release package for the AArch64 architecture. The procedure for verifying the integrity of the release package for the x86_64 architecture is the same.

Introduction

To prevent the software package from being incompletely downloaded due to network or storage device faults during transmission, you need to verify the integrity of the software package after obtaining it. Only the software package that passes the verification can be installed.

Compare the verification value recorded in the verification file with the calculated verification value of the ISO file to check whether the software package is complete. If the values are consistent, the ISO file is not damaged. Otherwise, the file is damaged and you need to obtain it again.

Prerequisites

Before verifying the integrity of the release package, you need to prepare the following files:

ISO file: openEuler-22.03-LTS-SP1-aarch64-dvd.iso

Verification file: openEuler-22.03-LTS-SP1-aarch64-dvd.iso.sha256sum

Procedures

To verify the file integrity, perform the following operations:

  1. Obtain the verification value in the verification file. Run the following command:

    $ cat openEuler-22.03-LTS-SP1-aarch64-dvd.iso.sha256sum 
    
  2. Calculate the SHA256 verification value of the file. Run the following command:

    $ 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.

    If the values are consistent, the ISO file is not damaged. Otherwise, the file is damaged and you need to obtain it again.

Installation Requirements for PMs

To install the openEuler OS on a PM, the PM must meet the following requirements.

Hardware Compatibility

You need to take hardware compatibility into account before installing openEuler. Table 1 describes supported servers.

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.

Table 1 Supported servers

Server TypeServer NameServer Model
Rack serverTaiShan 2002280 balanced model
Rack serverFusionServer ProFusionServer Pro 2288H V5
NOTE:
The server must be configured with the Avago SAS3508 RAID controller card and the LOM-X722 NIC.

Minimum Hardware Specifications

Table 2 lists the minimum hardware specifications supported by openEuler.

Table 2 Minimum hardware specifications

ComponentMinimum Hardware Specifications
ArchitectureAArch64 or x86_64
CPUTwo single-core 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)

Installation Requirements for VMs

To install the openEuler OS on a VM, the VM must meet the following requirements.

Virtualization Platform Compatibility

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

Minimum Virtualization Platform Specifications

Table 3 lists the minimum virtualization platform specifications supported by openEuler.

Table 3 Virtualization platform specifications

ComponentVirtualization Platform Specifications
ArchitectureAArch64 or x86_64
CPUTwo 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)

Bug Catching

Buggy Content

Bug Description

Submit As Issue

It's a little complicated....

I'd like to ask someone.

PR

Just a small problem.

I can fix it online!

Bug Type
Specifications and Common Mistakes

● Misspellings or punctuation mistakes;

● Incorrect links, empty cells, or wrong formats;

● Chinese characters in English context;

● Minor inconsistencies between the UI and descriptions;

● Low writing fluency that does not affect understanding;

● Incorrect version numbers, including software package names and version numbers on the UI.

Usability

● Incorrect or missing key steps;

● Missing prerequisites or precautions;

● Ambiguous figures, tables, or texts;

● Unclear logic, such as missing classifications, items, and steps.

Correctness

● Technical principles, function descriptions, or specifications inconsistent with those of the software;

● Incorrect schematic or architecture diagrams;

● Incorrect commands or command parameters;

● Incorrect code;

● Commands inconsistent with the functions;

● Wrong screenshots.

Risk Warnings

● Lack of risk warnings for operations that may damage the system or important data.

Content Compliance

● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

● Copyright infringement.

How satisfied are you with this document

Not satisfied at all
Very satisfied
Submit
Click to create an issue. An issue template will be automatically generated based on your feedback.