• With proxmox 8 and the new standard x86-64-v2-AES cpu type...is there any benefit using it over "host"? ... x86-64-v2-AES is a generic type.
  • qemu-x86_64-v2-aes. ... x86_64-v2-aesOpenBenchmarking.orgPhoronix Test Suite2 x QEMU Virtual 2.5+ (24 Cores) QEMU Standard PC (i440FX + PIIX 1996)...
  • The backend default is kvm64 which works on essentially all x86_64 host CPUs and the UI default when creating a new VM is x86-64-v2-AES...
  • I just upgrade my Proxmox VE to the latest v8.0.3. The release notes said the default CPU type of the new VM is X86-64-v2-AES.
  • This patchset adds new AES-XTS implementations that accelerate disk and file encryption on modern x86_64 CPUs.
  • One of the benefits expected from switching the base architecture to x86_64-v2 would be that some newer processor instructions can be used to optimize the distro.
  • Based on the above explanation, I ask you, will devices with x86_64 architecture support (before x86_64-v2) be more likely to be discontinued by distros?
  • The Linux kernel configuration item CONFIG_CRYPTO_AES_X86_64 ... See http://csrc.nist.gov/encryption/aes/ for more information.
  • For example x86-64-v2 means that a CPU support not only the basic x86-64 instructions set, but also other instructions like SSE4.2, SSSE3 or POPCNT.
  • I'm trying to build my docker container based on keycloak:21.0, but it fails on build.sh, and says: Fatal glibc error: CPU does not support x86-64-v2.