Recent changes to Using_Provmethod=osimagename

Using_Provmethod=osimagename modified by Victor Hu

Victor Hu — Wed, 05 Nov 2014 20:54:44 -0000

--- v179
+++ v180
@@ -184,60 +184,69 @@

 #### **Installing a New Kernel in the Stateless Image**

-The _kerneldir_ attribute in _linuximage_ table is used to assign one directory to hold the new kernel to be installed into the stateless/statelite image. Its default value is _/install/kernels_, you need to create the directory named _<kernelver>_ under the _kerneldir_, and genimage will pick them up from there. 
-
-Assuming you have the kernel in RPM format in /tmp, the value of _kerneldir_ is not set (which will take the default value: _/install/kernels_). 
-
-This procedure assumes you are using xCAT 2.6.1 or later. The rpm names are an example and you can substitute your level and architecture. The kernel will be installed directly from the rpm package. 
-
-  
-
-
-  * For RHEL: 
-
-The kernel RPM package is usually named _kernel-<kernelver>.rpm_, for example: kernel-2.6.32.10-0.5.x86_64.rpm is the kernel package for **2.6.32.10-0.5.x86_64**. 
-
-  
-~~~~ 
-    
-    cp /tmp/kernel-2.6.32.10-0.5.x86_64.rpm /install/kernels/
-    createrepo /install/kernels/
-~~~~     
-
-  
-
-
-  * For SLES: 
-
-Usually, the kernel files for SLES are separated into two parts: _kernel-<arch>-base_ and _kernel_, and the naming of kernel RPM packages are different. For example, there's two RPM packages in /tmp: 
+**Note: This procedure assumes you are using xCAT 2.6.1 or later.**
+
+The _kerneldir_ attribute in _linuximage_ table can be used to assign a directory containing kernel RPMs that can be installed into stateless/statelite images. The default for _kernerdir_ is _/install/kernels_.  To add a new kernel, create a directory named _<kernelver>_ under the _kerneldir_, and genimage will pick them up from there. 
+
+The following examples assume you have the kernel RPM in /tmp and is using the default value for _kerneldir_ (_/install/kernels_).  
+
+*The RPM names below are only examples, substitute your specific level and architecture.*
+
+
+**[RHEL]:**
+
+The RPM kernel package is usually named: _kernel-<kernelver>.rpm_.
+For example, **kernel-2.6.32.10-0.5.x86_64.rpm** means _kernelver_=**2.6.32.10-0.5.x86_64**. 
+
+~~~~ 
+    mkdir -p /install/kernels/2.6.32.10-0.5.x86_64
+    cp /tmp/kernel-2.6.32.10-0.5.x86_64.rpm /install/kernels/2.6.32.10-0.5.x86_64/
+    createrepo /install/kernels/2.6.32.10-0.5.x86_64/
+~~~~     
+ 
+
+Run genimage/packimage to update the image with the new kernel. 
+**Note:** *If downgrading the kernel, you may need to first remove the rootimg directory.*
+
+~~~~   
+    genimage <imagename> -k 2.6.32.10-0.5.x86_64
+    packimage <imagename>
+~~~~  
+
+ 
+
+**[SLES]:** 
+
+The RPM kernel package is usually separated into two parts: _kernel-<arch>-base_ and _kernel_<arch>. 
+For example, /tmp contains the following two RPMs:

 ~~~~     
     kernel-ppc64-base-2.6.27.19-5.1.x86_64.rpm
     kernel-ppc64-2.6.27.19-5.1.x86_64.rpm
 ~~~~     
