Re: [Xen-users] Pvops Kernel Compile: No module isci found for kernel 2.6.32.12

["Zhu, Shengkai" <shengkai.zhu@xxxxxxxxx>]

Here I got some detailed message from serial console. It shows several moduels 
errors during loading... What's the problem?

--Shengkai

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxx] 
On Behalf Of Zhu, Shengkai
Sent: Thursday, March 22, 2012 3:28 PM
To: Fajar A. Nugraha
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Pvops Kernel Compile: No module isci found for kernel 
2.6.32.12

Thank you for your reply, Fajar.

I am using 4.1.2-rc because I was on a mission to duplicate some test results.

You are correct, my original kernel was distro RHEL5.7 (2.6.18), this is also a 
part of duplicate requirement.

And I agree with you that the isci probably not relevant, since I could boot it 
up with native 2.6.32 kernel.

--Shengkai

-----Original Message-----
From: Fajar A. Nugraha [mailto:list@xxxxxxxxx]
Sent: Thursday, March 22, 2012 3:15 PM
To: Zhu, Shengkai
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Pvops Kernel Compile: No module isci found for kernel 
2.6.32.12

On Thu, Mar 22, 2012 at 2:00 PM, Zhu, Shengkai <shengkai.zhu@xxxxxxxxx> wrote:
> Hi folks,
>
>
>
>    I'm compiling xen-4.1.2-rc6

Why -rc? Isn't 4.1.2 out already?

> with pvops kernel 2.6.32.12. When mkinitrd, it shows error: No module 
> isci found for kernel 2.6.32.12, aborting. Does anyone know which 
> driver I'm missing in config?

Which kernel version were you on originally? I think for newer kernels (3.x 
anyway) the kernel module for iscsi initiator is iscsi_tcp.

>
>
>
> mkinitrd -v -f --with=ahci --with=aacraid --with=sd_mod 
> --with=scsi_mod /boot/initrd-xen.img 2.6.32.12
>
> Creating initramfs
>
> Modulefile is /etc/modprobe.conf
>
> Looking for deps of module ehci-hcd
>
> Looking for deps of module ohci-hcd
>
> Looking for deps of module uhci-hcd
>
> Looking for deps of module ext3
>
> Found root device sda1 for LABEL=/
>
> Looking for driver for device sda1
>
> Looking for deps of module
> pci:v00008086d00001D02sv00008086sd00003584bc01sc06i01: scsi_mod libata 
> ahci
>
> Looking for deps of module scsi_mod
>
> Looking for deps of module sd_mod: scsi_mod
>
> Looking for deps of module libata: scsi_mod
>
> Looking for deps of module ahci: scsi_mod libata
>
> Looking for driver for device sda2
>
> Looking for deps of module
> pci:v00008086d00001D02sv00008086sd00003584bc01sc06i01: scsi_mod libata 
> ahci
>
> Looking for deps of module isci
>
> No module isci found for kernel 2.6.32.12, aborting.
>
>
>
>    I tried to bypass the issue by comment out the isci line in 
> /etc/modprobe.conf, it hung at:
>
>
>
> Setting up other filesystems.
>
> Setting up new root fs
>
> setuproot: moving /dev failed: No such file or directory
>
> no fstab.sys, mounting internal defaults
>
> setuproot: error mounting /proc: No such file or directory
>
> setuproot: error mounting /sys: No such file or directory
>
> Switching to new root and running init.
>
> unmounting old /dev
>
> unmounting old /proc
>
> unmounting old /sys
>
> switchroot: mount failed: No such file or directory
>
> Kernel panic - not syncing: Attempted to kill init!
>
>
>
>    Any idea?

Do you use iscsi? If not, then whether the module is included in initrd or not 
is not related to whether you can boot or not.

If you're originally on a distro that uses kernel 2.6.32 or newer (e.g. 
RHEL/Centos6) then using 2.6.32 (or newer) xen kernel should be straight 
forward. However, if you originally use an older kernel (e.g.
RHEL/Centos5 with 2.6.18) there are some additional compatibility kernel config 
that needs to be turned on (forgot which ones, sorry).
Failure to have those config on might be the cause of your problem.

I'd actually recommend you start with latest upstream kernel from 
http://elrepo.org/tiki/kernel-ml . It SHOULD work as dom0 kernel (at least the 
one for RHEL6 does, I haven't tested the one for RHEL5), and should give you a 
good baseline on which kernel configuration items are necessary.

--
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

Attachment: dom0bootfail.log
Description: dom0bootfail.log

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users