Clone of virtual machine snapshot fails due to UEFI disk and TPM state

[Phips]

Good morning dear Proxmox community,

unfortunately I am facing an issue.
I have a Windows 11 machine with of course an EFI and a TPM disk.

I just tried to clone the latest snapshot via the GUI so that I can fiddle around without risking my running VM.
Unfortunately this clone fails with the error message:

Full clone feature is not supported for drive 'efidisk0' (500)

From time to time a similar message appears for the TPM.

In the meantime I tried the following to create a backup and restore this backup as a new VM. Unfortunately no snapshots are backed up.

I know that I could simply clone my current working setup and fiddle with the VM with the snapshots but I think this situation might be interesting.
(Also I would like to keep my running VM with the snapshots and not split it up.)

My host is running on PVE 8.2.7 and uses ZFS.

Thanks in advance and br
Phips

 

[bbgeek17]

Hi @Phips , welcome to the forum.

Making a full clone of a VM with EFI and TPM works for me:

Spoiler: direct VM clone

Task viewer: VM 9021 - Clone

create full clone of drive efidisk0 (blockbridge-iscsi:vm-9021-disk-0)
create full clone of drive scsi0 (blockbridge-iscsi:vm-9021-disk-1)
transferred 0.0 B of 32.0 GiB (0.00%)
..
transferred 32.0 GiB of 32.0 GiB (100.00%)
create full clone of drive scsi1 (blockbridge-iscsi:vm-9021-disk-2)
transferred 0.0 B of 32.0 GiB (0.00%)
..
transferred 32.0 GiB of 32.0 GiB (100.00%)
create full clone of drive tpmstate0 (blockbridge-iscsi:vm-9021-disk-3)
transferred 0.0 B of 4.0 MiB (0.00%)
..
transferred 4.0 MiB of 4.0 MiB (100.00%)
TASK OK

Spoiler: snapshot of the VM

Task viewer: VM 9021 - Snapshot
snapshotting 'drive-scsi0' (blockbridge-iscsi:vm-9021-disk-1)
snapshotting 'drive-scsi1' (blockbridge-iscsi:vm-9021-disk-2)
snapshotting 'drive-efidisk0' (blockbridge-iscsi:vm-9021-disk-0)
snapshotting 'drive-tpmstate0' (blockbridge-iscsi:vm-9021-disk-3)
TASK OK

Spoiler: full clone of a VM from snapshot

Task viewer: VM 9021 - Clone
create full clone of drive efidisk0 (blockbridge-iscsi:vm-9021-disk-0)
create full clone of drive scsi0 (blockbridge-iscsi:vm-9021-disk-1)
transferred 0.0 B of 32.0 GiB (0.00%)
...
transferred 32.0 GiB of 32.0 GiB (100.00%)
create full clone of drive scsi1 (blockbridge-iscsi:vm-9021-disk-2)
transferred 0.0 B of 32.0 GiB (0.00%)
...
transferred 32.0 GiB of 32.0 GiB (100.00%)
create full clone of drive tpmstate0 (blockbridge-iscsi:vm-9021-disk-3)
transferred 0.0 B of 4.0 MiB (0.00%)
..
transferred 4.0 MiB of 4.0 MiB (100.00%)
TASK OK

Perhaps you can share your VM configuration, full output of the pveversion -v, storage configuration (cat /etc/pve/storage.cfg), exact output of the task result, repeat the command from CLI as its easier to demonstrate the objects you are operating on than in GUI, snippet of the journalctl that contains task details/work.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Phips]

Thanks for the answer and the welcome @bbgeek17

Spoiler: pveversion -v

proxmox-ve: 8.2.0 (running kernel: 6.5.13-3-pve)
pve-manager: 8.2.8 (running version: 8.2.8/a577cfa684c7476d)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
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.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.8
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.11
libpve-storage-perl: 8.2.6
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.5.0-1
proxmox-backup-client: 3.2.8-1
proxmox-backup-file-restore: 3.2.8-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.0
pve-cluster: 8.0.8
pve-container: 5.2.1
pve-docs: 8.2.4
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.14-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

Spoiler: cat /etc/pve/storage.cfg

dir: local
path /var/lib/vz
content vztmpl,iso,backup
shared 0

zfspool: local-zfs
pool rpool/data
content images,rootdir
sparse 1

zfspool: local-zfs-02
pool local-zfs-02
content images,rootdir
mountpoint /local-zfs-02
nodes pve

In the meantime I temporary helped myself with zfs send and zfs receive.

1. Checked the snapshots with zfs list -t snapshot.
2. Cloned the snapshot via zfs send and zfs receive (repeated for every disk; example: zfs send rpool/data/vm-1000-disk-0@snapshot1 | zfs receive -F rpool/data/vm-1001-disk-0
3. Cloned and edited the .conf file of the original VM in /etc/pve/qemu-server

But I don't see this as a good solution.

As you asked for it I tried to clone directly from the CLI via qm clone 1000 1010 --name clonetest which does not take the snapshots to the clone. (like expected)
So I tried to clone with the following option --snapname snapshot1 in addition to the previous command.
qm clone 1000 1010 --name clonetest --snapname snapshot1 results in Full clone feature is not supported for drive 'tpmstate0'
VM is stopped during the whole process.

Thanks and br,
Phips

 

[Phips]

To precise it a bit more (maybe I did not do in the initial post): I am trying to clone a snapshot of the VM and not the current state.

Thanks and br,
Phips

 

[fiona]

For reference: https://bugzilla.proxmox.com/show_bug.cgi?id=2805