View previous topic :: View next topic |
Author |
Message |
Scorpion265 Tux's lil' helper
Joined: 05 May 2005 Posts: 129 Location: Kansas City, MO
|
Posted: Sat Dec 22, 2012 5:36 pm Post subject: [Solved] Weird Xen Networking Issue |
|
|
Hello all,
I've got Xen 4.2.1 running and am running into a strange networking issue with both PV and HVM servers. When I create a new server, I always have to run sysctl -p /etc/sysctl.conf to get networking run for the newly created VM. I don't know if I am missing a kernel option somewhere, or what. Here is what I have in sysctl.conf:
Code: |
net.ipv4.ip_forward = 1
net.ipv4.conf.bond0.proxy_arp = 1
net.ipv4.conf.eth1.proxy_arp = 1
net.ipv4.conf.eth0.proxy_arp = 1
|
I wasn't sure if I needed proxy_arp on the devices that make up bond0, or bond0 itself. I've tried it with just bond0 and as the configuration shown with the same results. If you want to see my kernel config, I will post it as well.
Last edited by Scorpion265 on Sun Dec 23, 2012 1:06 am; edited 1 time in total |
|
Back to top |
|
|
Scorpion265 Tux's lil' helper
Joined: 05 May 2005 Posts: 129 Location: Kansas City, MO
|
Posted: Sat Dec 22, 2012 11:14 pm Post subject: |
|
|
I was off base on this. It seems like waiting about 5-10 minutes after a domU reboots, the network 'kicks in'. Anyone have any clue what could cause this? This is my xen networking setup:
eth0 and eth1 are bonded to create bond0
bond0 is added to bridge xenbr0
(vif-script vif-bridge bridge=xenbr0) is my network script in xen-config.sxp |
|
Back to top |
|
|
Scorpion265 Tux's lil' helper
Joined: 05 May 2005 Posts: 129 Location: Kansas City, MO
|
Posted: Sun Dec 23, 2012 1:05 am Post subject: |
|
|
Finally figured it out, it was the way my bond was setup. It was using round robin instead of adaptive load balancing. |
|
Back to top |
|
|
|