* Singh, Brijesh (brijesh.si...@amd.com) wrote: > The LAUNCH_START is used for creating an encryption context to encrypt > newly created guest, for an incoming guest the RECEIVE_START should be > used. > > Signed-off-by: Brijesh Singh <brijesh.si...@amd.com>
Reviewed-by: Dr. David Alan Gilbert <dgilb...@redhat.com> > --- > target/i386/sev.c | 14 ++++++++++---- > 1 file changed, 10 insertions(+), 4 deletions(-) > > diff --git a/target/i386/sev.c b/target/i386/sev.c > index 6dbdc3cdf1..49baf8fef0 100644 > --- a/target/i386/sev.c > +++ b/target/i386/sev.c > @@ -789,10 +789,16 @@ sev_guest_init(const char *id) > goto err; > } > > - ret = sev_launch_start(s); > - if (ret) { > - error_report("%s: failed to create encryption context", __func__); > - goto err; > + /* > + * The LAUNCH context is used for new guest, if its an incoming guest > + * then RECEIVE context will be created after the connection is > established. > + */ > + if (!runstate_check(RUN_STATE_INMIGRATE)) { > + ret = sev_launch_start(s); > + if (ret) { > + error_report("%s: failed to create encryption context", > __func__); > + goto err; > + } > } > > ram_block_notifier_add(&sev_ram_notifier); > -- > 2.17.1 > -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK