[Xen-users] Fedora install: Domain0 allocation is too small for current kernel

[Lucas Kenter <lucas.kenter@xxxxxxxxx>]

Hello,

I've just installed Fedora Core 4 and I'm now trying to install xen.
I'm follwing the redhat quickstart but when I try to boot the xen
kernel I get the sam errors as described in a previous message to this
list. Nobody has answered, so I thought it was a good idea to repost
it...

Greetings, 


I installed Fedora a few weeks ago and have been using the basic 
instructions from http://www.fedoraproject.org/wiki/FedoraXenQuickstart.  
This worked well, however since then there was a new linux kernel 2.6.13 and 
the base development Fedora kernel was updated.  Xen was also updated, and 
it's been updated once more since the new kernel also.  Niether of the new 
Xen kernels boot. 


This one doesn't boot:
-----------------------------------------------
title Fedora Core (2.6.13-1.1530_FC5xen0)
      root (hd0,0)
      kernel /xen.gz
      module /vmlinuz-2.6.13-1.1530_FC5xen0 ro 
root=/dev/VolGroup00/LogVol00
      module /initrd-2.6.13-1.1530_FC5xen0.img
----------------------------------------------- 


Nor does this:
-----------------------------------------------
title Fedora Core (2.6.13-1.1529_FC5xen0)
      root (hd0,0)
      kernel /xen.gz
      module /vmlinuz-2.6.13-1.1529_FC5xen0 ro 
root=/dev/VolGroup00/LogVol00
      module /initrd-2.6.13-1.1529_FC5xen0.img
----------------------------------------------- 


The error is:
-----------------------------------------------
Panic on CPU 0:
Domain 0 allocation is too small for kernel image
----------------------------------------------- 


I've tried adding extra argument on boot:
-----------------------------------------------
title Fedora Core (2.6.13-1.1526_FC5xen0)
      root (hd0,0)
      kernel /xen.gz dom0_mem=131072
      module /vmlinuz-2.6.13-1.1526_FC5xen0 ro 
root=/dev/VolGroup00/LogVol00
      module /initrd-2.6.13-1.1526_FC5xen0.img
----------------------------------------------- 


I also tried 'dom0_mem=262144' and 'dom0_mem=65536'.  I know the 
/etc/grub.conf changes are working because 'noreboot' is working. 


Ideas? 

The system is a HP DL380 Xeon 3.4 GHz with single CPU (with hyperthreading) 
and 1 GB of ram. 


Regards,
Dave Seddon

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users