[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: [elilo-discuss] a patch to make elilo loadanother module


  • To: "Yang, Fred" <fred.yang@xxxxxxxxx>, "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Fri, 26 Aug 2005 15:13:57 -0700
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 26 Aug 2005 22:11:56 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWYaSAKDEpFITOYRmOMPwJnp5q9pQAADjIQADg3V1AALzs7IAAA1IBAAJG2/gAAqDjkoALc+tCg
  • Thread-topic: [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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.