centos 7 guest with QEMU agent freezing

Hmm ... I run a similar setups yet have not encountered any problem.

Can you describe your system and since when this problem occurs?
 
root@proxmox3:~# qm config 169
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 4
efidisk0: NVMe:vm-169-disk-0,efitype=4m,pre-enrolled-keys=1,size=528K
ide2: none,media=cdrom
memory: 8096
meta: creation-qemu=6.1.0,ctime=1649423345
name: GV-WHM
net0: virtio=52:65:E2:84:94:EF,bridge=vmbr0,tag=109
numa: 0
ostype: l26
parent: removeGuestAgent
scsi0: NVMe:vm-169-disk-1,size=580G
scsihw: virtio-scsi-pci
smbios1: uuid=2562f677-6809-4e62-af56-1011ce30e2dd
sockets: 1
vmgenid: 949f3a42-867e-4421-a540-e99d20371d84

Virtual Environment 7.2-7
Backup Server 2.2-7

It started ever since I enabled the guest agent on this VM
This is what cPanel said:

Hello,

Thank you for your update. I was able to successfully access the server. I noticed there is a gap in the server logs between roughly 4AM and 10AM server time. I also noticed the following entries in /var/log/messages that appear to be happening directly before each crash:

[11:15:47 server01 root@94536889 ~]cPs# grep fsfreeze /var/log/messagesstyle='font-family:Consolas;color:#2B2E2F;background:#F8F8F8'>

Feb 26 08:47:01 server01 qemu-ga: info: guest-fsfreeze called

Feb 26 08:47:01 server01 qemu-ga: info: executing fsfreeze hook with arg 'freeze'

Mar 1 08:33:07 server01 qemu-ga: info: guest-fsfreeze called

Mar 1 08:33:07 server01 qemu-ga: info: executing fsfreeze hook with arg 'freeze'

Mar 2 06:42:29 server01 qemu-ga: info: guest-fsfreeze called

Mar 2 06:42:29 server01 qemu-ga: info: executing fsfreeze hook with arg 'freeze'style='color:#2B2E2F'>

Although this doesn't appear to be related to or caused by cPanel, it appears that another user has opened a bug report regarding a similar issue:

https://gitlab.com/qemu-project/qemu/-/issues/520

In short, it appears that the qemu agent could be causing the kernel to crash when it executes 'fsfreeze'. I would recommend working with your system administrator to temporarily disable this package/function to see if it resolves the issue. Since this package is not managed or developed by cPanel, we would be unable to disable it from our side.
 
Yes, according to the bug report, there are only a few software products in a special setup affected. So you canot pin-point it to a special PVE version.