Elasticsearch/Kibana Service Startup Failure Due to Unsupported CPU Instruction Set

Elastic Search
1

Description:

We are facing an issue while starting the Elasticsearch/Kibana service on the current virtual machine. The application fails during startup because the host CPU does not support the instruction sets required by the bundled executable/image.

Error Observed:
```root@virtkibana:~# journalctl -u elasticsearch.service --no-pager
May 08 04:19:04 virtkibana systemd[1]: Starting elasticsearch.service - Elasticsearch...
May 08 04:19:04 virtkibana systemd-entrypoint[8297]: The current machine does not support all of the following CPU features that are required by the image: [CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA, F16C].
May 08 04:19:04 virtkibana systemd-entrypoint[8297]: Please rebuild the executable with an appropriate setting of the -march option.
May 08 04:19:04 virtkibana systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
May 08 04:19:04 virtkibana systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
May 08 04:19:04 virtkibana systemd[1]: Failed to start elasticsearch.service - Elasticsearch.

Log Reference:

May 08 04:19:04 virtkibana systemd-entrypoint[8297]:
Please rebuild the executable with an appropriate setting of the -march option.

Impact:

  • Elasticsearch/Kibana service is unable to start.

  • Portal functionality is unavailable.

  • Deployment on the current VM/host is blocked.

Probable Cause:
The deployed Elasticsearch/Kibana image or binary was built targeting newer CPU architectures requiring advanced instruction sets (AVX/AVX2 and related features), which are not available on the current VM host CPU.

Required Action:

  • Verify CPU compatibility on the VM/hypervisor host.

  • Use a compatible Elasticsearch/Kibana version built for older CPU architectures, OR

  • Rebuild the executable/image using a lower -march target compatible with the current hardware, OR

  • Migrate the workload to a host supporting AVX/AVX2 instructions.

Environment:

  • Service: Elasticsearch / Kibana

  • Host Type: Virtual Machine

  • OS: Linux

  • Startup Method: systemd

Severity:
High – Service unavailable.

Expected Result:
Elasticsearch/Kibana services should start successfully without CPU compatibility errors.

2

we have the same issue.

3

I had the same issue and posted about it here: Elasticseach 9.4.0 Won't Start on Nehalem CPU "does not support all the following CPU features"

There is a pull request to fix the issue: Pin server-launcher native -march to x86-64-v2 by JVerwolf · Pull Request #148542 · elastic/elasticsearch · GitHub