Snapshot failed - guest configuration does not support taking new snapshots.

[gplindstrom]

Describe the bug

Pegaprox pretends like it can do a snapshot, when a snapshot is prevented due to the config of the VM.

Steps to Reproduce

I have a vm that I pass a raw disk to. Proxmox says that "The current guest configuration does not support taking new snapshots". But PegaProx goes ahead and lets me try. It fails of course. Maybe that is good enough to just say it failed? But the first time I did it, I didn't see the message in the lower corner because it cleared.

Expected behavior

Shouldn't be able to do it. Perhaps a message that says it is not available due to configuration.

Environment

• PegaProx Version: 0.9.12.3
• Proxmox: 9.2.3 and 8.4.19

This isn't a big deal, but maybe should be addressed for compleness?

[mkellermann97]

Appreciate the clear write-up — and you've basically pinned the constraint yourself. Whether a VM can be snapshotted depends on its full disk config (a passed-through raw disk being the classic blocker), and Proxmox doesn't expose any API to ask "is a snapshot allowed here?" up front — it only evaluates that when the snapshot is actually fired. So there's nothing we can query to grey the action out in advance; the honest behaviour is what you're seeing — let the attempt run and surface PVE's reason when it refuses. If Proxmox ever adds a capability hint to the VM/config API, we'll wire it straight into the UI, but until then a pre-check would just be us second-guessing rules PVE keeps to itself. Closing as a Proxmox API limitation rather than something we can fix on our side — the failure does get reported, even if that toast cleared too fast to catch the first time. opencollective.com/pegaprox if PegaProx is doing right by you. — Marcus