Update & workaround : The issue occurs with Proxmox when using the default cpu type (vm64). Setting the VM cpu type to “host” fixes the problem.
Thankfully found this from thread:
Update & workaround : The issue occurs with Proxmox when using the default cpu type (vm64). Setting the VM cpu type to “host” fixes the problem.
Thankfully found this from thread: