On 06/04/2013 01:35 PM, Corey Bryant wrote: > > > On 06/04/2013 03:23 PM, Eric Blake wrote: >> On 06/04/2013 12:18 PM, Corey Bryant wrote: >>> This patch series provides persistent storage support that a TPM >> can use to store NVRAM data. It uses QEMU's block driver to store >>> data on a drive image. The libtpms TPM 1.2 backend will be the >>> initial user of this functionality to store data that must persist >>> through a reboot or migration. A sample command line may look like >>> this: >>> >>> qemu-system-x86_64 ... >>> -drive file=/path/to/nvram.qcow2,id=drive-nvram0-0-0 >>> -tpmdev libtpms,id=tpm-tpm0 >>> -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0,drive=drive-nvram0-0-0 >> >> Is a TPM device hot-pluggable? If so, do you have a design for the QMP >> counterpart in mind? >> > > Well the TPM is not hot-pluggable. And the feedback we've been getting > is to simplify this support so I'm not sure it's needed/wanted. (?)
Fair enough - just making sure we aren't forgetting something where it makes sense, but I agree with your point that for TPM, hot-plug does NOT make sense :) -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature