[prev in list] [next in list] [prev in thread] [next in thread] 

List:       npaci-rocks-discussion
Subject:    Re: [Rocks-Discuss] (Really) custom kernel shall be used
From:       support <support () gridplexus ! com>
Date:       2010-08-30 21:48:31
Message-ID: 4C7C272F.5000206 () gridplexus ! com
[Download RAW message or body]

Martin,

Here are my notes that have helped me build/verify correct custom kernel 
in the past.  More info should be available on the list.  Please adjust 
to your versions as required. 

make roll  > roll.log 2>&1
 tail roll.log
 cat roll.log | grep unpacking

rocks add roll kernel*iso

mount -o loop kernel-5.2-0.i386.disk1.iso /mnt/cdrom
cd /mnt/cdrom
strings isolinux/vmlinuz | grep 2\.6\.18

-Robert



Martin Brodbeck wrote:
> The custom kernel has been freshly built (2010-08-26). So I don't 
> think that the time-stamp is a problem.
>
> Martin
>
> Am 27.08.2010 17:21, schrieb Bart Brashers:
>> What are the time-stamps on the files themselves?  The installer will 
>> pick the newest file, so perhaps a "touch" on your desired kernel RPM 
>> will work.
>>
>> Bart
>>
>>> Thanks for your answer. But you somehow bypass the rocks-system, right?
>>> I wonder *why* Rocks doesn't use our kernel as default, since it is
>>> slightly newer (2.6.18-194.3.1.el5.028stab069.6.NETxen) than the
>>> original one (2.6.18-164.6.1.el5PAE). Is it because rocks prefers a
>>> PAE-kernel before a XEN-kernel?
>>>
>>> Maybe someone can tell me how rocks is "thinking" here and how I can
>>> convince it using our kernel…
>>>
>>> best regards,
>>> Martin
>>>
>>> Am 26.08.2010 16:09, schrieb Mike Hanby:
>>>> We have to run the Lustre kernels on our compute nodes. The Lustre 
>>>> kernel
>>> is an older version than what is provided in Rocks 5.3. Our procedure
>>>>
>>>> 1. copying the kernel and other related packages to the contrib 
>>>> directory
>>>> 2. In extend-compute.xml (and other appliance xml files) we add the
>>> following to the<post>   section:
>>>>
>>>> <!-- 20091223 MJH Replace default kernel with the Kernel used for 
>>>> Lustre
>>> clients -->
>>>> <file name="/etc/rc.d/rocksconfig.d/post-97-replace-kernel" 
>>>> perms="0755">
>>>> /sbin/service rocks-grub stop
>>>> /sbin/chkconfig rocks-grub off
>>>>
>>>> # Change default runlevel to 3 in case it's set to 5
>>>> /usr/bin/perl -pi -e 's/^id:5:initdefault/id:3:initdefault/g' 
>>>> /etc/inittab
>>>>
>>>> # Install the Lustre kernel packages, these are older than the 
>>>> currently
>>> installed kernel so use --oldpackage
>>>> /bin/rpm -ivh --oldpackage /share/apps/lustre/kernel-2.6.18-
>>> 128.7.1.el5.x86_64.rpm /share/apps/lustre/kernel-devel-2.6.18-
>>> 128.7.1.el5.x86_64.rpm
>>>>
>>>> # Optionally add the doc and headers to the above command
>>>> # /share/apps/lustre/kernel-doc-2.6.18-128.7.1.el5.noarch.rpm
>>> /share/apps/lustre/kernel-headers-2.6.18-128.7.1.el5.x86_64.rpm
>>>>
>>>> # Modify grub to boot this kernel as the default
>>>> /sbin/grubby --copy-default --make-default \
>>>>    --initrd=/boot/initrd-2.6.18-128.7.1.el5.img \
>>>>    --add-kernel=/boot/vmlinuz-2.6.18-128.7.1.el5 --title="Rocks 
>>>> (2.6.18-
>>> 128.7.1.el5)"
>>>>
>>>> /bin/mv /etc/rc.d/rocksconfig.d/post-97-replace-kernel /root/post-97-
>>> replace-kernel
>>>>
>>>> /sbin/shutdown -r now
>>>>
>>>> </file>
>>>>
>>>> -----Original Message-----
>>>> From: npaci-rocks-discussion-bounces@sdsc.edu [mailto:npaci-rocks-
>>> discussion-bounces@sdsc.edu] On Behalf Of Martin Brodbeck
>>>> Sent: Thursday, August 26, 2010 3:26 AM
>>>> To: npaci-rocks-discussion@sdsc.edu
>>>> Subject: [Rocks-Discuss] (Really) custom kernel shall be used
>>>>
>>>> Hello all,
>>>>
>>>> it is necessary that we use a custom and heavily patched kernel on our
>>>> compute nodes. It cannot (or not so easy) be built how it is explained
>>>> in the user guide documentation. But the kernel rpm package ist named
>>>> kernel-xen[…].rpm and — after putting it into the contrib directory 
>>>> — it
>>>> is correctly installed on the nodes.
>>>>
>>>> Unfortunately, the nodes still boot the rocks kernel
>>>> (2.6.18-164.6.1.el5PAE). So my question is what am I doing wrong here?
>>>> How can I achieve that our own kernel is being used?
>>>>
>>>> Here is the grub menu:
>>>> --- snip ---
>>>> […]
>>>> default=0
>>>> timeout=5
>>>> hiddenmenu
>>>> title Rocks Reinstall
>>>>            root (hd0,0)
>>>>            kernel //kickstart/default/vmlinuz-5.3-i386
>>>> ramdisk_size=150000 kssendmac ks selinux=0
>>>>            initrd //kickstart/default/initrd.img-5.3-i386
>>>> title Rocks (2.6.18-164.6.1.el5PAE)
>>>>            root (hd0,0)
>>>>            kernel /vmlinuz-2.6.18-164.6.1.el5PAE ro root=/dev/md1
>>>>            initrd /initrd-2.6.18-164.6.1.el5PAE.img
>>>> title Rocks-xen (2.6.18-194.3.1.el5.028stab069.6.NETxen)
>>>>            root (hd0,0)
>>>>            kernel /xen.gz-2.6.18-194.3.1.el5.028stab069.6.NET
>>>>            module /vmlinuz-2.6.18-194.3.1.el5.028stab069.6.NETxen ro
>>>> root=/dev/md1
>>>>            module /initrd-2.6.18-194.3.1.el5.028stab069.6.NETxen.img
>>>> --- snip ---
>>>>
>>>> Thanks a lot
>>>> Martin
>>>
>>>
>>> -- 
>>> Univ. Stuttgart, IPVS | phone : +49(0)711 / 7816 479
>>> Universitässtr. 38    | fax   : +49(0)711 / 7816 1479
>>> D-70569 Stuttgart     | email : martin.brodbeck@ipvs.uni-stuttgart.de
>>
>>
>> This message contains information that may be confidential, 
>> privileged or otherwise protected by law from disclosure. It is 
>> intended for the exclusive use of the Addressee(s). Unless you are 
>> the addressee or authorized agent of the addressee, you may not 
>> review, copy, distribute or disclose to anyone the message or any 
>> information contained within. If you have received this message in 
>> error, please contact the sender by electronic reply to 
>> email@environcorp.com and immediately delete all copies of the message.
>
>

[prev in list] [next in list] [prev in thread] [next in thread]