Re: QEMU Advent Calendar 2022 Call for Images

2022-10-21 Thread Stefan Hajnoczi
On Fri, 21 Oct 2022 at 12:45, Eldon Stegall wrote: > We are working to make QEMU Advent Calendar 2022 happen this year, and > if you have had an interesting experience with QEMU recently, we would > love for you to contribute! Hi Eldon, Count me in for 1 disk image. I will find something cool

Re: [PATCH RFC v2 00/13] IOMMUFD Generic interface

2022-10-21 Thread Jason Gunthorpe
On Fri, Sep 23, 2022 at 11:40:51AM -0400, Laine Stump wrote: > It's been a few years, but my recollection is that before starting a > libvirtd that will run a guest with a vfio device, a privileged process > needs to > > 1) increase the locked memory limit for the user that will be running qemu >

QEMU Advent Calendar 2022 Call for Images

2022-10-21 Thread Eldon Stegall
Hi, We are working to make QEMU Advent Calendar 2022 happen this year, and if you have had an interesting experience with QEMU recently, we would love for you to contribute! QEMU invocations that showcase new functionality, something cool, bring back retro computing memories, or simply entertain

Re: [PATCH v3 0/6] qemu: tpm: Add support for migration across shared storage

2022-10-21 Thread Stefan Berger
On 10/21/22 06:55, Michal Prívozník wrote: On 10/18/22 19:04, Stefan Berger wrote: This series of patches adds support for migrating vTPMs across hosts whose storage has been set up to share the directory structure holding the state of the TPM (swtpm). The existence of share storage

Re: [PATCH 0/6] Implement XML validation feature for node devices and storage volumes

2022-10-21 Thread Jonathon Jongsma
On 10/20/22 9:37 AM, Peter Krempa wrote: In the last round of adding support for built-in validation the node device APIs and storage volume creation were not covered. Note that due to the close freeze date I've already marked the APIs for v8.10. Peter Krempa (6): conf: node_device: Add

Re: [PATCH v3 4/6] qemu: tpm: Pass --migration option to swtpm if supported and needed

2022-10-21 Thread Michal Prívozník
On 10/21/22 15:31, Michal Prívozník wrote: > On 10/21/22 13:36, Stefan Berger wrote: >> >> >> On 10/21/22 06:55, Michal Prívozník wrote: >>> On 10/18/22 19:04, Stefan Berger wrote: Pass the --migration option to swtpm if swptm supports it (starting with v0.8) and if the TPM's state is

Re: [PATCH v3 4/6] qemu: tpm: Pass --migration option to swtpm if supported and needed

2022-10-21 Thread Michal Prívozník
On 10/21/22 13:36, Stefan Berger wrote: > > > On 10/21/22 06:55, Michal Prívozník wrote: >> On 10/18/22 19:04, Stefan Berger wrote: >>> Pass the --migration option to swtpm if swptm supports it (starting >>> with v0.8) and if the TPM's state is written on shared storage. If this >>> is the case

Re: [PATCH v3 2/6] qemu: tpm: Conditionally create storage on incoming migration

2022-10-21 Thread Stefan Berger
On 10/21/22 06:55, Michal Prívozník wrote: On 10/18/22 19:04, Stefan Berger wrote: Do not create storage if the TPM state files are on shared storage and there's an incoming migration since in this case the storage directory must already exist. Also do not run swtpm_setup in this case.

Re: [libvirt PATCH 3/4] qemu: add external backend for tpm

2022-10-21 Thread Michal Prívozník
On 10/17/22 16:27, Ján Tomko wrote: > Introduce a new backend type 'external' for connecting to a swtpm daemon > not managed by libvirtd. > > Mostly in one commit, thanks to -Wswitch and the way we generate > capabilities. > > https://bugzilla.redhat.com/show_bug.cgi?id=2063723 > >

Re: [PATCH v3 4/6] qemu: tpm: Pass --migration option to swtpm if supported and needed

2022-10-21 Thread Stefan Berger
On 10/21/22 06:55, Michal Prívozník wrote: On 10/18/22 19:04, Stefan Berger wrote: Pass the --migration option to swtpm if swptm supports it (starting with v0.8) and if the TPM's state is written on shared storage. If this is the case apply the 'release-lock-outgoing' parameter with this

Re: [PATCH v3 2/6] qemu: tpm: Conditionally create storage on incoming migration

2022-10-21 Thread Michal Prívozník
On 10/18/22 19:04, Stefan Berger wrote: > Do not create storage if the TPM state files are on shared storage and > there's an incoming migration since in this case the storage directory > must already exist. Also do not run swtpm_setup in this case. > > Signed-off-by: Stefan Berger > --- >

Re: [PATCH v3 4/6] qemu: tpm: Pass --migration option to swtpm if supported and needed

2022-10-21 Thread Michal Prívozník
On 10/18/22 19:04, Stefan Berger wrote: > Pass the --migration option to swtpm if swptm supports it (starting > with v0.8) and if the TPM's state is written on shared storage. If this > is the case apply the 'release-lock-outgoing' parameter with this > option and apply the 'incoming' parameter

Re: [PATCH v3 3/6] qemu: tpm: Add support for storing private TPM-related data

2022-10-21 Thread Michal Prívozník
On 10/18/22 19:04, Stefan Berger wrote: > Add support for storing private TPM-related data. The first private data > will be related to the capability of the started swtpm indicating whether > it is capable of migration with a shared storage setup since that requires > support for certain command

Re: [PATCH v3 0/6] qemu: tpm: Add support for migration across shared storage

2022-10-21 Thread Michal Prívozník
On 10/18/22 19:04, Stefan Berger wrote: > This series of patches adds support for migrating vTPMs across hosts whose > storage has been set up to share the directory structure holding the state > of the TPM (swtpm). The existence of share storage influences the > management of the directory