On 09/20/2013 01:11 PM, Karli Sjöberg wrote:
fre 2013-09-20 klockan 10:50 +0000 skrev SULLIVAN, Chris (WGK):
Hi,
Just following up on this issue. Turns out the network problems were being
caused by the bond0 interface.
The initial configuration was two NICs teamed as bond0, which was then bridged
to the ovirtmgmt interface. With this configuration, RHEL guests could access
the network normally but Windows guests (XP, 7, 2008 R2) could not. After
deactivating the bond0 interface and bridging one of the NICs directly to the
ovirtmgmt interface, both RHEL and Windows guests have fully functioning
networks.
I am not sure why exactly the bond0 interface was not working as intended. The
initial configuration had the mode as balance-rr, is this known to cause
problems? My intention was to have the mode as balance-alb however the bonding
driver in F19 seems to completely ignore any BONDING_OPTS settings in the
ifcfg-bond0 file. Attempts to change the bonding mode directly via
/sys/class/net/bond0/bonding/mode repeatedly failed due to 'the bond having
slaves', even after the bond had been taken down via ifconfig. I was not able
to remove the bond0 definition either, even after removing the ifcfg-bond0 file
and the modprobe.d alias.
Is there a recommended/tested bonding configuration HOWTO for oVirt on F19?
Have you checked the RHEV documentation and searched Microsoft Technet
for Nic Teaming?
http://technet.microsoft.com/en-us/library/hh831648.aspx - seems MS
Server 2012 R2 supports a type 4 bond.
An excellent doc about bonding is:
http://sourceforge.net/projects/bonding/files/Documentation/12%20November%202007/bonding.txt/download
Regards,
Patrick
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
