-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.17.0 missing AVX support #3262
Comments
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: |
This is fixed for XSTATE features in general, including all available AVX versions. |
Issue description
AVX support is disabled in OS images of Constellation.
To reproduce
lscpu | grep -i avx
is emptyEnvironment
AWS, Azure
Expected behavior
lscpu | grep -i avx
printsAVX
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.
The text was updated successfully, but these errors were encountered: