[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Mkinitramfs wants minimum 2.6.19 kernel!


  • To: "Emre Erenoglu" <erenoglu@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Mon, 5 Mar 2007 12:49:50 +0100
  • Delivery-date: Mon, 05 Mar 2007 03:49:40 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdexQdJ7YZnACdaRWO9v4Aj2LbfWwAVq8fQ
  • Thread-topic: [Xen-devel] Mkinitramfs wants minimum 2.6.19 kernel!

 

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Emre Erenoglu
> Sent: 05 March 2007 01:24
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Mkinitramfs wants minimum 2.6.19 kernel!
> 
> Dear Developers,
> 
> I'm sorry to disturb you with this problem, however, I couldn't find
> any clue in neither Ubuntu nor Xen mail lists, so this was my last way
> out:
> 
> I have a Ubuntu Feisty latest beta on my system with  2.6.20-9-generic
> kernel from Ubuntu Archives.
> 
> I built the latest Xen from mercurial repository (as of March 4, 2007)
> in this system, everything went fairly well after including bcc,
> -fno-stack-protector tricks etc.
> 
> now I'm trying to build an initrd image, as I have LVM and 
> RAID on my disks.
> 
> Here's the problem:
> 
> root@xen:/boot/xen# depmod 2.6.18-xen
> root@xen:/boot/xen# mkinitramfs -o 
> /boot/xen/initrd-2.6.18-xen.img 2.6.18-xen
> W: udev hook script requires at least kernel version 2.6.19
> W: not generating requested initramfs for kernel 2.6.18-xen
> 
> So mkinitramfs complains that my udev scripts need at least kernel
> 2.6.19. Would one of you have any clue on how to overcome this
> problem?

My guess is that you can simply edit mkinitramfs to "chop out" the check
for version of the kernel. However, there may be other parts of the
produced file that doesn't work - the check is PROBABLY there for some
good reason! But it's a simple change - just do "<your favourite editor>
`which mkinitramfs`" [note that those are "back-quotes" around the
"which" statement] and search for the error message, then remove
(comment out by adding # at the start of the lines) the whole
if-statement that checks the version. 

The other, more complex solution would be to change the version of the
kernel in Xen. There's been a few posts on Xen-users to explain how to
do that, but if you're not familiar with debugging why a Linux kernel
doesn't work, that's probably not an easy to achieve task. 

--
Mats
> 
> Thanks and Best regards,
> 
> Emre
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> 
> 



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.