Proxmox VM TPM not starting after Upgrade 8 to 9.1.2

[michi--]

Hello,

I used in Proxmox 8.x a Linked Clone VM with Windows Server 2025 and TPM. The .conf file was created when I setup the VM in Proxmox 8.x

bios: ovmf
boot: order=ide0;ide2;net0
cores: 1
cpu: x86-64-v2-AES
efidisk0: local:101/base-101-disk-0.qcow2/100/vm-100-disk-0.qcow2,efitype=4m,ms-cert=2023,pre-enrolled-keys=1,size=528K
ide0: local:101/base-101-disk-1.qcow2/100/vm-100-disk-1.qcow2,size=60G
ide2: none,media=cdrom
machine: pc-q35-9.0
memory: 4096
meta: creation-qemu=9.0.2,ctime=1727186226
name: server2022-man
net0: e1000=BC:24:11:99:C9:74,bridge=vmbr0
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=d28447cb-49f9-4ef7-b209-8e75de262987
sockets: 1
tpmstate0: local:101/base-101-disk-2.raw/100/vm-100-disk-2.qcow2,size=16896,version=v2.0
vmgenid: 51455b5e-d2cc-46f7-bcd3-11d76103b504




Now when I want to start the virtual machine I will receive an error in Proxmox 9.1.2

TASK ERROR: start failed: adding blockdev 'drive-tpmstate0' failed : QEMU storage daemon 100 qsd command 'blockdev-add' failed - Image is not in qcow2 format


When I am making a new linked clone in Proxmox 9.1.2 the vm is started, but not my old virtual machine after the upgrade to Proxmox 9.1.2. Do you have any hints?

Thanks and best regards
Michi

 

[fireon]

If you delete the TPM and recreate it, it should be QCOW2.

 

[fabian]

could you file an issue in our bugzilla? please include "pveversion -v", the config and the task log! this should be possible to fix..

recreating the TPM state is an option, but it will possibly require recovering bitlocker inside the VM using recovery codes, so it is a bit dangerous.

 

[michi--]

I posted it on bugzilla - https://bugzilla.proxmox.com/show_bug.cgi?id=7178
Thanks.