v2.17.0 missing AVX support
Issue description
AVX support is disabled in OS images of Constellation.
To reproduce
- Spawn a Constellation cluster with version 2.17.0
- Spawn a nodes shell on a node
-
lscpu | grep -i avxis empty
Environment
AWS, Azure
Expected behavior
lscpu | grep -i avx prints AVX
Additional info
We are currently investigating an appropriate fix.
Mitigation
This is only required if your deployments depend on AVX instructions. In that case: use cluster version 2.16.4.
We have debugged the issue and identified a misbehaving hypervisor for AWS and Azure. AWS is working on a fix. Azure confirmed that the issue is known and a fix is close to being deployed.
Do you have any new information about this topic on aws/azure?
@derpsteb Has there been any movement on this as far as on Azure's side? Or is there a website we could visit to track updates?
@jeffreyflynt I just tried and it seems to be fixed on Azure. Do you still experience issues with AVX on Azure?
@thomasten I didn't want to try to upgrade if it were not ready. I did before when I upgraded to 2.17 and had to roll back.
Fixed on Azure, follow-up issue regarding AWS: #3501
just a question:
is this fixed solely for plain/old AVX or including avx2, avx-512 (if available)?
this one should give all AVX versions:
lscpu | grep -o "avx[^ ]*"
This is fixed for XSTATE features in general, including all available AVX versions.