[Xen-users] Re: Could not boot an 2.6.23 kernel as domU

[Gerhard Brauer <gerhard.brauer@xxxxxx>]

Gruesse!
* Gerhard Brauer <gerhard.brauer@xxxxxx> schrieb am [20.01.08 16:49]:

> xc_dom_kernel_file: filename="/boot/vmlinuz26-xenU"
> xc_dom_malloc_filemap    : 1812 kB
> xc_dom_ramdisk_file: filename="/boot/kernel26-xenU.img"
> xc_dom_malloc_filemap    : 1546 kB
> xc_dom_boot_xen_init: ver 3.2, caps xen-3.0-x86_32p
> 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:499: panic: xc_dom_find_loader: no loader found
> xc_dom_release: called

Ok, i make a step further...
Above image was a bzImage and i've found two similar threads in this mailing
list about this.

-------------
When i try the vmlinux from my kernel build then i got at the moment:
xc_dom_boot_xen_init: ver 3.2, caps xen-3.0-x86_32p
xc_dom_parse_image: called
xc_dom_find_loader: trying ELF-generic loader ... OK
elf_parse_binary: phdr: paddr=0x0 memsz=0x1c3ba4
elf_parse_binary: memory: 0x0 -> 0x1c3ba4
elf_xen_note_check: ERROR: Not a Xen-ELF image: No ELF notes or '__xen_guest' 
section found.
xc_dom_release: called
--------------

This error i could handle. I'm sure i've enabled all xen options in
kernel config but it's a distribution kernel with patches and so on.
I next build a vanilla kernel.

Is there still a technical reason why bzImage compressed kernels are not
regognized?

Gerhard

-- 
Die NASA brauchte 12 Jahre um einen Kugelschreiber zu entwickeln, der
kopfueber, in der Schwerelosigkeit und unter Wasser schreiben kann.
Die Russen benutzten einfach einen Bleistift...


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