Comment 2 for bug 1853465

Hi Christian,

Thank you for the detailed response. Just to clarify, I'm not pursuing to use nested KVM here actually, but to have a consistent flag across multiple hosts so live-migration of the first level KVM VMs won't fail with:

> [instance: afd27b8f-30df-4eab-b18a-5c269ce97d06] Live Migration failure: operation failed: guest CPU doesn't match specification: missing features: vmx: libvirtError: operation failed

In any case, if newer kernel doesn't need the rmmod trick in postinst and the flag is enabled at boot as you wrote, then tracking down the root cause of the race condition is not the best way to spend our time. So we will take either of #1, #2, #3 you suggested above as the way forward.

I will leave this as Incomplete to let it expired unless other users are willing to test it more. Thanks again for the suggestions!