From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: PAE requirement in config file for HVM guests Date: Wed, 22 Nov 2006 09:47:35 +0000 Message-ID: References: <45641A31.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45641A31.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 22/11/06 08:36, "Jan Beulich" wrote: > 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). It's only to allow pae to be masked off. I think that you can specify pae=1 always and it won't be advertised to the guest if the host doesn't support it. If this isn't the case it should be, and I'd take a patch to make it so. :-) Oh, and xend should default pae=1 if it doesn't do so already. -- Keir