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

RE: [Xen-ia64-devel] RFC: Switch to xlilo now? Or post-3.0?



Oops..
I used my tools build patch befor make world.

Best Regards,

Akio Takebe

>Hi Dan,
>
>Plese call Akio. :-)
>
>I probably did the following step.
>
># cd /root
># hg clone http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
># cp /home/takebe/linux-2.6.12.tar.bz2 /root/xen-ia64-unstable.hg
># cd /root/xen-ia64-unstable.hg
># patch -p1 < /root/xen-xlilo.patch  <-----Tristan's Patch
># make world
># make install-tools
># cp xen/xen.gz /boot/efi/efi/xen/
># cp linux-2.6.12-xen0/vmlinux /boot/efi/efi/xen/vmlinux-2.6.12-xen0
># cd linux-2.6.12-xen0
># make modules_install
># mkinitrd -f /boot/efi/efi/xen/initrd-2.6.12-xen0.img 2.6.12.6-xen0
># vi /boot/efi/efi/xen/elilo.conf 
>       image=vmlinux-2.6.12-xen0
>               label=xen
>               vmm=xen.gz
>               initrd=initrd-2.6.12-xen0.img
>               read-only
>               append="com2=115200,8n1 console=com2 sched=bvt maxcpus=1 
>-- nomca nosmp console=tty0 console=ttyS1,115200,8n1 rhgb root=/dev/sda2"
>
># reboot
>and boot with /boot/efi/efi/xen/xlilo.efi
>
>Best Regards,
>
>Akio Takebe
>
>>Takebe -- (Sorry, should I call you Akio or Takebe?)
>>
>>Did you build and install from xen-ia64-unstable tip (cset 7734 or
>>greater)?
>>
>>If so, could you again provide the recipe for building and installing
>>on RHEL4?  I would like to try again and some things have changed
>>(such as CONFIG_LOCALVERSION and the build process for domU) so I would
>>like to understand the exact steps you used successfully first.
>>
>>Thank you!
>>Dan
>>
>>> -----Original Message-----
>>> From: takebe_akio@xxxxxxxxxxxxxx [mailto:takebe_akio@xxxxxxxxxxxxxx] 
>>> Sent: Thursday, November 17, 2005 6:11 AM
>>> To: Tristan Gingold; Magenheimer, Dan (HP Labs Fort Collins); 
>>> Yang, Fred; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>> Subject: Re: [Xen-ia64-devel] RFC: Switch to xlilo now? Or post-3.0?
>>> 
>>> Hi Tristan,
>>> 
>>> Great!!!
>>> I test your patch with xlilo on RHEL4.
>>> I confirmed Dom0 can be booted.
>>> 
>>> The following is my elilo.conf. :-)
>>> --------------------------
>>> image=vmlinux-2.6.12-xen0
>>>         label=xen
>>>         vmm=xen.gz
>>>         initrd=initrd-2.6.12-xen0.img
>>>         read-only
>>>         append="com2=115200,8n1 console=com2 sched=bvt maxcpus=1 -- 
>>> nomca nosmp console=tty0 console=ttyS1,115200,8n1 rhgb root=/dev/sda2"
>>>         
>>> --------------------------
>>> 
>>> Best Regards,
>>> 
>>> Akio Takebe
>>> 
>>> >Le Mercredi 16 Novembre 2005 22:36, Magenheimer, Dan (HP 
>>> Labs Fort Collins)
>>> > a 
>>> >馗rit :
>>> >> > Magenheimer, Dan (HP Labs Fort Collins) wrote:
>>> >> > > Once the xen4elilo patch got applied, this no longer worked
>>> >> > > for me.  It may have been my pilot error.
>>> >> >
>>> >> > The key descision is when to move to new elilo.efi for Xen to
>>> >> > take advantage of xen.gz loading.  We should all move forward
>>> >> > together to get the feature
>>> >> > -Fred
>>> >>
>>> >> Perhaps.  But there is not a patch on the table for
>>> >> support of compressed images yet, and there is one
>>> >> waiting for xlilo.  Since 3.0 is imminent, let's decide
>>> >> on the xlilo patch that is waiting.  If a compressed image
>>> >> patch is available and tested prior to 3.0 freeze,
>>> >> we can consider that one too.
>>> >Here is the change.
>>> >I have only tested it with the old elilo on my RHEL 3.
>>> >
>>> >Tristan.
>>> >
>>> >Signed-off-by: Tristan Gingold <tristan.gingold@xxxxxxxx>
>>> >
>>> >
>>> >-------------------------------text/plain--------------------
>>> -----------
>>> >_______________________________________________
>>> >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


 


Rackspace

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