yes, I am using the network bridge. Here is part of
[root <at> wheeljack ~]# cat
/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,
Eth0 is used for backup and cman communication only, its only,
its on a separate vlan.
Eth1 is for WAN communnication
Eth2,Eth3 is for iSCSI only and guests dont have direct access
Snippet from /var/log/messages:
Sep 13 01:28:32 wheeljack kernel: device vif1.0 entered
Sep 13 01:28:32 wheeljack kernel: physdev match: using --physdev-out
in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is
deprecated and breaks other things, it will be removed in January 2007. See
Documentation/feature-removal-schedule.txt for details. This doesn't affect you
in case you're using it for purely bridged traffic.
Sep 13 01:28:32 wheeljack logger: /etc/xen/scripts/vif-bridge:
iptables setup failed. This may affect guest networking.
Sep 13 01:28:37 wheeljack kernel: blkback: ring-ref 8,
event-channel 6, protocol 1 (x86_64-abi)
Sep 13 01:28:37 wheeljack kernel: eth1: topology change
Sep 13 01:28:37 wheeljack kernel: eth1: port 2(vif1.0) entering
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. I dont get these errors witht he
Xen 3.3.1 and Kernel i mentioned earlier. Ive gone as far as disabling iptables
and still have the same issues with stability. You did bring up an idea though,
i havent tried disabling access to eth0 from the guests, but again, what
changed in the xen versions that would cause such a problem if it was that. I
swear there must have been a change that has been poorly documented.
Anyway, thanks for the help, I sincerelly appreciate it.
From: Stephen Ross
Sent: Sunday, September 13, 2009 4:25 AM
To: Mark Chaney
Subject: Re: [Xen-users] 3.4.x networking
Are you using the xen network-bridge script or ifcfg scripts
to setup your networking? Are guest VM's and CMAN node info passing on the same
On Sun, Sep 13, 2009 at 6:57 AM, Mark Chaney <macscr@xxxxxxxxxx> wrote:
My Centos 5.3 cluster has major network stability issues (these are the
dom0's) when running xen 3.4 and 3.4.1. Things were rock solid when running
3.3.1 and they were again when we downgraded back to it. Are there any known
network issues with the 3.4.x group? Did something change with 3.4 with how
networking is done that we might have needed to change? The guest networking
worked fine afaik, but every hour or so, the dom0 would get fenced by another
cluster member and its more than likely because of some type of networking
change (maybe like the network service getting restarted or whatever). I
couldn’t get any useful info out of the logs, but only happened on nodes
that were running 3.4.x and it only happened if guests were running on it.
Everything was fine if no guests were running. BTW, we tried changing kernels
and that didn’t make a difference either. Current with centos is
2.6.18-128.7.1.el5xen, but our cluster was the most stable with
2.6.18-92.1.22.el5xen #1 SMP Tue Dec 16 12:26:32 EST 2008 x86_64 x86_64 x86_64
GNU/Linux and xen 3.3.1. Obviously for security and performance reasons we want
to stay current
Any help is sincerelly appreciated!
Xen-users mailing list