Ovirt devel - Aug 2008 - [PATCH]: Add /lib/modules/*/lib and /lib/modules/*/crypto into managed node

All,
     In order for iSCSI to work properly, we actually need a few of the kernel
modules that we've blown away inside the managed node.  Currently, if you
try to
attach to an iSCSI target, you get this in /var/log/messages in the managed
node:
> Aug  8 13:35:03 node201 kernel: session7: couldn't create a new
> connection.<6>scsi11 : iSCSI Initiator over TCP/IP Aug  8 13:35:03
node201
> modprobe: WARNING: Could not open
> '/lib/modules/2.6.25.11-97.fc9.x86_64/kernel/lib/libcrc32c.ko': No
such file
> or directory Aug  8 13:35:03 node201 modprobe: FATAL: Could not open
> '/lib/modules/2.6.25.11-97.fc9.x86_64/kernel/crypto/crc32c.ko': No
such file
> or directory Aug  8 13:35:03 node201 kernel: connection8:0: Could not
create
> connection due to crc32c loading error. Make sure the crc32c module is
built
> as a module or into the kernel
This patch just adds those two directories back in; if we really need the space
savings, we can probably get rid of some other modules, but we definitely need
the crc ones listed above.

Signed-off-by: Chris Lalancette <clalance at redhat.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt-managed-node-crypto-lib.patch
Type: text/x-patch
Size: 636 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20080808/fe1fa22b/attachment.bin>

Chris Lalancette wrote:
> All,
>      In order for iSCSI to work properly, we actually need a few of the
kernel
> modules that we've blown away inside the managed node.  Currently, if
you try to
> attach to an iSCSI target, you get this in /var/log/messages in the managed
node:
> 
>> Aug  8 13:35:03 node201 kernel: session7: couldn't create a new
>> connection.<6>scsi11 : iSCSI Initiator over TCP/IP Aug  8
13:35:03 node201
>> modprobe: WARNING: Could not open
>> '/lib/modules/2.6.25.11-97.fc9.x86_64/kernel/lib/libcrc32c.ko':
No such file
>> or directory Aug  8 13:35:03 node201 modprobe: FATAL: Could not open
>> '/lib/modules/2.6.25.11-97.fc9.x86_64/kernel/crypto/crc32c.ko':
No such file
>> or directory Aug  8 13:35:03 node201 kernel: connection8:0: Could not
create
>> connection due to crc32c loading error. Make sure the crc32c module is
built
>> as a module or into the kernel
> 
> This patch just adds those two directories back in; if we really need the
space
> savings, we can probably get rid of some other modules, but we definitely
need
> the crc ones listed above.
> 
> Signed-off-by: Chris Lalancette <clalance at redhat.com>
Ick, this is my fault.  I was a little over-zealous with image minimization.

ACK

Perry

Chris Lalancette wrote:
> All,
>      In order for iSCSI to work properly, we actually need a few of the
kernel
> modules that we've blown away inside the managed node.  Currently, if
you try to
> attach to an iSCSI target, you get this in /var/log/messages in the managed
node:
> 
>> Aug  8 13:35:03 node201 kernel: session7: couldn't create a new
>> connection.<6>scsi11 : iSCSI Initiator over TCP/IP Aug  8
13:35:03 node201
>> modprobe: WARNING: Could not open
>> '/lib/modules/2.6.25.11-97.fc9.x86_64/kernel/lib/libcrc32c.ko':
No such file
>> or directory Aug  8 13:35:03 node201 modprobe: FATAL: Could not open
>> '/lib/modules/2.6.25.11-97.fc9.x86_64/kernel/crypto/crc32c.ko':
No such file
>> or directory Aug  8 13:35:03 node201 kernel: connection8:0: Could not
create
>> connection due to crc32c loading error. Make sure the crc32c module is
built
>> as a module or into the kernel
> 
> This patch just adds those two directories back in; if we really need the
space
> savings, we can probably get rid of some other modules, but we definitely
need
> the crc ones listed above.
Committed.

Chris Lalancette