I got this built, and followed the Xen Project website to add the kernel config options to create my 4.19.26 Dom0 kernel, booted it and it seemed to work OK.
Unfortunately, the Xen + LILO instructions I was trying seem to be a little out of date:
https://lxadm.com/Running_Xen_with_LILO
They talk about being able to do zcat <image> to uncompress a compressed Linux kernel. A bit of reading and I found there's a script at /usr/src/linux/scripts/extract-vmlinux that's supposed to do this for you. I tried it, then made the bootpack. Except I didn't need an initrd (the Dom0 kernel boots without one), so I only included a single 'module' which was my Dom0 kernel.
Code:
mbootpack -o vmlinuz-xen-mbootpack -m vmlinuz-xen-uncomp xen-4.12.0
I put an entry in my elilo.conf file (/boot/efi/EFI/Slackware/) that looks like this:
Code:
chooser=simple
delay=30
timeout=30
#
image=vmlinuz
label=vmlinuz
initrd=initrd.gz
read-only
append="root=/dev/sda2 vga=normal ro"
image=vmlinuz-xen-mbootpack
label=vmlinuz-xen-mbootpack
read-only
append="dom0_mem=256M -- root=/dev/sda2 vga=normal ro"
Now I don't know what's up with ELILO, because that didn't give me a nice prompt to chose between the images, but with some fiddling I'm sure I did boot the bootpack because I was rewarded with a page of 99s, and when I did nothing and let it boot, I got back my original vmlinuz.
So has anyone gone through this setup recently? Am I doing something obviously wrong? I'm very new to ELILO, so maybe mbootpack just plain doesn't work with it.
Many thanks for any help!
