Feature List

Supports hybrid deployment for BMSs and KVMs in availability zones (AZs). Each AZ must contain only x86 or Kunpeng servers.

 

Constraints

• The management nodes must use either Kunpeng or x86 servers. They do not support hybrid deployments.
• Only AZ-level hybrid deployments are supported.

Supported on VMs: no

The virtualization software cannot be used on VMs.

Supports hybrid deployment of Kunpeng and x86 servers for Docker containers.

 

Constraints

Kubernetes management nodes do not support hybrid deployment.

 

Supported on VMs: no

The virtualization software cannot be used on VMs.

Supports oVirt use on the Kunpeng platform.

 

Supported on VMs: no

The virtualization software cannot be used on VMs.

Large-scale Docker container networking is classified into Open vSwitch networking and Calico networking.

• Open vSwitch

Open vSwitch (OVS) is an open-source, industrial-grade multi-layer virtual switch software. It implements large-scale network automation through programmable expansion, with a wide compatibility with standard management interfaces and protocols.

Application Scope

• Container orchestration engine deployment.
• Large clusters (more than 100 physical nodes or Pod objects).
• Calico

Calico is a pure Layer 3 protocol that does not use an overlay network. It provides communication between multiple hosts for Docker containers. With virtual routing rather than virtual switching, each virtual router uses BGP to transmit reachability information (routes) to the remaining data centers.

Application Scope

• Container orchestration engine deployment.
• Large clusters (more than 100 physical nodes or Pod objects).

Supported on VMs: yes

The Docker container technology can be used on VMs.

Kube-OVN integrates the OVN-based (OVN is short for open virtual network) network virtualization with Kubernetes. It offers an advanced container network fabric for enterprises with the most functions and the easiest operation. The software is open sourced based on Apache 2.0. Kube-OVN 1.2.0 officially supports the ARM64 architecture and can natively run on TaiShan servers.

 

Supported on VMs: yes

The Docker container technology can be used on VMs.

Supports OVS software offload and acceleration on the Kunpeng platform.

• VM user-mode OVS scenario. 
• Only cluster type (CT) services are accelerated.

Supported on VMs: yes

The virtualization software cannot be used on VMs.

Supports OVS flow table NIC acceleration (based on the Mellanox ConnectX-5 NIC) on the Kunpeng platform.

 

• VM kernel-mode OVS scenario. 
• SR-IOV passthrough mode. 
  
• Live VM migration is not supported.

The virtualization software cannot be used on VMs.

Supports user-mode OVS flow table NIC acceleration.

 

• VM user-mode OVS scenario.
• SR-IOV passthrough mode. 

The virtualization software and hardware collaboration solution cannot be used on VMs.

The Kubernetes SR-IOV device passthrough plugin automatically identifies and manages SR-IOV devices on nodes, and automatically completes the mounting process based on the SR-IOV device type specified in the configuration file, streamlining the usage process.

 

• Supported OS: openEuler 22.03 LTS SP4 or later.
• Constraints: Before using the SR-IOV device plugin, ensure that the VF of the SR-IOV device has been created.

This feature can be used only in container scenarios.

The KAE device plugin automatically manages all KAE devices on the server and streamlines the KAE device passthrough operations. Using this plugin, you can pass through KAE devices to containers through simple statements to accelerate encryption, decryption, and data compression, and set QoS for KAE devices.

 

Before using the KAE device plugin, ensure that the VF of the KAE device has been created.

This feature can be used only in container scenarios.

Provides the SPDK+Ceph solution to accelerate Ceph storage clients in virtualization scenarios, improving I/O read and write capabilities.

 

Constraints

Only the Ceph cloud disk scenario is supported.

Supported on VMs: no

The virtualization software cannot be used on VMs.

Guest NUMA can be configured for VMs. The vCPU NUMA status can be identified in VMs. Service software optimizes memory resource usage based on the guest NUMA topology.

 

Constraints

After guest NUMA is configured, the service software may fail to identify NUMA. If the service software is not optimized for identifying NUMA, cross-NUMA memory access occurs, causing performance deterioration.

Supported on VMs: no

The virtualization software cannot be used on VMs.

It also leverages hardware resources more efficiently, increases the system throughput, and speeds up responses to requests.

Constraint

The topology information of the physical CPU cluster must be correctly mapped to the VM.

Supported on VMs: yes

The enabling mode on a VM is the same as that on a physical machine. Supported OS must be openEuler 22.03 LTS SP2 or later.

This feature uses shared memory to relay vCPU preemption status from the hypervisor to VMs, minimizing conflict-induced errors and improving system stability.

Constraint

Supported OSs: openEuler 20.03 LTS SP1 or later

Libvirt 6.2.0 or later

QEMU 6.2.0 or later

Supported on VMs: yes

The enabling mode on a VM is the same as that on a physical machine. Supported OS must be openEuler 20.03 LTS SP1 or later.

By leveraging non-maskable interrupts (NMIs), this feature monitors interrupt responses in real time to detect deadlocks within VMs, ensuring recovery from unresponsive states caused by deadlocks.

Constraint

Supported OSs: openEuler 22.03 LTS SP2

Libvirt 6.2.0 or later

QEMU 6.2.0 or later

Supported on VMs: yes

The enabling mode on a VM is the same as that on a physical machine. Supported OS must be openEuler 22.03 LTS SP2 or later.

The cache size can be specified in the XML configuration file or QEMU command for starting VMs.

