Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-29 Thread Anthony Liguori
Corey Bryant cor...@linux.vnet.ibm.com writes: On 05/23/2013 03:15 PM, Anthony Liguori wrote: Corey Bryant cor...@linux.vnet.ibm.com writes: On 05/23/2013 02:03 PM, Anthony Liguori wrote: Corey Bryant cor...@linux.vnet.ibm.com writes: One of the difficulties in virtualizing a TPM is that

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-27 Thread Stefan Hajnoczi
On Fri, May 24, 2013 at 11:39:09AM -0400, Corey Bryant wrote: On 05/24/2013 08:36 AM, Stefan Hajnoczi wrote: On Fri, May 24, 2013 at 08:13:27AM -0400, Stefan Berger wrote: On 05/24/2013 05:59 AM, Stefan Hajnoczi wrote: On Thu, May 23, 2013 at 01:44:40PM -0400, Corey Bryant wrote: This

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-24 Thread Stefan Hajnoczi
On Thu, May 23, 2013 at 01:44:40PM -0400, Corey Bryant wrote: This patch series provides VNVRAM persistent storage support that QEMU can use internally. The initial target user will be a software vTPM 1.2 backend that needs to store keys in VNVRAM and be able to reboot/migrate and retain the

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-24 Thread Stefan Berger
On 05/24/2013 05:59 AM, Stefan Hajnoczi wrote: On Thu, May 23, 2013 at 01:44:40PM -0400, Corey Bryant wrote: This patch series provides VNVRAM persistent storage support that QEMU can use internally. The initial target user will be a software vTPM 1.2 backend that needs to store keys in VNVRAM

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-24 Thread Stefan Hajnoczi
On Fri, May 24, 2013 at 08:13:27AM -0400, Stefan Berger wrote: On 05/24/2013 05:59 AM, Stefan Hajnoczi wrote: On Thu, May 23, 2013 at 01:44:40PM -0400, Corey Bryant wrote: This patch series provides VNVRAM persistent storage support that QEMU can use internally. The initial target user will

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-24 Thread Corey Bryant
On 05/23/2013 03:15 PM, Anthony Liguori wrote: Corey Bryant cor...@linux.vnet.ibm.com writes: On 05/23/2013 02:03 PM, Anthony Liguori wrote: Corey Bryant cor...@linux.vnet.ibm.com writes: One of the difficulties in virtualizing a TPM is that it doesn't support SR-IOV. So the existing

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-24 Thread Corey Bryant
On 05/24/2013 08:36 AM, Stefan Hajnoczi wrote: On Fri, May 24, 2013 at 08:13:27AM -0400, Stefan Berger wrote: On 05/24/2013 05:59 AM, Stefan Hajnoczi wrote: On Thu, May 23, 2013 at 01:44:40PM -0400, Corey Bryant wrote: This patch series provides VNVRAM persistent storage support that QEMU

[Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-23 Thread Corey Bryant
This patch series provides VNVRAM persistent storage support that QEMU can use internally. The initial target user will be a software vTPM 1.2 backend that needs to store keys in VNVRAM and be able to reboot/migrate and retain the keys. This support uses QEMU's block driver to provide persistent

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-23 Thread Anthony Liguori
Corey Bryant cor...@linux.vnet.ibm.com writes: This patch series provides VNVRAM persistent storage support that QEMU can use internally. The initial target user will be a software vTPM 1.2 backend that needs to store keys in VNVRAM and be able to reboot/migrate and retain the keys. This

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-23 Thread Corey Bryant
On 05/23/2013 02:03 PM, Anthony Liguori wrote: Corey Bryant cor...@linux.vnet.ibm.com writes: This patch series provides VNVRAM persistent storage support that QEMU can use internally. The initial target user will be a software vTPM 1.2 backend that needs to store keys in VNVRAM and be able

Re: [Qemu-devel] [PATCH 0/7] VNVRAM persistent storage

2013-05-23 Thread Anthony Liguori
Corey Bryant cor...@linux.vnet.ibm.com writes: On 05/23/2013 02:03 PM, Anthony Liguori wrote: Corey Bryant cor...@linux.vnet.ibm.com writes: One of the difficulties in virtualizing a TPM is that it doesn't support SR-IOV. So the existing passthrough vTPM can only be used by one guest.