Type to search.

Override kernel version check

Serverless Unavailable

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Unavailable

    This functionality is not available in Elastic Cloud Serverless.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

The -no-kernel-version-check flag, or the no-kernel-version-check key in the Universal Profiling Agent configuration file, controls the kernel version compatibility check during the Universal Profiling Agent’s startup process. The kernel version compatibility check enforces the minimum kernel version supported, and prevents the profiling agent from running on certain kernel versions with known issues. When the no-kernel-version-check is set to true, the compatibility check is bypassed, allowing Universal Profiling Agent execution to proceed regardless of the kernel version. By default, this option is set to false, and the kernel compatibility version check is performed as usual.

Warning

Take extra caution when using this configuration option, especially when running the Universal Profiling Agent on older kernels with backported eBPF functionalities. Setting this option to true on kernels with unfixed eBPF bugs can crash your system.

The following example shows how to configure the -no-kernel-version-check in the Universal Profiling agent CLI:

Shell
sudo pf-host-agent/pf-host-agent -no-kernel-version-check=true

It is also possible to use the environment variable PRODFILER_NO_KERNEL_VERSION_CHECK=true to set this configuration.