So I wanted to put together a system that would build i686 and x64 versions of the kernel.
Shouldn’t be hard, I thought. Maybe a simple
yum install gcc.i686, and that’s all.
In short, I was wrong. So very wrong.
So I gave up and installed Fedora 14 with an i686 kernel. Except that, you know, something has to go wrong.
Turns out Anaconda doesn’t install kernel-PAE packages by default. Which… Xen needs to boot.
So a virt-install later, and I get tossed out with
ERROR POST operation failed: xend_post: error from xen daemon: (xend.err "Error creating domain: (2, 'Invalid kernel', 'elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images')")
Excuse me while I mount the domU drive in my VM, chroot, install kernel-PAE, let it run through the creation of the initial RAMdisk and what’s that you say?
yum install kernel-PAE comes back with no such package found?
[[email protected] xen]# yum search kernel-PAE Loaded plugins: langpacks, presto, refresh-packagekit Adding en_US to language list fedora/metalink | 11 kB 00:00 updates/metalink | 7.6 kB 00:00 updates | 4.7 kB 00:00 updates/primary_db | 5.6 MB 00:07 updates/pkgtags | 64 kB 00:00 Warning: No matches found for: kernel-PAE
Of course it does. This can never be smooth. So, it’s off to Koji to grab the PAE variant of the latest F14 kernel, and install that with a quick rpm -ivh while I have my domU mounted in my dom0.
dracut thankfully works fine, though grubby falls over and dies with a “No suitable template found” error. Dreading having to type out the entire options line, I just modified the kernel & initrd filename to reflect the new kernel/generated initrd. Currently, my cross-compiling workaround system is booting.
(As a side note, I’m guessing
yum install kernel-PAE failed because it’s not in the 64 bit yum repo.)