[SOLVED] GUI VM Snapshot button grayed after last upgrade

[j2m06]

Hello

After today PVE upgrade (on a PVE test server), looks like it's now impossible to take a VM snaphot on the GUI :

- From the GUI VM snapshot menu, the top snapshot button is now grayed
- A text "The current guest configuration does not support taking new snapshots" is displayed close to the snapshot button row

After some quick checks :

- All existing VMs prior to update still have an operationnal snapshot button,
- All freshly restored (new or overwritten) from a PBS server VMs have now a grayed button and the configuration warning message.

Thanks

PVE server (test) :

proxmox-ve: 8.2.0 (running kernel: 6.8.8-2-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.8-2
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 18.2.2-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.3
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.4-1
proxmox-backup-file-restore: 3.2.4-1
proxmox-firewall: 0.4.2
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.12-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.0-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

PBS Server (production) :

proxmox-backup: 3.2.0 (running kernel: 6.8.8-2-pve)
proxmox-backup-server: 3.2.6-1 (running version: 3.2.6)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.8-2
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
proxmox-kernel-6.8.8-1-pve-signed: 6.8.8-1
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5: 6.5.13-5
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ifupdown2: 3.2.0-1+pmx8
libjs-extjs: 7.0.0-4
proxmox-backup-docs: 3.2.6-1
proxmox-backup-client: 3.2.6-1
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: not correctly installed
proxmox-widget-toolkit: 4.2.3
pve-xtermjs: 5.3.0-3
smartmontools: 7.3-pve1
zfsutils-linux: 2.2.4-pve1

 

[intrax]

That depends on the file system storage you have selected...

 

[j2m06]

Precision : all VMs are on the same FS, qcow2 on ext4 (very simple test server)
May be a link with this problem : https://forum.proxmox.com/threads/p...ion-2024-06-27-using-pve-qemu-kvm-8-2.149883/

 

[j2m06]

Sorry guys, I apologize, was my fault.
The restore from PBS recreate a "raw" disk, and not a qcow2 one (orignal backuped VM was "raw").
We definitely need a format choice option on the restore box to avoid this recurrent mistake.
Thanks for the indication to take a look at the storage.

 

[intrax]

Sorry guys, I apologize, was my fault.
The restore from PBS recreate a "raw" disk, and not a qcow2 one (orignal backuped VM was "raw").
We definitely need a format choice option on the restore box to avoid this recurrent mistake.
Thanks for the indication to take a look at the storage.

See wrong storage ff !