Fabian Grünbichler fd95d780a2 migrate: send updated TPM state volid to target node ... The volid may change if local-storage migration is involved, we need to tell the target node the new one and update the in-memory config for starting the target VM accordingly. Reported here: https://forum.proxmox.com/threads/99906/#post-431345 this possibly breaks migration new -> old iff - spice is not used (else the explicit ticket wins because it comes later) - a local TPM state volume is used - that local TPM state volume has a different volume id on the target node (switched storage, volname already taken, ..) because the target node will then mis-interpret the tpmstate0 line as spice ticket and set it accordingly. if the old tpm state volume ID does not exist on the target node, migration will fail. if it exists by chance, it might work albeit with a wrong spice ticket (new because of this patch) and tpm state volume (pre-existing breakage). Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>		2021-11-22 16:55:17 +01:00
..
Qemu	api: machine list: parse as JSON	2021-03-05 16:33:08 +01:00
Makefile	buildsys: use $(MAKE) instead of make	2019-09-24 18:06:16 +02:00
Qemu.pm	migrate: send updated TPM state volid to target node	2021-11-22 16:55:17 +01:00