From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dr. David Alan Gilbert" Subject: Re: [PATCH v5 23/23] sev: add migration blocker Date: Thu, 7 Dec 2017 11:27:29 +0000 Message-ID: <20171207112729.GC2439@work-vm> References: <20171206200346.116537-1-brijesh.singh@amd.com> <20171206200346.116537-24-brijesh.singh@amd.com> <20171207110342.GB2439@work-vm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Brijesh Singh , QEMU Developers , Alistair Francis , Christian Borntraeger , Cornelia Huck , "Daniel P . Berrange" , "Edgar E . Iglesias" , Eduardo Habkost , Eric Blake , kvm-devel , Marcel Apfelbaum , Markus Armbruster , "Michael S. Tsirkin" , Paolo Bonzini , Peter Crosthwaite , Richard Henderson , Richard Henderson , Stefan Hajnoczi , Thomas L To: Peter Maydell Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35734 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752802AbdLGL1q (ORCPT ); Thu, 7 Dec 2017 06:27:46 -0500 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: * Peter Maydell (peter.maydell@linaro.org) wrote: > On 7 December 2017 at 11:03, Dr. David Alan Gilbert wrote: > > * Brijesh Singh (brijesh.singh@amd.com) wrote: > >> SEV guest migration is not yet implemented yet. > > Is there at least a plan for how migration of a guest with > encrypted memory would be implemented? It's something I've discussed with Brijesh and co and I've read through the spec and it does look doable; I understand wanting to get the basics of SEV going first though. Dave > thanks > -- PMM -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40822) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMuLG-0003rX-Cj for qemu-devel@nongnu.org; Thu, 07 Dec 2017 06:27:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eMuLD-0006xb-7h for qemu-devel@nongnu.org; Thu, 07 Dec 2017 06:27:50 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47362) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eMuLD-0006xH-1f for qemu-devel@nongnu.org; Thu, 07 Dec 2017 06:27:47 -0500 Date: Thu, 7 Dec 2017 11:27:29 +0000 From: "Dr. David Alan Gilbert" Message-ID: <20171207112729.GC2439@work-vm> References: <20171206200346.116537-1-brijesh.singh@amd.com> <20171206200346.116537-24-brijesh.singh@amd.com> <20171207110342.GB2439@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v5 23/23] sev: add migration blocker List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Brijesh Singh , QEMU Developers , Alistair Francis , Christian Borntraeger , Cornelia Huck , "Daniel P . Berrange" , "Edgar E . Iglesias" , Eduardo Habkost , Eric Blake , kvm-devel , Marcel Apfelbaum , Markus Armbruster , "Michael S. Tsirkin" , Paolo Bonzini , Peter Crosthwaite , Richard Henderson , Richard Henderson , Stefan Hajnoczi , Thomas Lendacky , Borislav Petkov * Peter Maydell (peter.maydell@linaro.org) wrote: > On 7 December 2017 at 11:03, Dr. David Alan Gilbert wrote: > > * Brijesh Singh (brijesh.singh@amd.com) wrote: > >> SEV guest migration is not yet implemented yet. > > Is there at least a plan for how migration of a guest with > encrypted memory would be implemented? It's something I've discussed with Brijesh and co and I've read through the spec and it does look doable; I understand wanting to get the basics of SEV going first though. Dave > thanks > -- PMM -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK