[Xen] Networking with bonding.
Posted: 2011/12/26 19:49:44
Hi everyone !
It's been quite a long time since I last came here... Everything was doing right in fact, up until I wanted to change something. :-D
So... I have a server running CentOS 5.7, up to date etc... I have 3 NICs that I bonded together in mode 4 (802.3ad) and I have the correct config on the other part, on my switch. On top of that bond0, I created a VLAN with ID 5. My server is used for several stuff, but mainly samba 3 as PDC and routing to the Internet. With a regular kernel, it's working perfectly (CentOS rocks !).
For several reasons, I need to run a WinXP virtual machine. So I decided to move towards xen. I installed all the stuff required for xen. So now, I am running a xen kernel 2.6.18-274.7.1.el5xen. The 2.6.18-274.12.1.el5 is installed but I have not rebooted yet. Anyway, I do not believe the update would solve my problems. What I would like is to keep my bond0 as the physical NIC with xen.
I read a lot everywhere and I came to the conclusion I should end with the following configuration. My bond0 device should be part of a bridge (let's call it xenbr0), with IP 0.0.0.0 (to receive everything). Then, I should create a bridge, let's call it xenbr0, and add vif0.0 to xenbr0. Finally, I should put my desired addresses for dom0 on veth0 (created by xen). And finally, fire up all the stuff. All right, that's the theory. The fact is : this is not working. I cannot reach anything in my network with this config', and nothing on the network can reach the server.
If I do use the scripts, they give the bridge (xenbr0, which is in fact renamed bond0 because bond0 is called pbond0... whatever...) the IP I want my dom0 to have. In that config', the server is reachable through the bridge. This could be all right, but if I add a vifU.0 to that bridge to let my domU get in the network, the domU does not connect to the network. The domU is completely isolated.
So my question is simple : how should I proceed to get what I want ? I guess the answer is a bit more complicated. :-P
I must add I tried to work with the MACs : give an appropriate MAC to the vifn.0 ifaces (one like 02:... as it is said on the xen wiki), the same to the vethn, not carrying at all about MACs... No way.
I hope someone could help me. Thanks in advance.
Cheers !
It's been quite a long time since I last came here... Everything was doing right in fact, up until I wanted to change something. :-D
So... I have a server running CentOS 5.7, up to date etc... I have 3 NICs that I bonded together in mode 4 (802.3ad) and I have the correct config on the other part, on my switch. On top of that bond0, I created a VLAN with ID 5. My server is used for several stuff, but mainly samba 3 as PDC and routing to the Internet. With a regular kernel, it's working perfectly (CentOS rocks !).
For several reasons, I need to run a WinXP virtual machine. So I decided to move towards xen. I installed all the stuff required for xen. So now, I am running a xen kernel 2.6.18-274.7.1.el5xen. The 2.6.18-274.12.1.el5 is installed but I have not rebooted yet. Anyway, I do not believe the update would solve my problems. What I would like is to keep my bond0 as the physical NIC with xen.
I read a lot everywhere and I came to the conclusion I should end with the following configuration. My bond0 device should be part of a bridge (let's call it xenbr0), with IP 0.0.0.0 (to receive everything). Then, I should create a bridge, let's call it xenbr0, and add vif0.0 to xenbr0. Finally, I should put my desired addresses for dom0 on veth0 (created by xen). And finally, fire up all the stuff. All right, that's the theory. The fact is : this is not working. I cannot reach anything in my network with this config', and nothing on the network can reach the server.
If I do use the scripts, they give the bridge (xenbr0, which is in fact renamed bond0 because bond0 is called pbond0... whatever...) the IP I want my dom0 to have. In that config', the server is reachable through the bridge. This could be all right, but if I add a vifU.0 to that bridge to let my domU get in the network, the domU does not connect to the network. The domU is completely isolated.
So my question is simple : how should I proceed to get what I want ? I guess the answer is a bit more complicated. :-P
I must add I tried to work with the MACs : give an appropriate MAC to the vifn.0 ifaces (one like 02:... as it is said on the xen wiki), the same to the vethn, not carrying at all about MACs... No way.
I hope someone could help me. Thanks in advance.
Cheers !