From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: PAE requirement in config file for HVM guests
Date: Wed, 22 Nov 2006 09:36:49 +0100
Message-ID: <45641A31.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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