[Xen-users] Installing openib modules to support IB over Debian.4-0 image

[rohan nigam <locaterohan@xxxxxxxxx>]

Hi,
 
 I am new to Xen. I have been experimenting with running mpi over Xen. I would really appreciate if you can tell me how i can install new modules that support IB  (Infiniband) over Xen.  I started using: mpirun --mca btl openib -np 2 IMB-MPI1
 
 I got the following error:

debian-pristine:~/IMB_3.1/src# /usr/local/bin/mpirun --mca btl openib -np 2 IMB-MPI1
libibverbs: Fatal: couldn't read uverbs ABI version.
--------------------------------------------------------------------------
[0,1,0]: OpenIB on host debian-pristine was unable to find any HCAs.
Another transport will be used instead, although this may result
 in
lower performance.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
No available btl components were found!

This means that there are no components of this type installed on your
system or all the components reported that they could not be used.

This is a fatal error; your MPI process is likely to abort. 
 Check the
output of the "ompi_info" command and ensure that components of this
type are available on your system.  You may also wish to check the
value of the "component_path" MCA parameter and ensure that it has at
least one directory that contains valid MCA components.

--------------------------------------------------------------------------
libibverbs: Fatal: couldn't read uverbs ABI version.
--------------------------------------------------------------------------
[0,1,1]: OpenIB on host debian-pristine was unable to find any HCAs.
Another transport will be used instead, although this may result in
lower performance.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
No available btl components were found!

This means that there
 are no components of this type installed on your
system or all the components reported that they could not be used.

This is a fatal error; your MPI process is likely to abort.  Check the
output of the "ompi_info" command and ensure that components of this
type are available on your system.  You may also wish to check the
value of the "component_path" MCA parameter and ensure that it has at
least one directory that contains valid MCA components.

--------------------------------------------------------------------------
When i did omppi_info i got this:

debian-pristine:~/IMB_3.1/src# ompi_info
                Open MPI: 1.2.6
   Open MPI SVN revision: r17946
                Open RTE: 1.2.6
   Open RTE SVN revision: r17946
                    OPAL: 1.2.6
       OPAL SVN revision: r17946
                  Prefix: /usr/local
 Configured architecture: x86_64-unknown-linux-gnu
           Configured by: root
           Configured on: Mon May  5 17:11:55 CDT 2008
          Configure host: debian-pristine
                Built by: root
                Built on: Mon May  5 17:22:09 CDT 2008
              Built host: debian-pristine
              C bindings: yes
           
 C++ bindings: yes
      Fortran77 bindings: yes (all)
      Fortran90 bindings: yes
 Fortran90 bindings size: small
              C compiler: gcc
     C compiler absolute: /usr/bin/gcc
            C++ compiler: g++
   C++ compiler absolute: /usr/bin/g++
      Fortran77 compiler: gfortran
  Fortran77 compiler abs: /usr/bin/gfortran
      Fortran90 compiler: gfortran
  Fortran90 compiler abs: /usr/bin/gfortran
             C profiling: yes
           C++ profiling: yes
     Fortran77 profiling: yes
     Fortran90 profiling: yes
          C++ exceptions: no
          Thread support: posix (mpi: no, progress: no)
  Internal debug support: no
     MPI parameter check: runtime
Memory profiling support: no
Memory debugging support: no
         libltdl support: yes
   Heterogeneous support: yes
 mpirun default --prefix: no
           MCA backtrace: execinfo (MCA v1.0, API v1.0, Component v1.2.6)
              MCA memory: ptmalloc2 (MCA v1.0, API v1.0, Component v1.2.6)
           MCA paffinity: linux (MCA v1.0, API v1.0, Component v1.2.6)
           MCA maffinity: first_use (MCA v1.0, API v1.0,
 Component v1.2.6)
               MCA timer: linux (MCA v1.0, API v1.0, Component v1.2.6)
         MCA installdirs: env (MCA v1.0, API v1.0, Component v1.2.6)
         MCA installdirs: config (MCA v1.0, API v1.0, Component v1.2.6)
           MCA allocator: basic (MCA v1.0, API v1.0, Component v1.0)
           MCA allocator: bucket (MCA v1.0, API v1.0, Component
 v1.0)
                MCA coll: basic (MCA v1.0, API v1.0, Component v1.2.6)
                MCA coll: self (MCA v1.0, API v1.0, Component v1.2.6)
                MCA coll: sm (MCA v1.0, API v1.0, Component v1.2.6)
                MCA coll: tuned (MCA v1.0, API v1.0, Component v1.2.6)
                  MCA io: romio (MCA v1.0, API v1.0, Component v1.2.6)
               MCA mpool: rdma (MCA v1.0, API v1.0, Component v1.2.6)
               MCA mpool: sm (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA pml: cm (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA pml:
 ob1 (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA bml: r2 (MCA v1.0, API v1.0, Component v1.2.6)
              MCA rcache: vma (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA btl: openib (MCA v1.0, API v1.0.1, Component v1.2.6)
                 MCA btl: self (MCA v1.0, API v1.0.1, Component
 v1.2.6)
                 MCA btl: sm (MCA v1.0, API v1.0.1, Component v1.2.6)
                 MCA btl: tcp (MCA v1.0, API v1.0.1, Component v1.0)
                MCA topo: unity (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA osc: pt2pt (MCA v1.0, API v1.0, Component v1.2.6)
              MCA errmgr: hnp (MCA v1.0, API v1.3, Component v1.2.6)
              MCA errmgr: orted (MCA v1.0, API v1.3, Component v1.2.6)
              MCA errmgr: proxy (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA gpr: null (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA gpr: proxy (MCA v1.0, API v1.0,
 Component v1.2.6)
                 MCA gpr: replica (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA iof: proxy (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA iof: svc (MCA v1.0, API v1.0, Component v1.2.6)
                  MCA ns: proxy (MCA v1.0, API v2.0, Component v1.2.6)
                  MCA ns: replica (MCA v1.0, API v2.0, Component v1.2.6)
                 MCA oob: tcp (MCA v1.0, API v1.0, Component v1.0)
                 MCA ras: dash_host (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA ras: gridengine (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA ras: localhost (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA ras: slurm (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA rds: hostfile (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA rds: proxy (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA rds: resfile (MCA v1.0, API v1.3, Component v1.2.6)
               MCA rmaps: round_robin (MCA v1.0, API v1.3, Component v1.2.6)
                MCA rmgr: proxy (MCA v1.0, API v2.0, Component v1.2.6)
                MCA rmgr: urm (MCA v1.0, API v2.0, Component v1.2.6)
                 MCA
 rml: oob (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA pls: gridengine (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA pls: proxy (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA pls: rsh (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA pls: slurm (MCA v1.0, API v1.3, Component v1.2.6)
                 MCA sds: env (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA sds: pipe (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA sds: seed (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA sds: singleton (MCA v1.0, API v1.0, Component v1.2.6)
                 MCA sds: slurm (MCA v1.0, API v1.0, Component v1.2.6)

As you can see the openib component is there. (see the line in bold)

So then i tried looking if i have all the modules for running IB in my xen image and i found that no modules are installed in the Xen image.

The image that i got is an debian.4-0 from the source: www.jailtime.org. Can any one please tell me how do i go about this problem. 

Thanks.

-Rohan

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