-
-_2.6.27.19-5.1.x86_64_ is **NOT** the kernel version. _2.6.27.19-5-_x86_64 is the kernel version . Follow this naming convention to determine the kernel version. 
-
-After the kernel version is determined for SLES, then: 
-
-  
-
-~~~~     
-    cp /tmp/kernel-ppc64-base-2.6.27.19-5.1.x86_64.rpm /install/kernels/
-    cp /tmp/kernel-ppc64-2.6.27.19-5.1.x86_64.rpm /install/kernels/
-~~~~     
-
-  
-Run genimage/packimage to update the image with the new kernel: (Use sles as example) 
-
-  
-
-
-Since the kernel version is different from the rpm package version, the -g flag needs to be specified on the genimage command for the rpm version of kernel packages. 
-
-~~~~     
-    genimage -i eth0 -n ibmveth -o sles11.1 -p compute -k 2.6.27.19-5-x86_64 -g 2.6.27.19-5.1
-~~~~     
+ 
+
+*2.6.27.19-5.1.x86_64* is **NOT** the kernel version,  2.6.27.19-**5-**x86_64 is the kernel version.  
+The "5.1.x86_64" is replaced with "5-x86_64". 
+
+~~~~
+    mkdir -p /install/kernels/2.6.27.19-5-x86_64/
+    cp /tmp/kernel-ppc64-base-2.6.27.19-5.1.x86_64.rpm /install/kernels/2.6.27.19-5-x86_64/
+    cp /tmp/kernel-ppc64-2.6.27.19-5.1.x86_64.rpm /install/kernels/2.6.27.19-5-x86_64/
+
+~~~~     
+ 
+
+Run genimage/packimage to update the image with the new kernel. 
+**Note:** *If downgrading the kernel, you may need to first remove the rootimg directory.*
+
+Since the kernel version name is different from the kernel rpm package name, the -g flag **MUST** to be specified on the genimage command. 
+
+~~~~
+    genimage <imagename> -k 2.6.27.19-5-x86_64 -g 2.6.27.19-5.1
+    packimage <imagename>
+~~~~
+ 

 #### **Installing New Kernel Drivers to Stateless Initrd**

Using_Provmethod=osimagename modified by Guang Cheng Li

Guang Cheng Li — Thu, 14 Aug 2014 07:35:26 -0000

--- v178
+++ v179
@@ -100,8 +100,8 @@
 Sync lists contain a list of files that should be sync'd from the management node to the image and to the running nodes. This allows you to have 1 copy of config files for a particular type of node and make sure that all those nodes are running with those config files. The sync list should contain a line for each file you want sync'd, specifying the path it has on the MN and the path it should be given on the node. For example:

 ~~~~     
-    /install/custom/syncfiles/compute/etc/motd > /etc/motd
-    /etc/hosts > /etc/hosts
+    /install/custom/syncfiles/compute/etc/motd -> /etc/motd
+    /etc/hosts -> /etc/hosts
 ~~~~     

 If you put the above contents in /install/custom/netboot/rh/compute.synclist, then:

Using_Provmethod=osimagename modified by Lissa Valletta

Lissa Valletta — Wed, 09 Jul 2014 17:01:32 -0000

