Talk:Running Xen with LILO
From WPKG | Open Source Software Deployment and Distribution
I did all you describe but at boot time I've got the error :
Fatal error : dom0 kernet not specified check bootloader configuraton
- Are you sure you used mbootpack options correctly? You might want to try again, just in case.
Dell optiplex 320 Fedora 7 x86_64 my lilo.conf
============
prompt
timeout=55
default=2.6.22.9-91.fc7
boot=/dev/sda
#map=/boot/System.map-2.6.21-1.3194.fc7
map=/boot/System.map-2.6.18-xen
#map=/boot/System.map
install=/boot/boot.b
lba32
image=/boot/vmlinuz-2.6.22.9-91.fc7
label=2.6.22.9-91.fc7
initrd=/boot/initrd-2.6.22.9-91.fc7.img
read-only
append="pci=nomsi noapic acpi=off notsc root=/dev/sda3"
image=/boot/vmlinuz-2.6.21-1.3194.fc7
label=Fc7-2.6.21-1
initrd=/boot/initrd-2.6.21-1.3194.fc7.img
read-only
append="pci=nomsi noapic acpi=off notsc root=/dev/sda3"
image=/boot/vmlinuz-2.6.18-xen-mbootpack
label=xen
read-only
append="dom0_mem=512M -- netloop.nloopbacks=16"
# append="pci=nomsi noapic acpi=off notsc "
root=/dev/sda3
Shouldn't the ramdisk be created with a "-o" option?
mkinitrd -o /boot/initrd-2.6.18.8-xen.img 2.6.18.8-xen
- It may depend on the "mkinitrd" you have - almost all distributions ship with a different mkinitrd script, which may have different options.
- In my case (Slackware 13, linux 3.2.9, xen 4.1.2, mbootpack 0.6) i used the mbootpack without any initrd and it worked just fine.