From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Nested VMX support v3 Date: Tue, 20 Oct 2009 12:30:34 +0900 Message-ID: <4ADD2EDA.7060700@redhat.com> References: <1255617706-13564-1-git-send-email-oritw@il.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, benami@il.ibm.com, abelg@il.ibm.com, muli@il.ibm.com, aliguori@us.ibm.com, mdday@us.ibm.com To: oritw@il.ibm.com Return-path: Received: from mx1.redhat.com ([209.132.183.28]:6668 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753693AbZJTDas (ORCPT ); Mon, 19 Oct 2009 23:30:48 -0400 In-Reply-To: <1255617706-13564-1-git-send-email-oritw@il.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/15/2009 11:41 PM, oritw@il.ibm.com wrote: > Avi, > We have addressed all of the comments, please apply. > > The following patches implement nested VMX support. The patches enable a guest > to use the VMX APIs in order to run its own nested guest (i.e., enable running > other hypervisors which use VMX under KVM). The current patches support running > Linux under a nested KVM using shadow page table (with bypass_guest_pf > disabled). SMP support was fixed. Reworking EPT support to mesh cleanly with > the current shadow paging design per Avi's comments is a work-in-progress. > Why is bypass_guest_pf disabled? > The current patches only support a single nested hypervisor, which can only run > a single guest (multiple guests are work in progress). Only 64-bit nested > hypervisors are supported. > Multiple guests and 32-bit support are merge requirements. As far as I can tell there shouldn't be anything special required to support them? > vpid allocation will be updated with the multiguest support (work in progress). > We are working on fixing the cr0.TS handling, it works for nested kvm by not > for vmware server. > Please either drop or fix vpid before merging. What's wrong with cr0.ts? I'd like to see that fixed as well. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.