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

["BB Mailing list" <bb.mlist@xxxxxxxxx>]

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