Red Hat Bugzilla – Bug 213211
kernel-2.6.18-1.2798.fc6xen poor diagnostics on non-PAE hw
Last modified: 2007-11-30 17:11:47 EST
Description of problem:
booting into kernel-2.6.18-1.2798.fc6xen results into a kenrel panic...
messages flowing by too quick.
HW is IBM T42p with PentiumM 2.10GHz 1GB RAM
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot into this kernel
book kernel and allow creation of domU's
I guess it's a lack of PAE support in the Pentium M chip problem.
We now compile xen and associated kernel with PAE support, as a result
the hypervisor will fail and rebbot after emitting the error message,
try to check if you can spot "PAE" before the reboot, but I'm pretty
sure it's the problem.
yup, you are right I in fact can spot this:
can not execute a PAE-enabled Kernel
Surely this will be the pain of more users and later RHEL users...
Are there any easy workarounds? Or plans to have an additional kernel w/o PAE
and Xen enabled?
In RHEL, the anaconda installer will not provide users the option of installing
virtualization if they don't have PAE capable hardware, so you won't see this
problem for initial installs. Of course they can manually install the kernel-xen
later, but there's only so much we can protect against.
Since the current Xen shadow pagetable design requires a matching PAE feature in
both Dom0 and DomU, supplying both PAE & non-PAE kernels will create alot of
incompatability pain between Dom0 & DomUs. Since all server hardware & the
majority of current desktop/laptop hardware is PAE enabled we decided to go for
the PAE kernels only.
Nonetheless, we should definitely make the error much much more obvious, so that
the user has no doubt as to what the problem was if they boot this kernel on
I have the SAME Problem on DELL D400 machine (with the LATEST A08 BIOS).
The same kernel panic and reboot afterwards appears.
isn't any kernel parameter that can resolve the issue, even with performance
downgrades? i need XEN only for demo for clients not for Production use, at
least not on this machine.
Not sure how much more obvious it can be than the kernel printing the error that
it requires PAE capable hardware. And anaconda shouldn't allow installing it
when you don't have PAE now