I was following theeIPoIB Manual Configuration guide in order to set up the ib interface as the main data interface for a VM. I followed the guide quite closely except for the fact that after setting up the eIPoIB network interface (eth2), I forced it to use a bridge. This bridge was used in the VM definition.
Here's my configuration on the hypervisor:
[root@mgmt2 ~]# ethtool -i eth2
driver: eth_ipoib
version: 1.0.0
firmware-version: 1
bus-info: ib0
[root@mgmt2 ~]# cat /sys/class/net/eth2/eth/vifs
SLAVE=ib0.1 MAC=00:1e:67:76:17:1d VLAN=N/A
[root@mgmt2 ~]# ifconfig eth2
eth2 Link encap:Ethernet HWaddr 00:1E:67:76:17:1D
inet6 addr: fe80::21e:67ff:fe76:171d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:2044 Metric:1
RX packets:70141448 errors:0 dropped:0 overruns:0 frame:0
TX packets:914489 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:138436120082 (128.9 GiB) TX bytes:40287426 (38.4 MiB)
[root@mgmt2 ~]# ifconfig br-data
br-data Link encap:Ethernet HWaddr 00:1E:67:76:17:1D
inet addr:192.200.0.2 Bcast:192.200.255.255 Mask:255.255.0.0
inet6 addr: fe80::21e:67ff:fe76:171d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:2044 Metric:1
RX packets:3528371 errors:0 dropped:0 overruns:0 frame:0
TX packets:914442 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:135771247634 (126.4 GiB) TX bytes:49426414 (47.1 MiB)
[root@mgmt2 ~]# brctl show
bridge name bridge id STP enabled interfaces
br-data 8000.001e6776171d no eth2
vnet0
If I ping another machine on the 192.200. network from the hypervisor everything works fine. However, if I set up a VM to use br-data, I can not ping other machines on the 192.200 network (beside the hypervisor). I'm having a little bit of trouble visualizing how the cloning of interfaces and enslaving them works. Any help would be greatly appreciated.