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: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen-2.0.7 and RHAS 2.4.21
From: "BB Mailing list" <bb.mlist@xxxxxxxxx>
Date: Thu, 26 Oct 2006 15:05:43 +0200
Delivery-date: Thu, 26 Oct 2006 06:06:21 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=cdwjEeisvqYACP4feqN93xZqFmG/POQWckMhXiC9x1edzUH3IUK9k6fTTpV7173FtoVi8+OGsh3zwVSr9cjKu8i15WK/GmI3qjMaVtBZbnbFbBxcTY/q/g/iEfh/phJar33BEUFukxNr4aagwzjgIg/M7um7/ObyDLPholxi4cE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <ae75590e0610260550k77faec99j16be04e9cd9eec86@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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Still a bit confused by how gmail groups the messages, I realize I sent my responses to Mark and Eric-Olivier without CCing the list; here they are:

I've had problems with the auto-generated initrd file on some
servers too. What I usually do is:
 - boot with the regular RHEL kernel
 - do a 'lsmod' to see the loaded modules and write down the ones
related to SCSI/SATA/SAS controllers and disks
 - rebuild the xen initrd with 'mkinitrd -v --with=<module-1>
--with=<module-2> -f /boot/initrd-<version> <version>', adding the
necessary modules
 - reboot and enjoy :)

 If you don't know what modules to add, you can send the output of
'lsmod' and I'll try to see what's needed.

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 :(

Quentin

I don't think I'd Xen 2 on a server?  Xen 3 is better supported in that it
receives regular bugfixing with each release.  There are known problems with
Xen 2 which don't look like being fixed, I'm afraid.

OTOH, Xen 2 systems have been known to make extremely long uptimes, just that
it's not necessarily any more stable than Xen 3 because it doesn't receive
fixes.

Cheers,
Mark



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 !

Cheers,

Quentin.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>