We are also experiencing this issue now from months, since we upgraded to Proxmox 7. Unfortunately, many users are reporting this exact same bug (curiously, most of them had the CPU locked exactly for 22 or 23 seconds), but for now there is no clear solution nor workaround...