Red Hat Bugzilla – Bug 172079
xen kernel panic
Last modified: 2007-11-30 17:11:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Epiphany/1.6.5
Description of problem:
Booting Xen gives me the following kernel panic:
(XEN) Panic on CPU0:
(XEN) Domain 0 allocation is too small for kernel image.
(XEN) Reboot in five seconds...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is still broken, and fc5t1 is frozen now.
Please could you tell me what the problem?
Lack of interest. Do you want this closed?
There has been a significant rebasing of the kernel and HV images for fc5t2.
Can you still reproduce the problem?
If so, then this sounds like a mismatch between the memory calculations in the
HV/bootloader and the kernel. The full Xen logs would be really useful in
tracking this down; is it possible for you to capture that to a serial console?
That, in conjunction with the normal non-xen boot logs, should let us examine
the memory maps being computed in both cases to see if there's a mismatch somewhere.
You _may_ be able to work around this by adding the "dom0_mem=...M" option to
the xen hypervisor line ("kernel=xen...") in /etc/grub.conf. If you assign
(say) only half your physical memory to dom0 on boot, does that work?
There are a number of other reports of this in bug 172406: I'll close this one
as a dup to keep the majority of the reports in one place. Please followup in
the other bug report.
*** This bug has been marked as a duplicate of 172406 ***