OK, I actually have iptables completely disabled at this point. There is
definitely something wrong with xen networking for me as its causing the
dom0 to get fenced from the cluster. This only happens if I have a guest
running on the dom0. Its not immediate though, happens randomly. But as
often as every hour or two. The dom0 is rock solid though if no guests are
running. My question though, is that if any major network changes have
happened between xen 3.3.1 and xen 3.4.1, why arent they documented
anywhere. The xen networking wiki hasnt been changed since Feb, so i wouldnt
think there were any. =/
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Wead, Adam G
Sent: Thursday, September 10, 2009 7:50 AM
To: Mark Chaney; Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] networking issue after upgrading to 3.4.1
Mark,
What does your iptables config look like?
...adam
________________________________________
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Mark Chaney
[macscr@xxxxxxxxxx]
Sent: Thursday, September 10, 2009 1:37 AM
To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] networking issue after upgrading to 3.4.1
Ok, im having an issue our xen networking once I updated to 3.4.1 on my
Centos 5.3 box. I've documented it here:
Error in /var/log/messages:
Sep 9 03:01:03 wheeljack logger: /etc/xen/scripts/vif-bridge: iptables
setup failed. This may affect guest networking.
NOTE: vif-bridge is stock that comes with 3.4.1
part of xend-config.sxp:
(network-script network-bridge-wrapper)
(vif-script vif-bridge)
[root@wheeljack ~]# cat /etc/xen/scripts/network-bridge-wrapper
#!/bin/sh
/etc/xen/scripts/network-bridge $1 netdev=eth0
/etc/xen/scripts/network-bridge $1 netdev=eth1
ifconfig is giving me: eth0, eth1, eth2, eth3,peth0, peth1, lo, and virbr0
btw, I upgraded from 3.3.1 to 3.4.1. I know it says the error is with
vif-bridge, but that's stock, so I don't know what could be wrong with it.
any ideas?
Thanks,
Mark
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home