WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen-2.0.7 and RHAS 2.4.21

To: "BB Mailing list" <bb.mlist@xxxxxxxxx>
Subject: Re: [Xen-users] Xen-2.0.7 and RHAS 2.4.21
From: "Eric-Olivier Lamey" <eolamey@xxxxxxxxx>
Date: Fri, 27 Oct 2006 07:26:29 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 27 Oct 2006 00:27:01 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bUX1kLCHvOHzQppuarG6mhm+zwB/mmGF3euGdIMGf2j4mfNtzml2XqdNlTzNENz3BK95RbSkH2MPcU4AopvexLdwm3VZZjFcnVRrWDK/YfZw2YkS0wdhH73IXonWlDoSMsPtMCh5dVw76KAiQHXMjywQ7qEexDfejyUdFuEARiM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <ae75590e0610260605w7d381677u6c6918967fb8c2e1@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <ae75590e0610260148m14d76c15t7dbe0fa9d0b1900f@xxxxxxxxxxxxxx> <200610261330.51770.mark.williamson@xxxxxxxxxxxx> <ae75590e0610260550k77faec99j16be04e9cd9eec86@xxxxxxxxxxxxxx> <ae75590e0610260605w7d381677u6c6918967fb8c2e1@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 10/26/06, BB Mailing list <bb.mlist@xxxxxxxxx> wrote:
Hi,

 Hi,

Thanks for the reply; I didn't know you could pass the module names directly
to the mkinitrd command, that sounded like a good idea, but here is the
output:

# mkinitrd -v --with=sg --with=sd_mod --with=e1000 --with=megaraid2
--with=aic7xxx --with=diskdumplib --with=scsi_mod -f /boot/initrd-
2.4.30-xen0 2.4.30-xen0
Looking for deps of module scsi_mod
Looking for deps of module sd_mod
Looking for deps of module unknown
Looking for deps of module aic7xxx
No module aic7xxx found for kernel 2.4.30-xen0 , aborting.

Still not initrd in /boot :(

 Hmmm, is aic7xxx compiled as a module in the xen 2 kernel ? What does a
   find /lib/modules/*xen* -name aic\*
 give ?

 I've just looked on a server using xen 3.0.3 and the module is there.

I overlooked the xen 2 vs xen 3 question: I thought xen 3 required a 2.6
kernel, that's why I went for xen 2 !
Now I'm more than happy if it's not the case !

 Well, you could run a 2.6 kernel on RHEL 3. Actually, I think you
can forget about your RHN support if you run a non-RedHat kernel
anyway, so you might as well go with a 2.6 one. The only package I
need to change on a RHEL 3.7 server to run a 2.6 kernel is
modules-init-tools (just get it from RHEL 4).

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>