xen-ia64-devel
[Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2]
Magenheimer, Dan (HP Labs Fort Collins) wrote:
>> Subject: RE: [PATCH] Patch for loading module[2of2]
>>
>> Please note, the meaning of the parameter is changed, you can
>> refer to fred's original email.
>>
>> For patched-xen, you should write elilo.conf like below
>> Initrd=rhinitrd.img (RHEL4.1) Module=xenlinux
>
> Um, why? Changing something this fundamental doesn't seem
> like a good idea. Could you please resubmit the patch
> to change the meaning of the parameters back?
Using initrd to load Linux kernel image is only a temporally workround and
should be corrected. There is no backward compability issue on Xen/ia64 on
loading kernel image per se. Rather, "initrd" should be maintained to load
"initrd" maintains the backward compability with current elilo.efi. The
"module" add-on is to continue to maintain elilo compability
Imaging a single elilo.conf to have multi-initrd with two different meanings,
this is definitely to confuse users.
> Yes with the parameters swapped it does seem to work,
> at least as far as trying to mount the root disk.
> (I don't yet have a combination of a non-rhel kernel
> and non-rhel initrd that boots.)
As indicated in the previous mail. The patch only validated to get to initrd,
but a corresponding initrd to match with xenlinux is yet to be built because no
initrd is built from the tree.
>
>>> -----Original Message-----
>>> From: Magenheimer, Dan (HP Labs Fort Collins)
>> [mailto:dan.magenheimer@xxxxxx]
>>> Sent: 2005年9月5日 5:25
>>> To: Yang, Fred; Xu, Anthony
>>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>> Subject: RE: [PATCH] Patch for loading module[2of2]
>>>
>>> My testing of the xen patch didn't go very well...
>>>
>>> unpatched-xen with patched-elilo, booting RHEL3.2: OK
>>> unpatched-xen with patched-elilo, module=rhinitrd.img (RHEL4.1):
>>> domain0 loads, no root disk (OK)
>>>
>>> patched-xen with existing-elilo, booting RHEL3.2: fails to load
>>> domain0 patched-xen with patched-elilo, module=rhinitrd.img
>>> (RHEL4.1): fails to load domain0 patched-xen with patched-elilo,
>>> booting RHEL3.2: fails to load domain0
>>>
>>> So it would appear that the xen patch is broken.
>>> I didn't try to debug, however the elilo verbose output does seem
>>> to indicate that it is loading "both" initrds (xenlinux and
>>> rhinitrd.img)
>>>
>>> One question: Is the xen patch (if it were working) intended to be
>>> backwards compatible? E.g. should it work with both an unpatched
>>> elilo (booting RHEL3.2) and a patched elilo (booting either RHEL3.2
>>> or RHEL4.1)? This would be highly desirable.
>>>
>>> Dan
>>>
>>>> -----Original Message-----
>>>> From: Yang, Fred [mailto:fred.yang@xxxxxxxxx]
>>>> Sent: Saturday, September 03, 2005 3:34 PM
>>>> To: Yang, Fred; Magenheimer, Dan (HP Labs Fort Collins); Xu,
>>>> Anthony Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>>> Subject: RE: [PATCH] Patch for loading module[2of2]
>>>>
>>>> Attached is Xen/ia64 patch again Rev Xen-ia64-unstable.hg REV 6461
>>>> Signed-off-by Fred Yang <Fred.Yang@xxxxxxxxx>
>>>> -Fred
>>>>
>>>> Yang, Fred wrote:
>>>>> Attached is patch for elilo to load Linux kernel as module.
>>>> A readme
>>>>> is also attached.
>>>>> We should push patch & readme into
>>>>> xen-ia64-unstable.hg/xen/arch/ia64/tools
>>>>>
>>>>> Note the Xen patch will be followed in a separate mail. Following
>>>>> is the required elilo.conf sample
>>>>>
>>>>> image=xen.gz
>>>>> label=xen
>>>>> module=xenlinux <== uncompressed Dom0
>>>>> image initrd=initrd-xenlinux.img <==
>>>>> corresponding Dom0 initrd read-only
>>>>> append="com2=57600,8n1 console=com2
>>>>> sched=bvt -- nomca console=ttyS1,576 00 console=tty0
>>>>> root=/dev/sda3"
>>>>>
>>>>> The patch has been validated to boot xenLinux. An initrd need to
>>>>> be built to match xenlinux & fully validated, though the initrd
>>>>> file can be loaded successfully.
>>>>>
>>>>> Signed-off-by Fred Yang <Fred.Yang@xxxxxxxxx>
>>>>>
>>>>> -Fred
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Yang, Fred
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Magenheimer, Dan (HP Labs Fort Collins)
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Xu, Anthony
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Magenheimer, Dan (HP Labs Fort Collins)
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2],
Yang, Fred <=
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Magenheimer, Dan (HP Labs Fort Collins)
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Xu, Anthony
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Yang, Fred
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Magenheimer, Dan (HP Labs Fort Collins)
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Magenheimer, Dan (HP Labs Fort Collins)
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Xu, Anthony
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Magenheimer, Dan (HP Labs Fort Collins)
- [Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2], Yang, Fred
|
|
|