Comment 21 for bug 1652934

There are the following ways to solve the issue:
1. pass 'no-kvmapf' kernel option in L1. This option will disable async pf from L2 to be passed to L0, because it disables it on L1. This will lead to some performance degradation though.
2. there is a kernel patch https://www.spinics.net/lists/kvm/msg142390.html which is not merged (and we can't guess when it will be), and we don't maintain kernel anyway.
3. it's possible though to try to build kvm module (e.g. as dkms) but this might bring more issues than it fixes.

Solution #1 looks best, we're waiting for confirmation that it works.

If it does then we should decide should it be some tunable passed to master node from fuel-qa or some logic in fuel-agent (it generates kernel options for slave nodes). This option can't be passed to any node, because on L0 compute it will lead to performance degradation. Controller nodes will not be affected (no matter HW or VM).