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

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>
[Xen-devel] PAE requirement in config file for HVM guests, Jan Beulich <= Re: [Xen-devel] PAE requirement in config file for HVM guests, Keir Fraser

Previous by Date:

RE: [Xen-devel][RFC]degradation on IPF due to hypercall set irq, Xu, Anthony

Next by Date:

[Xen-devel] VMX check_for_null_selector(), Jan Beulich

Previous by Thread:

[Xen-devel] [PATCH 00/04] Kexec / Kdump: Release 20061122 (xen-unstable-12502), Magnus Damm

Next by Thread:

Re: [Xen-devel] PAE requirement in config file for HVM guests, Keir Fraser

Indexes:

[Date] [Thread] [Top] [All Lists]