From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David F. Barrera" Subject: linux-2.6-xen kernels and initrds Date: Thu, 30 Mar 2006 16:12:26 -0600 Message-ID: <442C57CA.3040307@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I have a question regarding the building of the unified xen kernel (linux-2.6-xen) and the use of initrd. In the past I built both xen0 and xenU kernels; the xen0 default configurations had SCSI and Fusion MPT support compiled into the kernel. Now, they are built as modules. The problem is that I am unable to boot the xen kernel built that way, even though I am building an initrd. I have machines running both SLES and FC that are exhibiting this problem. The question is, do I need to do something special to build the initrds? In SuSE, I typically just used the 'mkinitrd' command; in FC4, I do it like this: "mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen 2.6.16-xen". At any rate, nothing has worked to this point. The SCSI device support help page in 'make menuconfig' states 'do not compile this as a module if your root file system (the one containing the directory /) is located on a SCSI device.', which is the case in my setup. But I have seen it where the distros compile it as module, and the initrd takes care of it. Any help would be appreciated. -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides