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

RE: [Xen-users] Xen 3.1 installation



 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of ymed
> Sent: 30 May 2007 17:16
> To: tim.post@xxxxxxxxxxx
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx; ymed@xxxxxxxxx
> Subject: Re: [Xen-users] Xen 3.1 installation
> 
> >On Tue, 2007-05-29 at 09:37 +0400, ymed wrote:
> >> 
> >> Hello!
> >
> >>    module /boot/initrd-2.6.18-xen
> >> 
> >> When I choose Xen 3.1 during boot I have the next error:
> >> 
> >> error 15: File not found. 
> >> 
> >> Really, Xen 3.1 tarball does not include initrd-2.6.18-xen 
> file in boot directory. Then I have tried to use 
> >> 
> >>    module /boot/initrd-2.6.18.2-34-default 
> >> 
> >> but in this case i see "kernel panic".  
> >> Is it problem with initrd?
> >
> >Yes. You need to build an initrd against the 2.6.18-xen 
> modules. I don't
> >use suse, but I would imagine its not all that much different than :
> >
> >mkinitrd -o /boot/initrd-2.6.18-xen 2.6.18-xen
> >
> >Or mkinitramfs, again I'm not sure what suse packages. Your 
> initrd is a
> >set of specific modules you (and only your) computer needs 
> to boot, and
> >those modules are specific to the kernel they were compiled with. It
> >can't possibly be distributed since its so specific.
> >
> >Hope this helps,
> >--Tim
> >
> >
> Hello Tim, thank you for the answer.
> This is an output of mkinitrd below. It can not finde modules.dep.
> There is no such file in xentarball.
> Mkinitrd created initrd-2.6.18-xen file but "kernel panic" again....

Do "depmod 2.6.18-xen" and you should get a "modules.dep" in the right
place. 

--
Mats



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


 


Rackspace

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