On 2/22/2005 8:50 AM, Stephane Eranian wrote:
> Arun,
> 
> On Mon, 2005-02-21 at 22:26 -0800, Arun Sharma wrote:
>> Stephane Eranian wrote:
>> 
>> > elilo loads each block of text/data at the address indicated by the
>> > paddr of the corresponding program header.
>> > 
>> > Are you saying that the address is different only when you abort a load?
>> 
>> Yes, that's right. Other missing pieces of info:
>> 
>> - I was using the elilo shipped with a RHEL4 beta
>> - my elilo.conf:
>> 
>> image=xen
>>         label=xen
>>         initrd=xenlinux
>>         read-only
>>         append="nomca console=ttyS1,57600 root=/dev/sda2"
>> 
>> xenlinux is a large uncompressed binary - so it's easy to hit space to 
>> abort it's loading.
>> 
> Ok, this means it is using the plain_loader.c. But that should not
> really matter.
> 

Murphy's law. Now that I'm trying to debug, I can't reproduce the problem any more.

Non debug:

startup.nsh> elilo xen
ELILO
Loading xen.....done
Loading initrd xenlinux...initrd.c(line 90):read initrd(xenlinux) failed: 1

ELILO boot: xen
Loading xen...ConvertPages: Incompatible memory types
plain_loader.c(line 292):relocation is disabled, cannot load kernel
Exit status code: Load Error

Debug output is also attached.

One thing I noticed is that if the loading of initrd (xenlinux) fails, the memory for initrd is freed, but the memory for the main image (xen) is not freed?

	-Arun