Digging around for instances of the "no loader found" error, I found in /var/log/xen/domain-builder-ng.log xc_dom_allocate: cmdline="ks=<a href="http://10.0.0.100/cblr/kickstarts/f8_min_pv/ks.cfg">http://10.0.0.100/cblr/kickstarts/f8_min_pv/ks.cfg</a> ksdevice=eth0 lang= kssendmac syslog=<a href="http://10.0.0.100:25150">10.0.0.100:25150</a> text ", features="" xc_dom_kernel_file: filename="/var/lib/xen/vmlinuz" xc_dom_ramdisk_file: filename="/var/lib/xen/initrd.img" xc_dom_boot_xen_init: ver 3.1, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_dom_find_loader: trying multiboot-binary loader ... failed xc_dom_core.c:495: panic: xc_dom_find_loader: no loader found xc_dom_release: called checking for the loaders in /var/lib/cobbler/settings, --- bootloaders: ia64: /var/lib/cobbler/elilo-3.6-ia64.efi standard: /usr/lib/syslinux/pxelinux.0 ... they do exist: ls -al /var/lib/cobbler/elilo-3.6-ia64.efi /usr/lib/syslinux/pxelinux.0 -rw-r--r-- 1 root root 13408 2007-10-17 08:53 /usr/lib/syslinux/pxelinux.0 -rw-rw-r-- 1 root root 374146 2008-01-31 15:04 /var/lib/cobbler/elilo-3.6-ia64.efi Not clear why the "xc_dom_find_loader" calls for finding the loader "failed", unless they're the wrong loader type.