Back
List of Supported Guest OS
The HRPC 6Gf KVM version supports all guest OS on virtual machines supported by QEMU/KVM.
For details on the guest OS supported by QEMU/KVM, please see the this website.
CPU Compatibility
x86-64 Microarchitecture Compatibility
The operating platform of KVM has a common hardware virtualization layer called x86-64 Microarchitecture levels, and the idea is to know what OS this common layer supports. This idea eliminates the contradiction that a guest OS “A” is guaranteed to work with a certain hypervisor “Ω”, but that hypervisor “Ω” does not guarantee the operation of guest OS “A”.x86-64-v1An early 64-bit extension, widely used for older CPUs and systems requiring broad compatibility. Many older operating systems and distributions run at this level.x86-64-v2It adds instruction sets such as SSE4.x and POPCNT, providing improved performance and compatibility. Many modern operating systems use this level. There is also x86-64-v2-aes, which adds AES support instructions to this level.x86-64-v3AVX, AVX2, AES-NI, etc. are added, making it ideal for data encryption and scientific and technical calculations. This level is recommended by the latest Windows and Linux distributions.x86-64-v4The latest instruction sets such as AVX-512 and VNNI have been added, which are advantageous for machine learning and large-scale parallel computing. Most new OSes support this level.
The correspondence table between x86-64 Micro-architecture Level and major OS is as follows.
level | Main instruction set/features | Supported OS/Distributions |
---|---|---|
x86-64-v1 | Basic x86-64 instruction set SSE (Streaming SIMD Extensions) | Windows: Windows 7 and later, Windows Server 2008 and later Linux: RHEL 6/7/8, CentOS 6/7, Ubuntu 16.04 and later, Debian 9/10 BSD: FreeBSD 11 and later |
x86-64-v2 | SSE3, SSE4.1, SSE4.2 POPCNT, CX16, LZCNT | Windows: Windows 10, Windows Server 2016 and later Linux: RHEL 7/8, Ubuntu 18.04 and later, Debian 10/11, Fedora 30 and later, Arch Linux BSD: FreeBSD 12 and later |
x86-64-v3 | AVX, AVX2, FMA3 AES-NI (Advanced Encryption Standard) | Windows: Windows 10, Windows 11, Windows Server 2019 and later Linux: RHEL 8/9, Ubuntu 20.04 and later, Debian 11 and later, Fedora 32 and later, Arch Linux BSD: FreeBSD 12 and later |
x86-64-v4 | AVX-512 CLWB (Cache Line Write Back) VAES (Vector AES), VNNI (Vector Neural Network Instructions) | Windows: Windows 11, Windows Server 2022 Linux: RHEL 9, Ubuntu 22.04 and later, Debian 12 and later, Fedora 34 and later, Arch Linux BSD: FreeBSD 13 and later |
The relationship between High Response Private Cloud and x86-64 Micro-architecture level is as follows:
Model | x86-64 Microarchitecture levels |
---|---|
HRPC 6Gf EPYC 9004 | Up to x86-64-v4 available |
HRPC 6Gf Xeon 5411N | Up to x86-64-v4 available |
For the relationship between x86-64 Micro-architecture level and individual CPUs, and the relationship with instruction sets, please refer to Support Information/Manual/HRPC – Proxmox VE/Creating a New Virtual Machine/About CPU and Memory .
OS-specific issues
EXT file systems are not recommended when installing Linux OS
Generally, it is not recommended to use “ext2/3/4” as a file system.
Generally, virtualized systems often share storage, and if a virtual machine generates a large amount of I/O, it affects other virtual machines in the same host, resulting in storage latency and causing this problem.
Defragmentation settings when installing Windows Server OS
Windows Server runs a defragmentation function on a regular basis, which can place unnecessary strain on storage in certain environments.