Dan,
We have got the patch against Rev6450 tree to boot XenLinux Dom0 and in
processing of merge into the latest Xen-ia64-unstabl.
However, we were caught supprised that TIP tree layout is completely
changed.
What is the rational behind the layout change? This is quite a
different tree from x86 structure, what is the impact to merge
Xen-ia64-unstable back to Xen?
-Fred
Magenheimer, Dan (HP Labs Fort Collins) wrote:
> Hi Anthony --
>
> Is this still underway? I would like to try a RHEL4 system.
>
> Thanks,
> Dan
>
>> -----Original Message-----
>> From: Xu, Anthony [mailto:anthony.xu@xxxxxxxxx]
>> Sent: Friday, August 26, 2005 6:00 PM
>> To: Magenheimer, Dan (HP Labs Fort Collins); Yang, Fred
>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: RE: [Xen-ia64-devel] RE: [elilo-discuss] a patch to make
>> eliloloadanother module
>>
>> Dan,
>> As I mentioned before, I haven't tested the patch on
>> xenolinux. Maybe there is an address collision, I'll take a
>> look at this, make sure it can boot xenolinux, and send a new patch
>> to you.
>>
>> Thanks,
>> Anthony
>>
>>> -----Original Message-----
>>> From: Magenheimer, Dan (HP Labs Fort Collins)
>>> [mailto:dan.magenheimer@xxxxxx]
>>> Sent: Friday, August 26, 2005 4:22 PM
>>> To: Yang, Fred; Xu, Anthony
>>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>> Subject: RE: [Xen-ia64-devel] RE: [elilo-discuss] a patch to make
>>> eliloloadanother module
>>>
>>>> Time to call it a week! Bye!
>>>
>>> Alright, I admit it, I couldn't quit yet!
>>>
>>> I added Anthony's patch (last version I got) and see the
>>> same result: machine reboots with no console output.
>>>
>>> I added an infinite loop of printf's at the beginning
>>> of construct_dom0 and it doesn't get that far (whereas
>>> a normal RHEL3 boot still works fine). I'd have to
>>> guess that the initrd is getting loaded in memory
>>> at a "bad" place which is killing Xen very early.
>>>
>>> NOW, time to call it a week.
>>>
>>> Dan
>>>
>>>> -----Original Message-----
>>>> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>>> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
>>>> Of Magenheimer, Dan (HP Labs Fort Collins)
>>>> Sent: Friday, August 26, 2005 5:04 PM
>>>> To: Yang, Fred; Xu, Anthony
>>>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>>> Subject: RE: [Xen-ia64-devel] RE: [elilo-discuss] a patch to make
>>>> eliloloadanother module
>>>>
>>>> Another update... This problem goes away when I
>>>> specify verbose=3 (or verbose=2) at the beginning
>>>> of my elilo.conf file. With verbose off, or with
>>>> verbose=1, I get the load error. Weird...
>>>>
>>>> So on to the next step... the module (the RHEL4
>>>> initrd) gets loaded but after a few seconds (and
>>>> no console output), the system reboots. This is
>>>> probably not unexpected as I haven't yet patched
>>>> Xen itself (awaiting latest patch from Anthony).
>>>>
>>>> Time to call it a week! Bye!
>>>>
>>>>> -----Original Message-----
>>>>> From: Magenheimer, Dan (HP Labs Fort Collins)
>>>>> Sent: Friday, August 26, 2005 4:36 PM
>>>>> To: 'Yang, Fred'; 'Xu, Anthony'
>>>>> Cc: 'xen-ia64-devel@xxxxxxxxxxxxxxxxxxx'
>>>>> Subject: RE: [Xen-ia64-devel] RE: [elilo-discuss] a patch to make
>>>>> elilo loadanother module
>>>>>
>>>>> I got some help from a local Red Hat guru and got to
>>>>> the next step... the modified elilo fails with:
>>>>>
>>>>> Loading xen....done
>>>>> Loading initrd xenlinux...done
>>>>> initrd.c(line 77):Failed to allocate 318 pages for initrd
>>>>> Start of netboot failed: Load Error
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Magenheimer, Dan (HP Labs Fort Collins)
>>>>>> Sent: Friday, August 26, 2005 4:14 PM
>>>>>> To: 'Yang, Fred'; Xu, Anthony
>>>>>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>>>>> Subject: RE: [Xen-ia64-devel] RE: [elilo-discuss] a patch to
>>>>>> make elilo loadanother module
>>>>>>
>>>>>> Finally got a chance to look at this. There were a typos
>>>>>> of problems in the README script:
>>>>>>
>>>>>> - rpc2cpio -> rpm2cpio
>>>>>> - remove "patch -p2 < elilo-initrd-size-fix.patch"
>>>>>>
>>>>>> The resulting source got a couple of gcc errors
>>>>>> with find_label having too few arguments. I added
>>>>>> module_name as the last argument (two places) and
>>>>>> it compiled.
>>>>>>
>>>>>> However, I realize I don't know how to build a RHEL4
>>>>>> kernel (with Xen mods) and initrd that will successfully
>>>>>> boot a RHEL4 system (e.g. with LVM in the initrd?)!
>>>>>> I assume you have done it so far on VTI with an
>>>>>> unmodified RHEL4 kernel? Unless you can provide a
>>>>>> recipe for this, I will look into how to do it...
>>>>>>
>>>>>> Also, I think Anthony had an update for the Xen hypervisor
>>>>>> patch (with the complicated arithmetic with constants
>>>>>> put in a macro)?
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Yang, Fred [mailto:fred.yang@xxxxxxxxx]
>>>>>>> Sent: Thursday, August 11, 2005 10:29 PM
>>>>>>> To: Magenheimer, Dan (HP Labs Fort Collins); Xu, Anthony
>>>>>>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>>>>>> Subject: RE: [Xen-ia64-devel] RE: [elilo-discuss] a patch to
>>>>>>> make elilo loadanother module
>>>>>>>
>>>>>>> Magenheimer, Dan (HP Labs Fort Collins) wrote:
>>>>>>>> Great! I would be happy to try out a preliminary
>>>>>>>> version of these instructions... Last Friday, I managed
>>>>>>>> to trash one disk on my test machine and partially trash
>>>>>>>> another, both running RHEL3.2. Rather than reinstall 3.2
>>>>>>>> and then install RHEL4 a few days later, I will just
>>>>>>>> wait and go straight to RHEL4.
>>>>>>> Attached is a Knowhow to create elilo patch for loading
>>>>>>> kernel as module, as well as Xen patch for Vti.
>>>>>>> Please note this patches are only a tempory patches, we will
>>>>>>> come out yet another patch in a couple days.
>>>>>>> Current kernel input can only be unzipped image. The next
>>>>>>> patch will make "module" as the deafult linux kernel and do
>>>>>>> the corrsponding unzip within elilo. The system.h patch will
>>>>>>> be surrounded with "#ifdef CONFG_Xen". Xen patch will also
>>>>>>> include non-VT-I patch code (but without validation due to
>>>>>>> target linux issue :() -Fred
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-ia64-devel mailing list
>>>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-ia64-devel
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home