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] Tainted kernel module?


On 5 Oct 2007, at 02:59, Mark Williamson wrote:

Some time ago, I noticed that whilst I had upgraded to Xen 3.1
(kernel 2.6.18-xen), I'd forgot to upgrade the paravirt DomU .cfg
kernels from 2.6.16-xen to reflect this. So, I upgraded the DomU
kernels & ran into issues with mounting devices, and the ext3 module
not being available.

After a bit of faffing about, I managed to sort this out and load the
ext3 module.

However, now, in the domU's dmesg, I see...
---
ide_generic: no version for "struct_module" found: kernel tainted.
---

Is this anything to be concerned about? How can I fix this?

Running RHEL 4.5 Dom0, with CentOS 4.5 guests.

Is some of this perhaps because you didn't upgrade the modules in the initrd
being used by the guests?

Hmmmm, explain? I did a..
---
mkinitrd -v --with=ext3 /boot/initrd-2.6.18-xen.img 2.6.18-xen
---
and copied the /lib/modules/2.6.18-xen/ directories from Dom0 to DomU. This was all prior to getting the 'kernel tainted' message.

FWIW, cat /proc/sys/kernel/tainted in DomU gives a "2" which apparently means a module load was enforced in SUSE (couldn't find the relevant info for RHEL). "--with=ext3"?

Thoughts?

Cheers,

Y.


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

<Prev in Thread] Current Thread [Next in Thread>