Linked clone windows 11 cannot be cloned to a new VM

[abarakat]

I have a linked clone VM that I want to clone to another VM but this fails. Any work arounds?

I am pretty sure this has soemthing to do with the EFI/TPM disks Win11 requires. They show as qcows2 but are actually raw

TASK ERROR: clone failed: copy failed: command '/usr/bin/qemu-img convert -p -n -f qcow2 -O raw /mnt/pve/pvevm/images/120/vm-120-disk-2.qcow2 zeroinit:/mnt/pve/pvevm/images/367/vm-367-disk-0.raw' failed: exit code 1

 

[fiona]

Hi,

I have a linked clone VM that I want to clone to another VM but this fails. Any work arounds?

I am pretty sure this has soemthing to do with the EFI/TPM disks Win11 requires. They show as qcows2 but are actually raw

yes, there was a bug over a year ago, where you could wrongly end up with a TPM drive with a qcow2 extension: https://git.proxmox.com/?p=qemu-server.git;a=commit;h=5f5aba2578e117247ec8ae5fcd925d3e19cba5c0 But the EFI disk can be qcow2, that's supported and not an issue.

TASK ERROR: clone failed: copy failed: command '/usr/bin/qemu-img convert -p -n -f qcow2 -O raw /mnt/pve/pvevm/images/120/vm-120-disk-2.qcow2 zeroinit:/mnt/pve/pvevm/images/367/vm-367-disk-0.raw' failed: exit code 1

Is /mnt/pve/pvevm/images/120/vm-120-disk-2.qcow2 the TPM disk? Best to have a tested backup before attempting it, but it might be enough to just rename it with a .raw extension and update the VM configuration accordingly.

Can you post the output of pveversion -v and qm config 120 --current?

 

[abarakat]

root@:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.4-3
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.6
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-2
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1


qm config 120 --current
agent: 1
bios: ovmf
boot: order=ide0;ide2;net0
cores: 4
efidisk0: pvevm:20000/base-20000-disk-0.qcow2/120/vm-120-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: pvevm:20000/base-20000-disk-1.qcow2/120/vm-120-disk-1.qcow2,size=100G
ide2: none,media=cdrom
machine: pc-q35-7.1
memory: 8192
meta: creation-qemu=7.1.0,ctime=1675378082
name: fswin11-test01
net0: virtio=6E:32:67:F4:BD:84,bridge=vmbr3,tag=118
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=b5190788-b0c6-484e-888a-ce6c47834cc5
sockets: 1
tpmstate0: pvevm:20000/base-20000-disk-0.raw/120/vm-120-disk-2.qcow2,size=16896,version=v2.0
vmgenid: 667d906b-59dd-4e59-be0f-40bb84547664