...

If you see output similar to the following example from Oracle Linux, this shows services that implicitly enable CPU accounting:

/usr/lib/systemd/system/unified-monitoring-agent_config_downloader.service:CPUQuota=40%
/usr/lib/systemd/system/unified-monitoring-agent.service:CPUQuota=40%

Depending on the service and the environment, it may or may not be possible to disable or uninstall the service. For example, the service shown in the OCI example above is required for Compute Instance Monitoring. It is automatically installed if Instance Monitoring is on, and it may be undesirable to disable it. This question must be reviewed and answered with knowledge of the customer requirements.

Solution

The cause of the problem is that CPU accounting is enabled on the Linux host system.

...

• If possible disable or remove the software that enables CPU accounting and reboot Linux before starting the emulator again.
• If you cannot remove or disable the offending software because of technical or customer environment restrictions, you can enable one of the following workarounds:
  • Remove the limitation on real-time scheduling:
    # sysctl -w kernel.sched_rt_runtime_us=-1 (add to sysctl.conf to make permanent
    To make the configuration permanent, add kernel.sched_rt_runtime_us=-1 to a file in /etc/sysctl.d (e.g., 90-rt.conf), or to sysctl.conf (deprecated in newer Linux versions).
    This configuration introduces the risk that a run-away real-time process could starve other processes and in extreme cases, lock up the system. The default value of this parameter is 950000 (=0.95 seconds).
  • Disable CPU accounting at boot by adding the following parameter to the kernel boot line:
    cgroup_disable=cpu
    Test this during an interactive boot first. If satisfied with the result, make it permanent. For example, by using:
    # grubby --update-kernel=ALL --args="cgroup_disable=cpu".
    Please note: this setting may prevent some software packages from running that are dependent on CPU accounting.

...