Hi everyone,

I wanted to post an update.

We have successfully upgraded to Proxmox VE 9.2.3, which also updated the PVE host kernel, QEMU-related packages, guest agent components, and everything involved.

At first, we thought the problem had been resolved, but it turns out that it has not. The issue still persists.

I noticed that when I migrate a VM to a datastore that does not have the “Allow Snapshots as Volume-Chain” checkbox enabled, snapshots initially seem to work correctly without freezing the VM.

This led me to mistakenly believe that everything was working fine after the update, because the process of creating and deleting the snapshot took only a few seconds and only caused the loss of 1–2 pings, without leaving the VM frozen.

However, after keeping the VM on that datastore for several days, we ran the same test again and the problem appeared again. The VM becomes inoperable / frozen for the duration of the snapshot process. The same thing happens when the snapshot is deleted.

This also happens even when the VM has no workload.

Has anyone else encountered this problem? Has anyone found a solution?

How is Proxmox typically set up in home lab and production environments?

I think our problem may come from running VMs over NFS. Maybe there are fewer issues when VMs are stored on:

• Local disks with ZFS
• ZFS-based storage
• Proxmox hyperconverged infrastructure / HCI with Ceph

But of course, if you have a NetApp, HPE, IBM, Hitachi, or similar storage array with NFS datastores, without “Allow Snapshots as Volume-Chain” as still inpreview, what options or solutions are available?