From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Nested SVM and migration Date: Mon, 22 Feb 2010 18:44:35 +0200 Message-ID: <4B82B473.4010906@redhat.com> References: <4B80347E.7000003@redhat.com> <20100220201822.GG20833@8bytes.org> <4B806FB9.20009@redhat.com> <20100221121008.GI20833@8bytes.org> <4B8125E2.8050309@redhat.com> <4B82B411.7020907@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Joerg Roedel , Joerg Roedel , kvm To: Zachary Amsden Return-path: Received: from mx1.redhat.com ([209.132.183.28]:64721 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752060Ab0BVQoj (ORCPT ); Mon, 22 Feb 2010 11:44:39 -0500 In-Reply-To: <4B82B411.7020907@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/22/2010 06:42 PM, Zachary Amsden wrote: > On 02/21/2010 02:24 AM, Avi Kivity wrote: >> On 02/21/2010 02:10 PM, Joerg Roedel wrote: >> >>> It is doable but I still think its >>> complicated to get this right. The simplest approach would be to >>> disallow migration when the vcpu is running in guest mode. >> >> Agree, though I dislike the need to introduce a "force vmexit" ioctl. >> > > How can this possibly work for guests which never exit SVM? They can > never be migrated. The force vmexit would generate an INTR #vmexit even if the INTR intercept was disabled and even if no INTR is pending. However this was shot down since there was no equivalent vmx exit reason that we can except the guest to reasonably handle. -- error compiling committee.c: too many arguments to function