Intermittent Windows 10 VM Freezing during WHMCS/Proxmox Addon Cloning (PVE 9.1.1)

[DolPhinSon]

Hi all,
I am experiencing a recurring and frustrating issue with Windows 10 VMs (both Pro and Enterprise editions) when deploying them via the WHMCS Proxmox Addon.

The Setup:

• Proxmox Version: pve-manager/9.1.1/42db4a6cf33dac83 (Running kernel: 6.17.2-1-pve)
• OS: Windows 10 (Pro/Enterprise)
• Template Status: Sysprep has been successfully completed on the gold image.
• Deployment Method: Cloned via WHMCS Proxmox Addon API.

Out of every 10 VMs cloned from the same template, about 1 or 2 VMs consistently fail. These VMs get stuck/frozen during the initial boot-up process (as shown in the attached screenshots). Once this freeze occurs, the VM becomes unusable, and a complete re-installation is the only way to recover.

We previously used Proxmox 8.3, and this issue was extremely rare. Since upgrading to PVE 9.1.1, the failure rate has increased significantly to roughly 10-20% of all clones.

 

[DolPhinSon]

New Observation:

This freezing issue is not limited to Windows 10. After further testing, we are seeing the exact same intermittent freezing across some Windows versions (Windows Server 2016, Server 2019/2022) when deployed via the WHMCS Proxmox Addon



Specific log on the host node

```

UPID:vnpttt-ssd-e5v4-s207:00085B9F:34D14C61:69CDEEF8:qmstart:207109:root@pam: 69CDEEFE OK

UPID:vnpttt-ssd-e5v4-s207:00085D3E:34D151CC:69CDEF05:qmstart:207109:root@pam: 69CDEF05 VM 207109 already running

UPID:vnpttt-ssd-e5v4-s207:000861D4:34D16CDA:69CDEF4B:qmreboot:207109:root@pam: 69CDEF8A VM quit/powerdown failed - got timeout

```

System-wide Hang: When the freeze occurs, the VM becomes completely unresponsive to ACPI signals. The fact that Proxmox hits a "timeout" trying to power down or reboot the VM suggests that the QEMU process itself is stuck at the kernel level.



#pveversion -v | grep qemu

libproxmox-backup-qemu0: 2.0.1

pve-qemu-kvm: 10.1.2-3

qemu-server: 9.0.30