I tried using ib-verbs as transport with a simple configuration. It's failing saying completion channel cannot be started.  The function ibv_create_comp_channel() in ib_verbs_get_device() is failing for some reason.

Logs and vol files are attached.
snippet of logfile:
[2009-06-26 03:23:37] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /opt/glusterfs/2.0.2/lib/glusterfs/2.0.2/xlator/features/locks.so: undefined symbol: notify -- neglecting
[2009-06-26 03:23:37] D [xlator.c:634:xlator_set_type] xlator: dlsym(notify) on /opt/glusterfs/2.0.2/lib/glusterfs/2.0.2/xlator/performance/io-threads.so: undefined symbol: notify -- neglecting
[2009-06-26 03:23:37] D [glusterfsd.c:1179:main] glusterfs: running in pid 15592
[2009-06-26 03:23:37] D [io-threads.c:2280:init] brick: io-threads: Autoscaling: off, min_threads: 8, max_threads: 8
[2009-06-26 03:23:37] D [transport.c:141:transport_load] transport: attempt to load file /opt/glusterfs/2.0.2/lib/glusterfs/2.0.2/transport/ib-verbs.so
[2009-06-26 03:23:37] D [xlator.c:276:_volume_option_value_validate] server: no range check required for 'option transport.ib-verbs.listen-port 23456'
[2009-06-26 03:23:37] E [ib-verbs.c:1394:ib_verbs_get_device] transport/ib-verbs: mlx4_0: could not create send completion channel
[2009-06-26 03:23:37] E [ib-verbs.c:1537:ib_verbs_init] transport/ib-verbs: could not create ib_verbs device for mlx4_0
[2009-06-26 03:23:37] E [ib-verbs.c:2362:init] server: Failed to initialize IB Device
[2009-06-26 03:23:37] E [transport.c:200:transport_load] transport: 'ib-verbs' initialization failed
[2009-06-26 03:23:37] E [server-protocol.c:7624:init] server: failed to load transport
[2009-06-26 03:23:37] E [xlator.c:736:xlator_init_rec] xlator: Initialization of volume 'server' failed, review your volfile again
[2009-06-26 03:23:37] E [glusterfsd.c:498:_xlator_graph_init] glusterfs: initializing translator failed
[2009-06-26 03:23:37] E [glusterfsd.c:1191:main] glusterfs: translator initialization failed.  exiting

This seems to be an installation issue. Same config is working with 2.0.0.