This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 01/14] Nested Virtualization: tools

To: "Dong, Eddie" <eddie.dong@xxxxxxxxx>, Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 01/14] Nested Virtualization: tools
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 17 Aug 2010 08:35:29 +0100
Delivery-date: Tue, 17 Aug 2010 00:36:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1A42CE6F5F474C41B63392A5F80372B2291436C6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acs9129JB24JYVk+QnyfzYyA5UN+ggAAKvOgAAGqOOc=
Thread-topic: [Xen-devel] [PATCH 01/14] Nested Virtualization: tools
User-agent: Microsoft-Entourage/
On 17/08/2010 08:19, "Dong, Eddie" <eddie.dong@xxxxxxxxx> wrote:

>>      xc_get_hvm_param(xch, domid, HVM_PARAM_PAE_ENABLED, &pae);
>>      is_pae = !!pae;
>> +    xc_get_hvm_param(xch, domid, HVM_PARAM_NESTEDHVM, &nestedhvm);
> If you insist to support cross vendor nested virtualization, I would like to
> suggest we have multiple options for configuration: VMX, SVM, or HW.
> VMX and SVM option is for what situation that the user want to enforce the
> guest VMX/SVM features regardless of underlying hardware, while HW means to
> implements same with underlying virtualization feature in guest. In this way,
> it provides room for either cross vendor nested virtualization or natively
> virtualization.

We don't want cross-vendor nested virt, ever. So a simple boolean is fine

 -- Keir

Xen-devel mailing list