--- v177
+++ v178
@@ -33,43 +33,51 @@
 **Note: To use an osimage as your provisioning method, you need to be running xCAT 2.6.6 or later.**

 The provmethod attribute of your nodes should contain the name of the osimage object definition that is being used for those nodes. The [osimage object](http://xcat.sourceforge.net/man7/osimage.7.html) contains paths for pkgs, templates, kernels, etc. If you haven't already, run [copycds](http://xcat.sourceforge.net/man8/copycds.8.html) to copy the distro rpms to /install. Default osimage objects are also defined when copycds is run. To view the osimages: 
-    
+
+~~~~    
     lsdef -t osimage          # see the list of osimages
-    lsdef -t osimage <osimage-name>          # see the attributes of a particular osimage
+    lsdef -t osimage <osimage-name>
+          # see the attributes of a particular osimage
+~~~~ 

 ### Select or Create an osimage Definition

 From the list found above, select the osimage for your distro, architecture, provisioning method (install, netboot, statelite), and profile (compute, service, etc.). Although it is optional, we recommend you make a copy of the osimage, changing its name to a simpler name. For example: 
-    
+ 
+~~~~    
     lsdef -t osimage -z rhels6.3-x86_64-netboot-compute | sed 's/^[^ ]\+:/mycomputeimage:/' | mkdef -z
-    
+
+~~~~     

 This displays the osimage "rhels6.3-x86_64-netboot-compute" in a format that can be used as input to mkdef, but on the way there it uses sed to modify the name of the object to "mycomputeimage". 

 Initially, this osimage object points to templates, pkglists, etc. that are shipped by default with xCAT. And some attributes, for example otherpkglist and synclists, won't have any value at all because xCAT doesn't ship a default file for that. You can now change/fill in any [osimage attributes](http://xcat.sourceforge.net/man7/osimage.7.html) that you want. A general convention is that if you are modifying one of the default files that an osimage attribute points to, copy it into /install/custom and have your osimage point to it there. (If you modify the copy under /opt/xcat directly, it will be over-written the next time you upgrade xCAT.) An important attribute to change is the rootimgdir which will contain the generated osimage files so that you don't over-write an image built with the shipped definitions. To continue the previous example: 
-    
+
+~~~~     
       chdef -t osimage -o mycomputeimage rootimgdir=/install/netboot/rhels6.3/x86_64/mycomputeimage
-    
+~~~~     

 ### Set up pkglists

 You likely want to customize the main pkglist for the image. This is the list of rpms or groups that will be installed from the distro. (Other rpms that they depend on will be installed automatically.) For example: 
-    
+
+~~~~     
     mkdir -p /install/custom/netboot/rh
     cp -p /opt/xcat/share/xcat/netboot/rh/compute.rhels6.x86_64.pkglist /install/custom/netboot/rh
     vi /install/custom/netboot/rh/compute.rhels6.x86_64.pkglist
     chdef -t osimage mycomputeimage pkglist=/install/custom/netboot/rh/compute.rhels6.x86_64.pkglist
-    
+~~~~     

 The goal is to install the fewest number of rpms that still provides the function and applications that you need, because the resulting ramdisk will use real memory in your nodes. 

 Also, check to see if the default exclude list excludes all files and directories you do not want in the image. The exclude list enables you to trim the image after the rpms are installed into the image, so that you can make the image as small as possible. 
-    
+
+~~~~     
     cp /opt/xcat/share/xcat/netboot/rh/compute.exlist /install/custom/netboot/rh
     vi /install/custom/netboot/rh/compute.exlist 
     chdef -t osimage mycomputeimage exlist=/install/custom/netboot/rh/compute.exlist
-    
+~~~~     

 Make sure nothing is excluded in the exclude list that you need on the node. For example, if you require perl on your nodes, remove the line "./usr/lib/perl5*". 

@@ -80,37 +88,45 @@
 ### Set up a postinstall script (optional)

 Postinstall scripts for diskless images are analogous to postscripts for diskfull installation. The postinstall script is run by genimage near the end of its processing. You can use it to do anything to your image that you want done every time you generate this kind of image. In the script you can install rpms that need special flags, or tweak the image in some way. There are some examples shipped in /opt/xcat/share/xcat/netboot/<distro>. If you create a postinstall script to be used by genimage, then point to it in your osimage definition. For example: 
-    
+
+~~~~     
     chdef -t osimage mycomputeimage postinstall=/install/custom/netboot/rh/compute.postinstall
-    
+~~~~     

 ### Set up Files to be synchronized on the nodes

 Note: This is only supported for stateless nodes in xCAT 2.7 and above. 

 Sync lists contain a list of files that should be sync'd from the management node to the image and to the running nodes. This allows you to have 1 copy of config files for a particular type of node and make sure that all those nodes are running with those config files. The sync list should contain a line for each file you want sync'd, specifying the path it has on the MN and the path it should be given on the node. For example: 
-    
-    /install/custom/syncfiles/compute/etc/motd -> /etc/motd
-    /etc/hosts -> /etc/hosts
-    
+
+~~~~     
+    /install/custom/syncfiles/compute/etc/motd > /etc/motd
+    /etc/hosts > /etc/hosts
+~~~~     

 If you put the above contents in /install/custom/netboot/rh/compute.synclist, then: 
+
+~~~~ 

     chdef -t osimage mycomputeimage synclists=/install/custom/netboot/rh/compute.synclist
-    
-
-For more details, see [Sync-ing_Config_Files_to_Nodes]. 
+~~~~     
+
+For more details, see [Sync-ing_Config_Files_to_Nodes](Sync-ing_Config_Files_to_Nodes). 

 ### Configure the nodes to use your osimage

 You can configure any noderange to use this osimage. In this example, we define that the whole compute group should use the image: 
-    
+
+~~~~    
      chdef -t group compute provmethod=mycomputeimage
-    
+~~~~     

 Now that you have associated an osimage with nodes, if you want to list a node's attributes, including the osimage attributes all in one command: 
+
+~~~~ 

     lsdef node1 --osimage
+~~~~ 

 ### Generate and pack your image
@@ -126,35 +142,42 @@
 If the image you are building is for nodes that are the same OS and architecture as the management node (the most common case), then you can follow the instructions here to run genimage on the management node. 

 Run [genimage](http://xcat.sourceforge.net/man1/genimage.1.html) to generate the image based on the mycomputeimage definition: 
+
+~~~~ 

     genimage mycomputeimage
-    
+~~~~     

 Before you pack the image, you have the opportunity to change any files in the image that you want to, by cd'ing to the rootimgdir (e.g. /install/netboot/rhels6/x86_64/compute/rootimg). Although, instead, we recommend that you make all changes to the image via your postinstall script, so that it is repeatable. 

 The genimage command creates /etc/fstab in the image. If you want to, for example, limit the amount of space that can be used in /tmp and /var/tmp, you can add lines like the following to it (either by editing it by hand or via the postinstall script): 
-    
+ 
+~~~~    
     tmpfs   /tmp     tmpfs    defaults,size=50m             0 2
     tmpfs   /var/tmp     tmpfs    defaults,size=50m       0 2
-    
+~~~~     

 But probably an easier way to accomplish this is to create a postscript to be run when the node boots up with the following lines: 
-    
+
+~~~~     
     logger -t xcat "$0: BEGIN"
     mount -o remount,size=50m /tmp/
     mount -o remount,size=50m /var/tmp/
     logger -t xcat "$0: END"
-    
+~~~~     

 Assuming you call this postscript settmpsize, you can add this to the list of postscripts that should be run for your compute nodes by: 
+
+~~~~ 

     chdef -t group compute -p postbootscripts=settmpsize
-    
+~~~~     

 Now pack the image to create the ramdisk: 
-    
+
+~~~~     
     packimage mycomputeimage
-    
+~~~~     

@@ -175,11 +198,11 @@
 The kernel RPM package is usually named _kernel-<kernelver>.rpm_, for example: kernel-2.6.32.10-0.5.x86_64.rpm is the kernel package for **2.6.32.10-0.5.x86_64**. 

-
+~~~~ 

     cp /tmp/kernel-2.6.32.10-0.5.x86_64.rpm /install/kernels/
     createrepo /install/kernels/
-    
+~~~~     

@@ -187,10 +210,11 @@
   * For SLES: 

 Usually, the kernel files for SLES are separated into two parts: _kernel-<arch>-base_ and _kernel_, and the naming of kernel RPM packages are different. For example, there's two RPM packages in /tmp: 
-    
+
+~~~~     
     kernel-ppc64-base-2.6.27.19-5.1.x86_64.rpm
     kernel-ppc64-2.6.27.19-5.1.x86_64.rpm
-    
+~~~~     

 _2.6.27.19-5.1.x86_64_ is **NOT** the kernel version. _2.6.27.19-5-_x86_64 is the kernel version . Follow this naming convention to determine the kernel version. 

@@ -198,10 +222,10 @@

-    
+~~~~     
     cp /tmp/kernel-ppc64-base-2.6.27.19-5.1.x86_64.rpm /install/kernels/
     cp /tmp/kernel-ppc64-2.6.27.19-5.1.x86_64.rpm /install/kernels/
-    
+~~~~     

 Run genimage/packimage to update the image with the new kernel: (Use sles as example) 
@@ -210,39 +234,46 @@

 Since the kernel version is different from the rpm package version, the -g flag needs to be specified on the genimage command for the rpm version of kernel packages. 
-    
+
+~~~~     
     genimage -i eth0 -n ibmveth -o sles11.1 -p compute -k 2.6.27.19-5-x86_64 -g 2.6.27.19-5.1
-    
+~~~~     

 #### **Installing New Kernel Drivers to Stateless Initrd**

 The kernel drivers in the stateless initrd are used for the devices during the netboot. If you are missing one or more kernel drivers for specific devices (especially for the network device), the netboot process will fail. xCAT offers two approaches to add additional drivers to the stateless initrd during the running of **genimage**. 

   * Use the '-n' flag to add new drivers to the stateless initrd 
-    
-    genimage <imagename> -n <new driver list>
-    
+
+~~~~     
+    genimage <imagename> -n <new driver="" list="">
+~~~~     

 Generally, the genimage command has a default driver list which will be added to the initrd. But if you specify the '-n' flag, the default driver list will be replaced with your <new driver list>. That means you need to include any drivers that you need from the default driver list into your <new driver list>. 

 The default driver list: 
-    
+ 
+~~~~    
+ 
     rh-x86:   tg3 bnx2 bnx2x e1000 e1000e igb mlx_en virtio_net be2net
     rh-ppc:   e1000 e1000e igb ibmveth ehea
     sles-x86: tg3 bnx2 bnx2x e1000 e1000e igb mlx_en be2net
     sels-ppc: tg3 e1000 e1000e igb ibmveth ehea be2net
-    
+ 
+~~~~    

 Note: With this approach, xCAT will search for the drivers in the rootimage. You need to make sure the drivers have been included in the rootimage before generating the initrd. You can install the drivers manually in an existing rootimage (using chroot) and run genimage again, or you can use a postinstall script to install drivers to the rootimage during your initial genimage run. 

   * Use the **driver rpm package** to add new drivers from rpm packages to the stateless initrd 

-Refer to the doc [Using_Linux_Driver_Update_Disk#Driver_RPM_Package]. 
+Refer to the doc [Using_Linux_Driver_Update_Disk#Driver_RPM_Package](Using_Linux_Driver_Update_Disk/#driver-rpm-package). 

 ### Boot the nodes
+
+~~~~

     nodeset compute osimage=mycomputeimage
-    
+~~~~    

 (If you need to update your diskless image sometime later, change your osimage attributes and the files they point to accordingly, and then rerun genimage, packimage, nodeset, and boot the nodes.)

Using_Provmethod=osimagename modified by Lissa Valletta

Lissa Valletta — Wed, 25 Jun 2014 15:36:00 -0000

--- v176
+++ v177
@@ -73,9 +73,9 @@

 Make sure nothing is excluded in the exclude list that you need on the node. For example, if you require perl on your nodes, remove the line "./usr/lib/perl5*". 

-{{:Install_OS_Updates}} 
-
-{{:Install_Additional_Packages}} 
+[[include ref=Install_OS_Updates]] 
+
+[[include ref=Install_Additional_Packages]] 

 ### Set up a postinstall script (optional)

Using_Provmethod=osimagename modified by

Mon, 23 Jun 2014 18:51:24 -0000

--- v175
+++ v176
@@ -47,7 +47,10 @@

 This displays the osimage "rhels6.3-x86_64-netboot-compute" in a format that can be used as input to mkdef, but on the way there it uses sed to modify the name of the object to "mycomputeimage". 

-Initially, this osimage object points to templates, pkglists, etc. that are shipped by default with xCAT. And some attributes, for example otherpkglist and synclists, won't have any value at all because xCAT doesn't ship a default file for that. You can now change/fill in any [osimage attributes](http://xcat.sourceforge.net/man7/osimage.7.html) that you want. A general convention is that if you are modifying one of the default files that an osimage attribute points to, copy it into /install/custom and have your osimage point to it there. (If you modify the copy under /opt/xcat directly, it will be over-written the next time you upgrade xCAT.) 
+Initially, this osimage object points to templates, pkglists, etc. that are shipped by default with xCAT. And some attributes, for example otherpkglist and synclists, won't have any value at all because xCAT doesn't ship a default file for that. You can now change/fill in any [osimage attributes](http://xcat.sourceforge.net/man7/osimage.7.html) that you want. A general convention is that if you are modifying one of the default files that an osimage attribute points to, copy it into /install/custom and have your osimage point to it there. (If you modify the copy under /opt/xcat directly, it will be over-written the next time you upgrade xCAT.) An important attribute to change is the rootimgdir which will contain the generated osimage files so that you don't over-write an image built with the shipped definitions. To continue the previous example: 
+    
+      chdef -t osimage -o mycomputeimage rootimgdir=/install/netboot/rhels6.3/x86_64/mycomputeimage
+    

 ### Set up pkglists

Using_Provmethod=osimagename modified by Bruce

Bruce — Mon, 23 Jun 2014 18:51:23 -0000

--- v174
+++ v175
@@ -244,20 +244,3 @@
 (If you need to update your diskless image sometime later, change your osimage attributes and the files they point to accordingly, and then rerun genimage, packimage, nodeset, and boot the nodes.)

 Now boot your nodes... 
-
-## Where Do I Go From Here?
-
-Now that your basic cluster is set up, here are suggestions for additional reading: 
-
-  * To help configure your networks: 
-    * [Managing_the_Mellanox_Infiniband_Network] 
-    * [Managing_Ethernet_Switches] 
-  * To install other HPC products: 
-    * [IBM_HPC_Stack_in_an_xCAT_Cluster] 
-  * For on-going management of the cluster: 
-    * [Using_Updatenode] 
-    * [Monitoring_an_xCAT_Cluster] 
-  * If you want to create multiple virtual machines in each physical server: 
-    * [XCAT_Virtualization_with_VMWare] 
-    * [XCAT_Virtualization_with_KVM] 
-    * [XCAT_Virtualization_with_RHEV]

Using_Provmethod=osimagename modified by Bruce

Bruce — Mon, 23 Jun 2014 18:51:19 -0000

--- v173
+++ v174
@@ -244,3 +244,20 @@
 (If you need to update your diskless image sometime later, change your osimage attributes and the files they point to accordingly, and then rerun genimage, packimage, nodeset, and boot the nodes.)

 Now boot your nodes... 
+
+## Where Do I Go From Here?
+
+Now that your basic cluster is set up, here are suggestions for additional reading: 
+
+  * To help configure your networks: 
+    * [Managing_the_Mellanox_Infiniband_Network] 
+    * [Managing_Ethernet_Switches] 
+  * To install other HPC products: 
+    * [IBM_HPC_Stack_in_an_xCAT_Cluster] 
+  * For on-going management of the cluster: 
+    * [Using_Updatenode] 
+    * [Monitoring_an_xCAT_Cluster] 
+  * If you want to create multiple virtual machines in each physical server: 
+    * [XCAT_Virtualization_with_VMWare] 
+    * [XCAT_Virtualization_with_KVM] 
+    * [XCAT_Virtualization_with_RHEV]

Using_Provmethod=osimagename modified by Lissa Valletta

Lissa Valletta — Mon, 23 Jun 2014 18:51:18 -0000

--- v172
+++ v173
@@ -64,7 +64,7 @@
 Also, check to see if the default exclude list excludes all files and directories you do not want in the image. The exclude list enables you to trim the image after the rpms are installed into the image, so that you can make the image as small as possible.

     cp /opt/xcat/share/xcat/netboot/rh/compute.exlist /install/custom/netboot/rh
-    vi compute.exlist 
+    vi /install/custom/netboot/rh/compute.exlist 
     chdef -t osimage mycomputeimage exlist=/install/custom/netboot/rh/compute.exlist

Using_Provmethod=osimagename modified by Bruce

Bruce — Mon, 23 Jun 2014 18:51:17 -0000

--- v171
+++ v172
@@ -213,14 +213,14 @@

 #### **Installing New Kernel Drivers to Stateless Initrd**

-The kernel drivers in the stateless initrd are used to drive the devices during the netboot. If missing one or more kernel drivers for specific devices (especially for the network device), the netboot process would fail. xCAT offers two approaches to add additional drivers to stateless initrd during the running of **genimage**. 
-
-  * Use the '-n' flag to add new drivers to stateless initrd 
+The kernel drivers in the stateless initrd are used for the devices during the netboot. If you are missing one or more kernel drivers for specific devices (especially for the network device), the netboot process will fail. xCAT offers two approaches to add additional drivers to the stateless initrd during the running of **genimage**. 
+
+  * Use the '-n' flag to add new drivers to the stateless initrd 

     genimage <imagename> -n <new driver list>

-Generally, genimage command has a default driver list which will be added to the initrd by default. But if you specifying the '-n' flag, the default driver list will be replaced with your <new driver list>. That means the default driver list should be added in the <new driver list> if you are not sure whether should remove the default list. 
+Generally, the genimage command has a default driver list which will be added to the initrd. But if you specify the '-n' flag, the default driver list will be replaced with your <new driver list>. That means you need to include any drivers that you need from the default driver list into your <new driver list>. 

 The default driver list: 

@@ -230,9 +230,9 @@
     sels-ppc: tg3 e1000 e1000e igb ibmveth ehea be2net

-Note: With this approach, the drivers will be searched from rootimage. You need to make sure the drivers have been included in the rooimage before generating the initrd. You could install the drivers to an existed rootimage and run genimage again or using the postinstall script to install drivers to rootimage during running of genimage. 
-
-  * Use the **driver rpm package** to add new drivers from rpm packages to stateless initrd 
+Note: With this approach, xCAT will search for the drivers in the rootimage. You need to make sure the drivers have been included in the rootimage before generating the initrd. You can install the drivers manually in an existing rootimage (using chroot) and run genimage again, or you can use a postinstall script to install drivers to the rootimage during your initial genimage run. 
+
+  * Use the **driver rpm package** to add new drivers from rpm packages to the stateless initrd 

 Refer to the doc [Using_Linux_Driver_Update_Disk#Driver_RPM_Package].

Using_Provmethod=osimagename modified by XiaoPeng Wang

XiaoPeng Wang — Mon, 23 Jun 2014 18:51:14 -0000

--- v170
+++ v171
@@ -156,7 +156,7 @@

-#### **Installing a new Kernel in the stateless image**
+#### **Installing a New Kernel in the Stateless Image**

 The _kerneldir_ attribute in _linuximage_ table is used to assign one directory to hold the new kernel to be installed into the stateless/statelite image. Its default value is _/install/kernels_, you need to create the directory named _<kernelver>_ under the _kerneldir_, and genimage will pick them up from there.