Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-12-03 Thread Daniel P . Berrangé
On Fri, Nov 29, 2019 at 03:02:41PM +0100, Janosch Frank wrote: > On 11/29/19 1:35 PM, Daniel P. Berrangé wrote: > > Is there any way to prevent a guest from using protected mode even > > if QEMU supports it ? eg the mgmt app may want to be able to > > guarantee that all VMs are migratable, so

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-29 Thread Viktor Mihajlovski
On 11/29/19 3:02 PM, Janosch Frank wrote: [...] As a mgmt app I think there will be a need to be able to determine whether a host + QEMU combo is actually able to support protected machines. If the mgmt app is given an image and the users says it required protected mode, then the mgmt app

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-29 Thread Janosch Frank
On 11/29/19 1:35 PM, Daniel P. Berrangé wrote: > On Fri, Nov 29, 2019 at 01:14:27PM +0100, Janosch Frank wrote: >> On 11/29/19 12:08 PM, Daniel P. Berrangé wrote: >>> On Wed, Nov 20, 2019 at 06:43:19AM -0500, Janosch Frank wrote: Most of the QEMU changes for PV are related to the new IPL type

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-29 Thread Daniel P . Berrangé
On Fri, Nov 29, 2019 at 01:14:27PM +0100, Janosch Frank wrote: > On 11/29/19 12:08 PM, Daniel P. Berrangé wrote: > > On Wed, Nov 20, 2019 at 06:43:19AM -0500, Janosch Frank wrote: > >> Most of the QEMU changes for PV are related to the new IPL type with > >> subcodes 8 - 10 and the execution of

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-29 Thread Janosch Frank
On 11/29/19 12:08 PM, Daniel P. Berrangé wrote: > On Wed, Nov 20, 2019 at 06:43:19AM -0500, Janosch Frank wrote: >> Most of the QEMU changes for PV are related to the new IPL type with >> subcodes 8 - 10 and the execution of the necessary Ultravisor calls to >> IPL secure guests. Note that we can

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-29 Thread Daniel P . Berrangé
On Wed, Nov 20, 2019 at 06:43:19AM -0500, Janosch Frank wrote: > Most of the QEMU changes for PV are related to the new IPL type with > subcodes 8 - 10 and the execution of the necessary Ultravisor calls to > IPL secure guests. Note that we can only boot into secure mode from > normal mode, i.e.

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-21 Thread Cornelia Huck
On Thu, 21 Nov 2019 10:13:29 +0100 Janosch Frank wrote: > On 11/20/19 2:26 PM, Cornelia Huck wrote: > > On Wed, 20 Nov 2019 06:43:19 -0500 > > Janosch Frank wrote: > > > > Do you have a branch with this somewhere? > > Just for you: > https://github.com/frankjaa/qemu/tree/protvirt >

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-21 Thread Janosch Frank
On 11/20/19 2:26 PM, Cornelia Huck wrote: > On Wed, 20 Nov 2019 06:43:19 -0500 > Janosch Frank wrote: > > Do you have a branch with this somewhere? Just for you: https://github.com/frankjaa/qemu/tree/protvirt

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-20 Thread Janosch Frank
On 11/20/19 2:26 PM, Cornelia Huck wrote: > On Wed, 20 Nov 2019 06:43:19 -0500 > Janosch Frank wrote: > > Do you have a branch with this somewhere? > >> Most of the QEMU changes for PV are related to the new IPL type with >> subcodes 8 - 10 and the execution of the necessary Ultravisor calls to

Re: [PATCH 00/15] s390x: Protected Virtualization support

2019-11-20 Thread Cornelia Huck
On Wed, 20 Nov 2019 06:43:19 -0500 Janosch Frank wrote: Do you have a branch with this somewhere? > Most of the QEMU changes for PV are related to the new IPL type with > subcodes 8 - 10 and the execution of the necessary Ultravisor calls to > IPL secure guests. Note that we can only boot into

[PATCH 00/15] s390x: Protected Virtualization support

2019-11-20 Thread Janosch Frank
Most of the QEMU changes for PV are related to the new IPL type with subcodes 8 - 10 and the execution of the necessary Ultravisor calls to IPL secure guests. Note that we can only boot into secure mode from normal mode, i.e. stfle 161 is not active in secure mode. The other changes related to