[Qemu-devel] [PATCH 0/2] TPM NVRAM persistent storage
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 Thanks, Corey Corey Bryant (2): nvram: Add TPM NVRAM implementation nvram: Add tpm-tis drive support hw/tpm/Makefile.objs |1 + hw/tpm/tpm_int.h |2 + hw/tpm/tpm_nvram.c | 399 ++ hw/tpm/tpm_nvram.h | 25 +++ hw/tpm/tpm_tis.c |8 + 5 files changed, 435 insertions(+), 0 deletions(-) create mode 100644 hw/tpm/tpm_nvram.c create mode 100644 hw/tpm/tpm_nvram.h
Re: [Qemu-devel] [PATCH 0/2] TPM NVRAM persistent storage
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? Thanks, Corey Corey Bryant (2): nvram: Add TPM NVRAM implementation nvram: Add tpm-tis drive support hw/tpm/Makefile.objs |1 + hw/tpm/tpm_int.h |2 + hw/tpm/tpm_nvram.c | 399 ++ hw/tpm/tpm_nvram.h | 25 +++ hw/tpm/tpm_tis.c |8 + 5 files changed, 435 insertions(+), 0 deletions(-) create mode 100644 hw/tpm/tpm_nvram.c create mode 100644 hw/tpm/tpm_nvram.h -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: [Qemu-devel] [PATCH 0/2] TPM NVRAM persistent storage
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. (?) -- Regards, Corey Bryant Thanks, Corey Corey Bryant (2): nvram: Add TPM NVRAM implementation nvram: Add tpm-tis drive support hw/tpm/Makefile.objs |1 + hw/tpm/tpm_int.h |2 + hw/tpm/tpm_nvram.c | 399 ++ hw/tpm/tpm_nvram.h | 25 +++ hw/tpm/tpm_tis.c |8 + 5 files changed, 435 insertions(+), 0 deletions(-) create mode 100644 hw/tpm/tpm_nvram.c create mode 100644 hw/tpm/tpm_nvram.h
Re: [Qemu-devel] [PATCH 0/2] TPM NVRAM persistent storage
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
