Re: Partial success enabling TPM2 in an existing qemu guest VM

Ed Greshko writes: This is mostly intellectual curiousity, something to tinker with, and a learning experience. I learned about qcow2 snapshots by screwing around with this thing. They are very useful, without them it would be a mess. And I did learn that qemu is capable of booting Windows 10 in secure boot mode. When I pick this up again, in a month or two (unless I get a good lead, earlier) the first step would be to figure out how to create a new VM in virt-manager but preserve the data in the emulated TPM chip, to see if that makes Windows 10 survive the firmware transplant. I see that it's in a directory whose name is te VM's random UUID. So, what will it be? Copy the existing VM's TPM directory to the new VM when it gets created? virt-manager seems to automatically start the new VM after creating it, I don't really see a reason for this behavior, but I'd have to force-off the VM to get its UUID. I don't remember if I can edit the XML file in the custom installation mode, maybe I can cut/paste and create a VM with the same UUID, so that virt- manager-started swtpm ends up loading the same data?