WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] PAE requirement in config file for HVM guests

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] PAE requirement in config file for HVM guests
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 22 Nov 2006 09:36:49 +0100
Delivery-date: Wed, 22 Nov 2006 00:34:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Could anyone explain why it was necessary in 3.0.3 to require config files
for 32-bit/PAE or 64-bit x86 hvm guests on respective hypervisors to have
an explicit 'pae = 1', whereas in 3.0.2 this wasn't needed? It would seem
that the emulated CPUID feature flag should, as in 3.0.2, just be
suppressed if the hypervisor really can't support PAE (i.e. 32-bit non-PAE
build).

Thanks, Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>