Thanks for fixing it @mruffell!
Yes, we did have KSM enabled on the hypervisor where we hit this issue.
Thanks for fixing it @mruffell!
Yes, we did have KSM enabled on the hypervisor where we hit this issue.