On 2024-08-26 09:47, Christian Theune wrote:
Hi,
colleagues noticed that they are increasingly encountering software that
requires x86-64-v2 (typically complained by a container’s glibc) and they need
to select specific architectures in our VMs.
We’re currently in the process of migrating away from Intel to AMD (about few
Intel hosts left in the pool) and we could target specific AMD architectures in
the future, but would obviously then loose the ability to potentially mix in
Intel in the future again.
We’ve been quite happy running mostly generic architectures except for a few
specific workloads that benefit from faster TLS with hardware support.
Reading up on the issue it looks like the microarchitecture levels defined in
2020 would have exactly the intention to make managing mixed fleets easier -
and I guess RedHat would have an interest to extend Qemu/KVM to match this?
https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels
I wasn’t able to find anything on the Internet regarding Qemu development.
Proxmox seems to have simply defined manual presets:
https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines
I guess I could also provide those settings as defaults, but I’m wondering
whether this would be better placed for long term support in Qemu directly?
I believe that current versions of qemu (and probably libvirt as well)
allow selecting specific CPU generations with more granularity than
that old naming scheme, which (according to Wikipedia) only covers
differences between CPUs that are now somewhat old.
See this page for the possible values and how they map to that name scheme:
https://www.qemu.org/docs/master/system/i386/cpu.html
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
