tpmstate0: property is not defined in schema and the schema does not allow additional properties

[David Herselman]

Hi,

We have a PVE7 + Ceph Pacific cluster with enterprise subscription where we have set one of the cluster nodes to the no-subscription repository to see the new options for vTPM support.

When attempting to add TPM state we receive the following error:


tpmstate0: property is not defined in schema and the schema does not allow additional properties

[admin@kvm1d ~]# cat /etc/pve/nodes/kvm1b/qemu-server/122.conf
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 1
cpu: SandyBridge,flags=+pcid
ide2: none,media=cdrom
localtime: 1
machine: pc-q35-6.0
memory: 4096
name: lair-temp
net0: virtio=00:11:22:33:44:55,bridge=vmbr0,tag=1
numa: 1
ostype: win10
protection: 1
scsi0: rbd_hdd:vm-122-disk-0,cache=writeback,discard=on,size=80G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=5e5039e1-7555-4b25-a84b-add2e52b29c4
sockets: 2

Same error when attempting to add EFI Disk.

 

[t.lamprecht]

Hi,

We have a PVE7 + Ceph Pacific cluster with enterprise subscription where we have set one of the cluster nodes to the no-subscription repository to see the new options for vTPM support.

I mean what do you expect? You use different software versions where the GUI that you loaded (from a new pve-manager version on that node due to no-subscription) exposes a feature that the node with the VM were your operating on, does not support yet (due to older pve-enterprise provided qemu-server package).

That cannot work, each node on a cluster needs to have the same package versions, at least if you do not want to run into such and other errors. Note that migrations from new -> old is not supported either, so with such a setup you need to always take special care.

 

[David Herselman]

Logical, I'll move the VM to the one node running the new components.

There is alot of interest around win 11 and server 2022, had wanted to start creating sysprep templates in preparation for vTPM being official...

Had noticed swtpm having been installed on the enterprise subscription nodes so incorrectly presumed backend already had support and that the UI would update once those changes were marked as stable...

 

[t.lamprecht]

There is alot of interest around win 11 and server 2022, had wanted to start creating sysprep templates in preparation for vTPM being official...

Understandable, fwiw, we got rather good feedback here in the forum.

Had noticed swtpm having been installed on the enterprise subscription nodes so incorrectly presumed backend already had support and that the UI would update once those changes were marked as stable...

Just for clarity: only the qemu-server version that actually supports adding tpmstate is pulling in the swtpm packages as new dependency...