1 person found this helpful
Usually, the OVM installer creates a bond0 interface using the NIC you selected as the magement network. For me, it never actually tied two NICs to the bond0 interface. You should get rid of the 2nd bonded interface and use that 2nd NIC for your guests.
I've check my settings and I think you are right.
- NIC 1
DEVICE=eth0 HWADDR=00:25:90:6B:15:A8 BOOTPROTO=none ONBOOT=yes BRIDGE=10b661baf0 NM_CONTROLLED=no
- NIC 2
DEVICE=eth1 BOOTPROTO=none HWADDR=00:25:90:6B:15:A9 ONBOOT=yes MASTER=bond0 SLAVE=yes
DEVICE=bond0 BONDING_OPTS="mode=1 miimon=250 use_carrier=1 updelay=500 downdelay=500 primary=eth1" BOOTPROTO=static ONBOOT=yes IPADDR=192.168.50.51 NETMASK=255.255.255.0 #NETWORK=192.168.50.0 GATEWAY=192.168.50.x
DEVICE=10b661baf0 TYPE=Bridge BOOTPROTO=none ONBOOT=yes DELAY=0
[root@oravm3 network-scripts]# brctl show bridge name bridge id STP enabled interfaces 10b661baf0 8000.0025906b15a8 no eth0 tap5.0 vif5.0
So, with your suggestions, I am considering some tasks that have to do:
- connect two NICs to network (I am using same network 192.168.50.0/24 for management and guest virtual machine)
- set the IP for bridge (192.168.50.x)
- how does connect Virtual NIC to bridge (to 192.168.50.0/24 network)?
Sorry for my bad understanding
Please use OVM Manager to set these things - it will do all the setup for you. Changeing settings by bypassing OVMM can lead to very "intertesting" results.