Constraint

• Physical machine: openEuler 22.03 LTS SP4
• Virtual machine: openEuler 22.03 LTS SP4

Supported on VMs: yes

Physical machine: openEuler 22.03 LTS SP4

Virtual machine: openEuler 22.03 LTS SP4

The Kunpeng Accelerator Engine (KAE) encryption and decryption module uses the KAE to implement the RSA, SM3, SM4, DH, MD5, and AES algorithms. It provides high-performance symmetric and asymmetric encryption/decryption algorithms based on the lossless user-mode driver framework. Compatible with OpenSSL 1.1.1a and later versions, it supports the synchronous and asynchronous mechanisms. This module can accelerate applications in VMs and containers.

 

Constraint

You need to apply for a license on a physical machine.

Supported on VMs: yes

The VM OS must be openEuler 20.03 LTS SP1 (or later) or openEuler 22.03 LTS SP1 (or later).

In the Kubernetes container deployment scenario, the CPU scheduling range of containers can be automatically adjusted based on the CPU load of compute nodes to ensure NUMA affinity.

 

Constraint

Supported OSs: openEuler 20.03 LTS SP3 and openEuler 22.03 LTS SP4

Kubernetes version: 1.23.x and 1.28.4

containerd version: 1.7.14

Docker version: 20.10.14

Constraints:

• Use containerd as the container runtime.
• Use Dockershim as the Runtime communication component.

 

Supported on VMs: No

This feature can be used only in container scenarios.

The Kubernetes MPAM plugin can dynamically isolate the resource usage of offline services in hybrid deployment scenarios. When resources are idle, offline services can use more resources. When resources are insufficient, the resource usage of offline services is limited to ensure the performance of online services and improve the overall resource utilization of the system.

 

Constraint

Supported OS: openEuler 22.03 LTS SP4 or later

Constraints: Before using the MPAM plugin, ensure that MPAM has been enabled.

 

Supported on VMs: No

This feature can be used only in container scenarios.

This feature increases or decreases the number of vCPUs of a running VM without interrupting services.

 

Constraint

The CPU specifications of the VM applying the hotplug feature cannot exceed the maximum CPU specifications supported by the hypervisor and the maximum CPU specifications supported by the guest OS.

 

Supported on VMs: No

The virtualization software cannot be used on VMs.

This feature makes the VM's XML configuration file contain a NUMA node with 0 initial memory and dynamically adds memory to the NUMA node using memory hotplug commands.

 

Constraint

VM specification：Among the NUMA nodes configured for a VM, a maximum of one NUMA node whose initial memory is 0 is supported.

Hotplug specification：The VM XML configuration file must contain the maxMemory node as required by QEMU. This node specifies the number of memory slots (setting the slots attributes) dedicated for the VM's memory hotplug and the maximum total memory that can be achieved through hotplug (setting the value of maxMemory).

Supported on VMs: No

The virtualization software cannot be used on VMs.

When hardware-assisted virtualization acceleration is enabled on new-model Kunpeng 920 processors, the direct interrupt injection of GICv4.1 (including vSGI passthrough) cuts interrupt response times and enhances throughput for demanding network and I/O workloads.

 

Constraint

Only new Kunpeng 920 processor models are supported.

 

Supported on VMs: No

The virtualization software cannot be used on VMs.

During the VM live migration, compression technologies (for example, zlib library) are usually used on the source physical host to compress memory pages before data transmission, and then the memory pages are decompressed on the target physical host, thereby speeding up the VM live migration.

 

Constraint

• Version: For Arm-based KVM and QEMU virtualization platforms, only libvirt 10.0.0 and later versions, and QEMU 6.2.0 are supported.
• License: KAE license.

• The application environment must meet the software and hardware environment requirements supported by KAE.

 

Supported on VMs: No

KAE passthrough live migration specifically addresses the scenario where VMs are configured with KAE passthrough devices, offering enhanced operational flexibility and continuous service availability.

 

Constraint

Supported OSs:

openEuler 22.03 LTS SP4

Constraints:

Version: For Arm-based KVM and QEMU virtualization platforms, only libvirt 6.2.0 and QEMU 6.2.0 are supported.

License: KAE license.

The application environment must meet the software and hardware environment requirements supported by KAE.

 

Supported on VMs: No

PMU virtualization enables PMU events to be collected on a VM, which helps analyze and optimize the performance of the VM OS and service software.

 

Constraint

Supported OS: openEuler 22.03 LTS SP4 or later

 

Supported on VMs: Yes

The enabling method on the VM is the same as that on the physical machine.

MPAM is used to allocate VMs to different bandwidth/cache partitions, implementing rate limiting or priority control.

 

Constraint

Supported OS: openEuler 24.03 LTS SP2

Constraints: Arm-based KVM and QEMU virtualization platforms are required. Only libvirt 9.10.0 and QEMU 8.2.0 are supported.

 

Supported on VMs: No

The virtualization software cannot be used on VMs.

The Workload Aware Acceleration System (WAAS) detects and analyzes the workload of user processes and utilizes a series of optimization methods to improve the service performance and running efficiency of applications on VMs.

 

Constraints

The system parameter configurations are effective only for application services that are tuned online. Only Redis, Nginx, MySQL, Spark, Hive and HBase are supported so far. WAAS is not responsible for the impact on other applications.

Supported on VMs: yes

It can be used only on VMs. The VM OS must be openEuler 22.03 LTS SP3.