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

RE: [Xen-users] Success with RHEL 4.1 build?


  • To: brian@xxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Wed, 17 May 2006 22:34:35 +0200
  • Delivery-date: Wed, 17 May 2006 15:56:11 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcZ58IiDqueLC3eOQO2hbLU6TUHUcgAAJsLg
  • Thread-topic: [Xen-users] Success with RHEL 4.1 build?

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> brian@xxxxxxxxxxxxx
> Sent: 17 May 2006 17:51
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Success with RHEL 4.1 build?
> 
> On Wed, May 17, 2006 at 05:07:52AM -0600, John R. Shannon wrote:
> > I had no problem building under CentOS 4.3 which is a RHEL clone. 
> > Nothing special was required. What problem are you encountering?
> 
> Basically, the following errors at boot:
> 
> Loading <module>.ko module                                    
>                   
> <module>: disagrees about version of symbol struct_module     
>                   
> insmod: error inserting '/lib/<module>.ko': -1 Invalid module 
> format            
> ERROR: /bin/insmod exited normally       
> 
> (Repeats for each module)
> 
> This is on a Dell 380n, BTW, which comes with RHEL 4.1 
> compiled for the x86_64 arch.  I'm trying to keep these 
> workstations as "stock" as possible (not a requirement, but 
> more for reasons of time available to test other distros 
> somewhat lacking).  
> 
> Things I've tried:
> 
> 1.  make world, etc... (per the docs)
> 
> Compiles fine, initial boot is fine, module loading errors.
> 
> 2. Thinking that there may be some modules necessary for the 
> particular workstation I'm compiling for, I painstakingly diff'd the
> .9 and .16 .config files.  Compile errors (mostly not being 
> able to find *.ko files) led me to abandon this approach 
> after much time spent modifying kernel configuration params.
> 
> 3.  Another post on the xen-users lists indicated that 
> symbol-related errors might be due to the wrong modules being 
> pulled into the initrd boot image.  So I tried the following:
> 
> $ depmod -F /boot/System.map-2.6.16-xen 2.6.16-xen            
>                   
> $ mkinitrd -o /boot/xen.img 2.6.16-xen 

And you have a "module /boot/xen.img" as part of your grub.conf
[menu.lst in some systems], so that you're using this, and not some
other initrd file?

--
Mats
> 
> Same errors as above.  
> 
> That's where I'm at now.  
> 
>   --Brian
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 


_______________________________________________
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®.