Installation Preparations

Before installation, you need to consider software and hardware compatibility issues and evaluate related configurations and preparations to ensure a smooth installation process.

System Requirements

1️⃣ Storage Space

ItemDescription
Minimum Requirements (Reserved for Windows)At least 100 GB of available space must be reserved on the Windows system drive (only for the Windows OS and basic software usage).
Recommended Dual-System Configuration (DevStation)A separate free partition (unallocated disk space) is required, with a minimum size of 40 GB (80 GB recommended). This space will be dedicated to installing the openEuler DevStation system.

Example:

If your hard drive is 500 GB, a typical partitioning scheme is as follows:

  • Windows system partition: 150 GB (Windows 11 requires about 40 GB, with extra space reserved for commonly used software)
  • Data partition (Drive D): 300 GB (for storing personal files)
  • Free partition: 50 GB (dedicated to openEuler DevStation)

⚠️Note: The free partition must be unformatted. It will be automatically formatted during system installation.

2️⃣ Memory

ItemDescriptionImpact on Dual-System
Minimum Requirement (4 GB)Meets the most basic memory requirement for running either system independentlyWhen running Windows or DevStation, the computer can barely start (but cannot run both systems at the same time).
Recommended Configuration (8 GB DDR4+)Provides a foundation for smooth operation of modern OSsAllows either system in a dual-boot setup to run smoothly with development tools (such as VSCode, Docker, etc.)

🤔Common misconception: A dual-boot system does not run both OSs simultaneously. Only one system can be used at a time, and memory requirements are calculated independently for each system.

3️⃣ UEFI Support

What is UEFI? It is a new boot mode for modern computers (compared to the traditional Legacy BIOS), providing a more secure boot environment and supporting large-capacity drives.

Key ItemRequirement DescriptionFailure Case
MandatoryYour mainboard must support the UEFI boot mode (most computers produced after 2012 support this mode).Using Legacy mode on older computers may cause partitioning failures.
Enabling CSMFor older devices, enable the compatibility support module in the mainboard settings (allows UEFI to support legacy devices).If not enabled, the installation interface may freeze.

▶ How to check the UEFI mode? In Windows, press Win+R, enter msinfo32, and check whether the BIOS mode is UEFI.

▶ Why use UEFI?

  • Supports hard drives larger than 2 TB
  • Faster boot speed
  • More stable dual-system boot (better compatibility between GRUB and Windows Boot Manager)

What if the requirements are not met?

HardwareConsequenceSolution
Insufficient storage"Insufficient disk space" error occurs during installationShrink the Windows partition
Insufficient memorySevere system lag and frequent crashesClose background programs or add more RAM (laptop users should verify memory expansion support)
No UEFI supportInstallation initialization cannot be completedEnable CSM on older computers or create a Legacy-mode bootable media separately

Recommended configuration for actual use cases:

Typical configuration for students or developers:

markdown
Disk: 512 GB SSD
- Allocate 200 GB to Windows (system + basic development environment)
- Allocate 80 GB to DevStation (Linux development environment + containers)
- Use the remaining 232 GB as a shared data partition (NTFS format, accessible by both Windows and Linux)

Memory: 16 GB DDR4 → Handles intensive workloads such as IDEs and virtual machines
Firmware: UEFI mode + Secure Boot disabled → Ensures hardware driver compatibility

Obtaining the Installation Source

Before the installation, you need to obtain the openEuler DevStation image and verification file.

Follow the steps below to obtain the openEuler DevStation image and verification file:

  1. Log in to the openEuler DevStation community mirror site.
  2. Select the openEuler-24.03-LTS-SP2 version.
  3. Based on the architecture and installation scenario of the target environment, select the openEuler DevStation image and verification file to download.
    1. For the AArch64 architecture:
      1. Select the aarch64 directory.
      2. Download the openEuler-24.03-LTS-SP2-DevStation-aarch64-dvd.iso image to the local system.
    2. For the x86_64 architecture:
      1. Select the x86_64 directory.
      2. Download the openEuler-24.03-LTS-SP2-DevStation-x86_64-dvd.iso image to the local system.

`NOTE:`

  • The image of the AArch64 architecture supports the UEFI mode, and the image of the x86_64 architecture supports both the UEFI and Legacy modes.

Verifying Image Integrity

`NOTE:`

This section takes the image integrity verification for the AArch64 architecture as an example. The verification procedure for the x86_64 architecture is the same.

Overview

To prevent incomplete download of the software package due to network or storage device problems during the transmission, verify the integrity of the software package after obtaining it. Only the software package that passes the verification can be deployed.

This is done by comparing the checksum recorded in the verification file with the checksum manually calculated from the ISO file to determine whether the package is complete. If the two values are identical, the ISO file is intact; otherwise, the ISO image has been corrupted and must be downloaded again.

Prerequisites

Before verifying the image integrity, prepare the following files:

  • ISO file: openEuler-24.03-LTS-SP2-DevStation-aarch64-dvd.iso
  • Verification file: openEuler-24.03-LTS-SP2-DevStation-aarch64-dvd.iso.sha256sum. This file stores the integrity verification information of the ISO image. The checksum entries correspond one-to-one with the ISO file values.

Operation Guide

To verify the file integrity, follow the steps below:

  1. Calculate the SHA-256 checksum of the file by running the following command:

    bash
    sha256sum openEuler-24.03-LTS-SP2-DevStation-aarch64-dvd.iso

    After the command is executed, the checksum value is displayed.

  2. Compare the checksum calculated in step 1 with the SHA256 value copied from the verification file.

    If the checksum values are identical, the ISO file is intact. If the checksum values are different, the file integrity has been compromised, and the ISO image needs to be downloaded again.

Creating a Bootable USB Drive

  1. Download Rufus (or use tools such as Etcher or Ventoy).
  2. Insert a USB drive (capacity ≥ 8 GB).
  3. Open Rufus and select the downloaded ISO image.
    1. Partition type: MBR
    2. Target system type: BIOS or UEFI
    3. File system: FAT32
  4. After the process is complete, record the USB drive volume label (for example, "openEuler-24.03-LTS-SP2-DevStation-netin").

Releasing Disk Space in Windows

Partition shrinking steps

  1. Open the disk management interface.

  2. Right-click the target partition and select the option to shrink the volume.

  3. Enter the shrink size (in MB).

    bash
    Recommended formula: (Total space Space used by the system) x 0.3 # For example, on a 100 GB system drive, it is advised to reserve 30 GB for Windows

Space verification

powershell
# Run as Administrator:
Get-Partition | ft -AutoSize
# Verify that "Unallocated" space is displayed